GRD-Border-Noise and Thermal noise removal are not working anymore since March 13. 2018

Microwave Toolbox Problem Reports
#48

Thats interesting @paultcochrane - I would be interested to see if your installation can replicate the issue of data quality after thermal noise removal with the following image: S1A_IW_GRDH_1SDV_20180313T180532_20180313T180557_021000_0240E0_114C
My steps are as follows:

  1. Apply Restituted Orbits
  2. Border Noise removal
  3. Thermal Noise removal - this step produces the bad image in S-1 Thermal Noise removal introduces Artefacts in the image. I think this is related to the number 4 issue raised by @biocpu
    Thanks,
    Sanjay.
#49

Anyone has any news for this problem?

#50

This should be fixed with the update from May 20th

#51

Thanks lveci!

Just FYI and someone would be interested.

The new Sentinel-1 images (after 2018.03.18) “Thermal Noise Removing” procedure uses about twice memory size than the previous images (before 2018.03.18). So enlarge the memory limitation will solve the “NullPointerException” error.

According to my tests, it should be 15GB or larger.

Find the file SNAPINSTALLATIONDIRECTORY/snap/bin/gpt.vmoptions

add
Xmx15G

1 Like
#52

I can confirm the memory issue with Sentinel1RemoveThermalNoiseOp. The method buildNoiseLUTForTOPSGRD creates very large matrices, for instance:
noiseMatrix = new double[numLines][numSamples];//numLines: 16694, numSamples: 8807

This causes the memory requirement to be a bit impractical. Perhaps the LUT can be created in a more memory efficient manner?

1 Like
#53

Hi,

I am using SNAP 6.0 with s1tbx (V. 6.0.3). I am trying to co-register two images acquired after March 13, 2018 with GPT, by performing the Thermal noise removal and other pre-processing steps. The process stops after 40% as shown below, providing an output image with half of the cells affected by No data values:

…10%…20%…30%…40%.Sentinel1RemoveThermalNoiseOp: ERROR: i = 9 y = 13527burstBlocks[i].azimuthNoise.length = 13527
java.lang.NullPointerException

The same graph works if I use the SNAP user interface, highlighting that in my case this issue is not related to the used memory.

Could you give me some information about this error ?

Thanks,
Giuseppe

Bad outcome of batch preprocessing sequence
#54

So the issue is still not fixed? Do you have a recommendation about how to get around this problem?
VHR

#55

It’s been working fine for my graphs. Maybe you should include exactly which products and which preprocessing you did to repeat the problem

#56

I would suggest you bring the image id so that they can easily locate the problem. Just FYI.

LOL

getGeoPos errors with GPT
#57

For me I think the problem is somehow fixed as long as we got sufficient memory space. I have already processed about 40 images without any problem.

For giuse’s question, I think it may relate to the image itself.

#58

I posted a couple of days ago this (one of the scenes that I´m having problems with is S1A_IW_GRDH_1SDV_20180425T115326_20180425T115359_021623_025464_D0DE):

For some time now I have been unable to complete a batch preprocessing sequence even if I have the latest version and update plugins every time I start SNAP. My graph contains:

_ Apply orbit file_
_ Thermal noise removal_
_ Calibration_
_ Multilook_

I try to process 5 S1A_IW_GRDH_1SDV dual polarization scenes dating from between March and April 2018 and that cover Northern Guatemala.

Some of the scenes (the older ones and usually just 2 of them) are processed well, but the others just don´t have any meaningful data. The process creates a huge file (17 GB) in the log directory (file created = heapdump.hprof.old). I´m attaching the resultant log file.

Can someone help me correct this issue? Thanks.

#59

And my computer has 32 GB of RAM . . . would that be a problem? How much do you have?

VHR

#60

Would you please check SNAPINSTALLATIONDIRECTORY/snap/bin/gpt.vmoptions

Did you set the software memory limitation? like:

Xmx15G

Enlarge it or write it down to see if you can solve this.

And you can also check some memory inspection applications to see if the program uses enough memory.

Cheers,

#61

You are right we will need to fix this with a module update.

#62

Thanks for your suggestion. I checked and I have Xmx20G that I assume means that I have 20 GB configured. Do I move this number to 32? Am I limited to just what I have in RAM memory? Thanks again.
VHR

#63

Hello,

I am a little confused. Does this mean we do not need correct data for thermal noise and border noise after the update?

Thanks,
Diya

#64

Yes you should do them, even if in many cases their effect on the end-result is minimal.

#65

Thank you. I updated my installation to the most recent version and am getting the same error as mentioned by holi in the first post of this thread.

INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters

at index 23: C:\WINDOWS\System32\Wbevator.GDALPlugInActivator: Illegal char <
m
at index 23: C:\WINDOWS\System32\Wbelegal char <
m
at sun.nio.fs.WindowsPathParser.normalize(Unknown Source)
at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at sun.nio.fs.WindowsPath.parse(Unknown Source)
at sun.nio.fs.WindowsFileSystem.getPath(Unknown Source)
at java.nio.file.Paths.get(Unknown Source)
at org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller.findFolderInPathEnvironment(GDALDistributionInstaller.java:213)
at org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller.processInstalledWindowsDistribution(GDALDistributionInstaller.java:179)
at org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller.install(GDALDistributionInstaller.java:67)
at org.esa.s2tbx.dataio.gdal.activator.GDALPlugInActivator.start(GDALPlugInActivator.java:22)
at org.esa.snap.runtime.Engine.informActivators(Engine.java:222)
at org.esa.snap.runtime.Engine.lambda$start$10(Engine.java:121)
at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
at org.esa.snap.runtime.Engine.start(Engine.java:121)
at org.esa.snap.runtime.Engine.start(Engine.java:90)
at org.esa.snap.runtime.Launcher.run(Launcher.java:51)
at org.esa.snap.runtime.Launcher.main(Launcher.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:62)
at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:101)
at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:16)

Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start
java.lang.NullPointerException
done.

Error: [NodeId: Remove-GRD-Border-Noise] java.lang.NullPointerException

I am using the same graph I’ve been using before the March update and it is not working now. Do you have any suggestions?

Thank you,
Diya

#66

Hello again,

My mistake, I had not completed the update. I am no longer getting these errors. Thank you.

-Diya

#67

I think you may not finished your snap update. I made my limitation for 15g and successfully processed over hundreds of images.

refer to this web: https://senbox.atlassian.net/wiki/spaces/SNAP/pages/30539785/Update+SNAP+from+the+command+line

list and check your local snap version.