search

cgi-estonia-space / ALUs

GPU accelerated earth observation data processors
https://twitter.com/spacest372
GNU General Public License v3.0
23 stars 3 forks source link

S1 GRD thermal noise removal error #37

Open bjoern234 opened 1 year ago

bjoern234 commented 1 year ago

Hi, I've tested your S1 GRD calibration routine which in general works well. But in some cases, I've got an error during the thermal noise removal procedure:

[2023-06-11 14:02:20.028403] [0x00007f96c7ab0000] [info]    Processing parameters:
Input product - 
/tmp/S1B_IW_GRDH_1SDV_20190405T230644_20190405T230711_015678_01D696_7102.SAFE
Subswath -
Polarisation - VV
Calibration type - sigma
First burst index - 0
Last burst index - 0
AOI -
Write intermediate files - NO

[2023-06-11 14:02:20.805075] [0x00007f96c7ab0000] [info]    Using 'NVIDIA GeForce GTX 1080 Ti' device nr 0 for calculations
[2023-06-11 14:02:20.828726] [0x00007f96c7ab0000] [info]    Target bands count: 1
[2023-06-11 14:02:20.828740] [0x00007f96c7ab0000] [info]    Processing band Amplitude_VV_VV

[2023-06-11 14:02:34.663293] [0x00007f96c7ab0000] [error]   Caught an exception
There were no matching noise values from noise vectors for azimuth range [7034.963325, 7034.963331]. Tile properties x:16384 y:16384 w:2048 h:1756
[2023-06-11 14:02:34.663311] [0x00007f96c7ab0000] [error]   Exiting.

Thank you! Bjoern

kautlenbachs commented 11 months ago

Yes, it is the same as - https://github.com/cgi-estonia-space/ALUs/issues/39 When I eventually implemented it, the range matching was implemented strictly. SNAP simply takes the last noise vector if azimuth range goes out of the bounds of the metadata noise vectors. This one needs a little investigation, since I am not sure that this might be the correct solution, but for the sake of making it work the "fix" could be easy one liner.