Null pointer exception slice assemby after12th March 2018

s1tbx
#1

Hello

We operationally process Sentinel 1 (A and B) data over our area. First step we do is slice assembly. We are experiencing problems with data after 12th march 2018.

The slice assembly process throws Null Pointer Exception. If we do tasks with data acquired prior to 13th march SNAP processes data without problems. If we try to apply the same process, to data acquired starting from 13th march 2018, the processing fails. We have reprocessed some previous data and the processing is succesful.

We are using SNAP 6 on linux ubuntu. We have test that on two different computers (both the same SNAP version and the same operating system) with the same outputs.

20180312 and prior, the processing succes:

S1B_IW_GRDH_1SDV_20180312T070928_20180312T070953_009995_0121F1_2CE6.zip
S1B_IW_GRDH_1SDV_20180312T070953_20180312T071018_009995_0121F1_75F7.zip
S1B_IW_GRDH_1SDV_20180312T071018_20180312T071043_009995_0121F1_D21B.zip

2013 and later, the processing fails:

S1A_IW_GRDH_1SDV_20180313T070201_20180313T070226_020993_0240AE_2C83.zip
S1A_IW_GRDH_1SDV_20180313T070226_20180313T070251_020993_0240AE_07ED.zip
S1A_IW_GRDH_1SDV_20180313T070251_20180313T070318_020993_0240AE_542C.zip

Regards
Josep

1 Like
#2

sorry!!
correction: 20180313 and later…

#3

We are using snap/snappy also to operationally process Sentinel 1 data and we can report the same problem. The problem exists with both snap versions 5 and 6. Of note is that on 13th of March a new Sentinel-1 product format is operational… see also

https://earth.esa.int/web/sentinel/news/-/asset_publisher/xR9e/content/sentinel-1-new-product-format-operational-on-13-march-2018?redirect=https%3A%2F%2Fearth.esa.int%2Fweb%2Fsentinel%2Fnews%3Fp_p_id%3D101_INSTANCE_xR9e%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_count%3D1

This product change is most likely responsible for the snap failure. Is there a fix already released or is it scheduled to be released any time soon?

Best,
Panagiotis

#4

Hi @marpet,

Hows gone.

We faced the same problem and may I provide some more information.

java.lang.NullPointerException
org.esa.snap.core.gpf.OperatorException: java.lang.NullPointerException
        at org.esa.snap.engine_utilities.gpf.OperatorUtils.catchOperatorException(OperatorUtils.java:432)
        at org.esa.s1tbx.calibration.gpf.Sentinel1RemoveThermalNoiseOp.initialize(Sentinel1RemoveThermalNoiseOp.java:140)
        at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:486)
        at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:273)
        at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:387)
        at org.esa.snap.core.gpf.main.CommandLineTool.runOperator(CommandLineTool.java:306)
        at org.esa.snap.core.gpf.main.CommandLineTool.runGraphOrOperator(CommandLineTool.java:284)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:188)
        at org.esa.snap.core.gpf.main.CommandLineTool.run(CommandLineTool.java:121)
        at org.esa.snap.core.gpf.main.GPT.run(GPT.java:54)
        at org.esa.snap.core.gpf.main.GPT.main(GPT.java:34)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.esa.snap.runtime.Launcher.lambda$run$14(Launcher.java:55)
        at org.esa.snap.runtime.Engine.runClientCode(Engine.java:189)
        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(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:62)
        at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:57)

Here are the exceptions we got. Would you mind have a look of this? Danke sehr.

#5

Good to know. We are facing the same problems during ThermalNoiseRemoval

#6

I have the same problem…

Obviously, the error was created after the release of the new S1 format.
How to solve this?

#7

Is it possible that Slice Assembly does not need to be more preprocessing? Now I’ve done and all the tiles are well connected.

#8

Hi there,
So I got in the same problem in my pre-processing (Thermal noise removal). Do you mean that these newer images/files do not need any Thermal Noise Removal pre-processing at all and I have to skip this process for the images after mid-march 2018?
Thanks for your reply in advance

#9

No, it means that you have to update SNAP and use it to pre-process your data (Thermal Noise Removal) from before the 13th of March using this new version.

#10

Hey,
I got the same problem.
I’m processing Sentinel-1 images and calibration, subset, speckle-filter and terrain correction are successfully done, but the last operator which is Slice Assembly throws:

RuntimeError: org.esa.snap.core.gpf.OperatorException: java.lang.NullPointerException

What is the cause and how to solve? Am I setting the wrong order of operators?

#11

Input for the slice assembly operator are consecutive S-1 slices. If the “subset” in your processing is “spatial” it might be a problem.

#12

I rearranged the order of the processes and it works fine. It has to do something with the subset probably.

#14

Have you guys find any solution to this error? While doing Slice assembly?