Mission RS2 is currently not supported for calibration

When i used Graph Builder to calibrate Radarsat2 data, I ran into an error as it says:
'[NodeId:Calibration] Mission RS2 is currently not supported for calibration.


It occurs when the sentinel-1 tool box was updated to version 7.0.3.
Is there a bug?

Im running into the same error. I also have version 7.0.3 for the s1 toolbox and version 7.5.3 for the Radarsat-2 toolbox.
Regards,
Thijs

The Error Details:

org.esa.snap.core.gpf.OperatorException: Mission RS2 is currently not supported for calibration.
at org.esa.s1tbx.calibration.gpf.support.CalibrationFactory.createCalibrator(CalibrationFactory.java:39)
at org.esa.s1tbx.calibration.gpf.CalibrationOp.initialize(CalibrationOp.java:134)
Caused: org.esa.snap.core.gpf.OperatorException: Mission RS2 is currently not supported for calibration.
at org.esa.snap.engine_utilities.gpf.OperatorUtils.catchOperatorException(OperatorUtils.java:440)
at org.esa.s1tbx.calibration.gpf.CalibrationOp.initialize(CalibrationOp.java:161)
at org.esa.snap.core.gpf.internal.OperatorContext.initializeOperator(OperatorContext.java:507)
at org.esa.snap.core.gpf.internal.OperatorContext.getTargetProduct(OperatorContext.java:294)
at org.esa.snap.core.gpf.Operator.getTargetProduct(Operator.java:387)
at org.esa.snap.core.gpf.GPF.createProductNS(GPF.java:330)
at org.esa.snap.core.gpf.GPF.createProduct(GPF.java:305)
at org.esa.snap.core.gpf.GPF.createProduct(GPF.java:284)
at org.esa.snap.graphbuilder.rcp.dialogs.SingleOperatorDialog.createTargetProduct(SingleOperatorDialog.java:175)
[catch] at org.esa.snap.graphbuilder.rcp.dialogs.SingleOperatorDialog.onApply(SingleOperatorDialog.java:287)
at org.esa.snap.ui.AbstractDialog.lambda$initUI$6(AbstractDialog.java:519)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

I have tried the same graph with SNAP v7.0 and a RS2 SLC product and did not get any problem

What about your plugins version?
I can do the calibration before updating the plugins also, and failed after the update.
Should I reinstall SNAP?

Just updated all plugins with the latest version and still have no problem in running calibration operator with RS2 SLC product. You can try to reinstall SNAP to see if that helps

I reinstalled SNAP and updated all plugins, but it doesn’t help.
The error is:


In addition, the data were acquired from 2012 to 2015.
The product metadata is here : product.xml (211.6 KB)

Do you have the “Polarimetric” item in the Radar menu in your SNAP?

Yes.Snipaste_2020-07-22_03-00-02

Then you have the calibrator. Can you open your product in SNAP and check the “MISSION” in the Abstracted metadata to see if it is “RS2”?

Yes, it is.

Then you should be able to do the calibration. I am confused. What I can suggest now is, go to http://step.esa.int/main/download/snap-download/ and download SNAP v7.0 and try it again. It works for me

I tried as you said. Still failed :pensive:.

I have the same problem! A month ago the calibration worked for me without any problem. When I now try to run the same raw data and same xml processing graph as I used before, I receive the error ‘mission RS2 is currently not supported for calibration’.

Please let me know if you have found any solution :slight_smile:

Perhaps something broke in the latest S1TBX update? @jun_lu

+1
I guess so.

Uninstall, then install the SNAP v7.0 from http://step.esa.int/main/download/snap-download/ and DON’T update the plugins/toolboxs.

I had the same problem and I actually rolled my snap version back to snap 7.0.0, created a completely new installation without updating any of the toolboxes. Now I can perform the calibration again. So it is definitely linked to the versions after 7.0.2

I can confirm that this was broken for me in the latest update as well.

@mengdahl @jun_lu - is there any information I can provide that might help track this down?

I have the same problem and with the latest update it broke. Will this be fixed soon?