Topographic Phase Removal Error

A problem occurred during the target product initialisation.
Type: OperatorException
Message: [slvProductName] is null

Does anyone know what to do?

Same problem with a newly upgraded SNAP (8.0.4)
GPT=(HOME)/snap/bin/gpt (GPT) TopoPhaseRemoval -SsourceProduct=target_deburst.dim -PdemName=“SRTM 3Sec” -t target_topo.dim -c 2048M -q 2
following split > orbit > back geocoding > ESD > interferometry > deburst:

Error: [slvProductName] is null

with the long dump ending with
Caused by: java.lang.IllegalArgumentException: [slvProductName] is null
at org.esa.snap.core.util.Guardian.assertNotNull(
at org.esa.snap.engine_utilities.gpf.StackUtils.saveSlaveProductBandNames(
at org.jlinda.nest.gpf.SubtRefDemOp.createTargetProduct(
at org.jlinda.nest.gpf.SubtRefDemOp.initialize(
… 24 more

This same area was already processed many times so I do not believe it is an issue with SRTM 3Sec tile (SNAP issue 1439 ?).

@Reelle: your screenshot looks like parts of the interferogram are missing. You have combined Sentinel-1A and B which are often shifted along track so the number of bursts differ. Please first compute a stack where all bursts are covered by both dates. Otherwise, the subsequent tasks can fail.

My issue was tracked to insufficient memory: random errors seemed to appear on the 12-GB RAM laptop I was running the processing on. Installing SNAP/gpt on a 64-GB RAM computer seems to allow completing all processing flawlessly. Apologies for the noise then.

Hello, I also have same problem. After some testing, I found this problem happened using s1tbx Version 8.0.4 with some special S-1 interferogram. Here is my testing:

  1. Input S-1 single swath interferogram to [Topographic Phase Removal]
    v8.0.1-> Successful
    v8.0.4-> Successful

  2. Input S-1 multi swath merge interferogram to [Topographic Phase Removal]
    v8.0.1-> Successful
    v8.0.4-> Error

Following is the error message:
java.lang.IllegalArgumentException: [slvProductName] is null
at org.esa.snap.core.util.Guardian.assertNotNull(
at org.esa.snap.engine_utilities.gpf.StackUtils.saveSlaveProductBandNames(
at org.jlinda.nest.gpf.SubtRefDemOp.createTargetProduct(
at org.jlinda.nest.gpf.SubtRefDemOp.initialize(
Caused: org.esa.snap.core.gpf.OperatorException: [slvProductName] is null
at org.jlinda.nest.gpf.SubtRefDemOp.initialize(
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(
at org.esa.snap.core.gpf.Operator.getTargetProduct(
at org.esa.snap.core.gpf.GPF.createProductNS(
at org.esa.snap.core.gpf.GPF.createProduct(
at org.esa.snap.core.gpf.GPF.createProduct(
at org.esa.snap.graphbuilder.rcp.dialogs.SingleOperatorDialog.createTargetProduct(
[catch] at org.esa.snap.graphbuilder.rcp.dialogs.SingleOperatorDialog.onApply(
at org.esa.snap.ui.AbstractDialog.lambda$initUI$6(
at javax.swing.AbstractButton.fireActionPerformed(
at javax.swing.AbstractButton$Handler.actionPerformed(
at javax.swing.DefaultButtonModel.fireActionPerformed(
at javax.swing.DefaultButtonModel.setPressed(
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(
at java.awt.AWTEventMulticaster.mouseReleased(
at java.awt.Component.processMouseEvent(
at javax.swing.JComponent.processMouseEvent(
at java.awt.Component.processEvent(
at java.awt.Container.processEvent(
at java.awt.Component.dispatchEventImpl(
at java.awt.Container.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.LightweightDispatcher.retargetMouseEvent(
at java.awt.LightweightDispatcher.processMouseEvent(
at java.awt.LightweightDispatcher.dispatchEvent(
at java.awt.Container.dispatchEventImpl(
at java.awt.Window.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.EventQueue.dispatchEventImpl(
at java.awt.EventQueue.access$500(
at java.awt.EventQueue$
at java.awt.EventQueue$
at Method)
at java.awt.EventQueue$
at java.awt.EventQueue$
at Method)
at java.awt.EventQueue.dispatchEvent(
at org.netbeans.core.TimableEventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForFilters(
at java.awt.EventDispatchThread.pumpEventsForFilter(
at java.awt.EventDispatchThread.pumpEventsForHierarchy(
at java.awt.EventDispatchThread.pumpEvents(
at java.awt.EventDispatchThread.pumpEvents(

1 Like

Hello, after some surveys, I found that one of the slave metadata doesn’t be updated after [Interferogram] step, which caused SNAP can’t find correspond band as input in [Topographic Phase Removal], after manually modifying the value, I can successfully finish [Topographic Phase Removal] step.

The xml node of the metadata is

Dimap_Document → Dataset_Sources → MDElem name=“metadata” → MDElem name=“Slave_Metadata” → MDElem name=“S1B_IW_SLC__xxxxx” → MDATTR name=“Slave_bands”

The correct value of this node after [Interferogram] step should all be like:
i_ifg_VV_12Jul2020_18Jul2020 q_ifg_VV_12Jul2020_18Jul2020 Phase_ifg_VV_12Jul2020_18Jul2020 coh_VV_12Jul2020_18Jul2020

but in the metadata of product encountering this problem, only the first slave had correct value, the others would be like:

i_IW1_VV_slv2_24Jul2020 q_IW1_VV_slv2_24Jul2020

Also, this node value seems not impact s1tbx version 8.0.1 and before, the product with incorrect value still can finish [Topographic Phase Removal] step in old version SNAP.

1 Like

hi everyone
i am having the same problem.
i am running steps of gpt via python with the goal of having a script to do interferogram on mass - long story - another time…

after interferogram and deburst steps seems to work fine…
i tried running this within snap (8.0.4), both graph and menu (just in case) and i get the above error.

i understand im not alone here but how do i fix this?

many thanks in advance

several errors are reported in this topic, can you please specify your problem?

hi abraun
thanks for getting back to me so quickly its been driving me crazy… :slight_smile:

ok from what i can tell - its the same as what Topographic Phase Removal Error is reporting

i have run the following: split, orbit, backgeocoding, esd, interferogram, deburst but when i try to do the tpr (topo phase removal) i get the [slvProductName] is null error… just like Jmfriedt above (if you ask me - his/hers problem swas solved by installing a different version - not the size of the computer)…im running all this on a win10 computer with 128g ram and 12 cores. i am using python to edit xml graphs and running them via gpt … my snap is 8.0.5

i tried running (actually its running as i write) the last few steps in snap just to see if it works. i tried earlier but it didn’t work. now i went back to do the steps from interferometry onward to check if the outcome is different (i suspect not)(update - it didnt work). toi that end - i suspect constantinevi is possibly right.

if it is a repeated problem - i am the third in this thread alone - i hope you can advise of a work around or something. right now (hopefully tomorrow) i plan to reinstall an older version of snap and pray to the gods of sentinel …

anyway thanks everyone for sharing hope to broadcast good news to you all soon.


Maybe topographic phase removal was already done in the interferogram operator?
If not, please activate the checkbox and select a suitable DEM so you won’t need the TPR as a separate operation.

hi everyone
so i uninstalled (complete clean etc) snap and reinstalled it (version 8.0.0 i think) and i disabled the automatic updating (which would install the buggy 8.0.5 version) and now everything is working. so! here are the good news i promised. :slight_smile:

still, as per abroun remark:

as it is - tpr wasn’t done in the interferogram opp. it first appears after the tpr run

your second comment is really interesting and important - you mean that if i activate and provide a suitable dem file - tpr will be done within the interferogram stage?
i will try again but previously when i entered a dem it didn’t work, thats why i have gone back to using the srtm… nonetheless - i will check it up and update this forum (but its not going to be immediately - i would like to finish writing and run successfully this version of the code.

many thanks for your advice and support. next bug hurdle - snaphu… anyone exported, run and imported back via python? is there an option doing this with xml graphs?

many thanks

this is not a good idea. Firstly, before you import it back, you have to do the actual unwrapping by calling snaphu. Then a visual check of the result is required, because depending on the number of tiles, the cost mode and the unwrapping method the result can look differently. The import only makes sense if the unwrapping worked fine.

[quote=“divething, post:9, topic:31030”]
just like Jmfriedt above (if you ask me - his/hers problem was solved by installing a different version - not the size of the computer)…[/quote]

I believe you are correct: unlike my 12 GB RAM laptop, the 64 GB RAM desktop is a remote computer with no graphical user interface so that SNAP will not automagically upgrade. I stumbled on the same problem again and downgrading from 8.0.5 to the current archive 8.0 solved the issue.
Actually I just realized while running the processing script with the downgraded version of SNAP that gpt was already complaining

WARNING: org.esa.snap.engine_utilities.gpf.StackUtils: saveSlaveProductBandNames: slvProductName is null

but did not crash as the newer upgrades. The command I use is

$SNAP/gpt TopoPhaseRemoval -SsourceProduct=target_deburst.dim -PdemName=“External DEM” -PexternalDEMFile=“DEM.tif” -PexternalDEMNoDataValue=0.0 -t target_topo.dim