Multiples problems with Coregistration function

Hello everyone,

I had some problems trying to coregister 2 S1GRD data recently. I haven’t had time to check the forum to see if these problems have been reported before and apologise in advance if they have.

First of all, when I coregistered my two pieces of data conventionally (Radar/Coresgitration/Coregistration function), I got two blank results (no problem of space on my computer, SNAP up to date…). I know that this problem is recurrent and can have multiple origins, so I won’t dwell on it. What’s more, using the following graph and the graph builder, I get a correct result.

Coregistration.xml (4.2 KB)

Secondly, the option initially proposed for Resampling Type in Create Stack is NONE, which causes an Error org.jblas;NativeBlas… I think that for the sake of clarity, it would be a good idea to propose another base method (preferably Nearest Neighbour, as this option doesn’t physically change the image).

Thirdly, I’ve observed the opposite phenomenon with Warp’s Show Residuals. If this is not ticked VS code opens the residual during the process, and if I tick it it doesn’t open it for me.

Fourthly, using the graph provided in Problem 1, I obtain the following results:

Master :

Slave :

My problem is as follows: the resampling has obviously not been carried out with a Nearest Neighbour, as the Slavic image seems “filtered” and I have negative values as shown in the Colour Editor… I imagine that a default value bypasses the user’s selection.

I would be happy to provide you with more information, and if I get some time I will take a look at the Git codes to try to understand the origines of these problems.

Have a good day,

Nathan Paillou

Trying to study a bit more this problem, I discovered an other issue. As I explained I have negatives value in my slave image. But when I use the “Linear to/from dB function”, these negatives values (x) are transformed to the dB values of the corresponding positive values (10*log10(-x)), instead of NaN. I think it is something which should be corrected.

@jun_lu can you have a look at this?

A JIRA ticket ([SNAP-3581] - JIRA) has been created to track the problem. We will look into it and than you for reporting the issue.

1 Like

Ok thanks a lot, don’t hesitate to contact me if you need more details/analysis !