-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] geo2rdr did not converge
for GMAO - think it's about Availability?
#488
Comments
Here are the failed jobs for reference (there are 3 / 18 submitted that failed):
|
It is easy to get the relevant GUNW (without tropo) from the failed jobs. Replace the
|
I think the orbits and SLC seems to overlap. @jlmaurer we might need to have a debug look at it? |
Yeah, this is more nefarious than the availability unfortunately. Possibly related to the padding of the orbit file, although the specific bug is:
|
This bug is indeed related to the padding parameter (which slices the state vectors in the orbit file around the GUNW reference UTC time). If extra padding is used (>41 minutes; the default is 10 minutes) then geo2rdr converges. @piyushrpt could you help us understand what's happening here? |
@bbuzz31 - looks like it's happening near a midnight crossing (or maybe I am just being Mr. Obvious) - might be helpful to see if that has something to do with it either requesting data within Raider, insider Raider's processing with ISCE3, or even ISCE3 itself. I know @rzinke had issue with Tibet AOIs in ISCE2 due to the midnight crossing. Maybe it is similar. |
I specifically selected this sample due to its midnight crossing ;) FYI - Thanks, Rob! |
@cmarshak yeah this may have something to do with it... did any of the 15 that succeeded have a midnight crossing? |
If 10 minutes around the reference time in insufficient, I would check the source granule. With SAR, time is same as spatial extent - i.e, where the satellite is looking. If it fails to converge with the right time window - it probably means that the assigned reference time is off or that when building the orbit data structure wrong times are being assigned to the state vector. |
Thank youk @piyushrpt - Brett, do not use the GUNW name for date and time, use the source granule for date/time. We can fix the GUNW name (where you are looking) but that will not solve the problem for older products (lots over Tibet with midnight crossing). There will one SLC in reference and secondary to get data you need. That will be sufficient. Here is the issue above using the first failed job. gunw_path = 'S1-GUNW-D-R-048-tops-20230106_20221214-000000-00090E_00040N-PP-c254-v2_0_6.nc' The first date is
Use the SLC id to figure out date and time together. https://github.com/dbekaert/RAiDER/blob/dev/tools/RAiDER/aria/prepFromGUNW.py#L65-L75 |
So we can fix GUNW to be center date as well as center time (the former is earliest date). Here is the issue we are seeing:
Outputs
The first date is the reference date (start) and the latter is the acq time (center). They are in different dates. So raider is thinking the acq is 24 hours earlier than it should be. This would be fixed if (a) GUNW had both as center or (b) this datetime is read using SLC IDs - you only need one reference and one secondary granule to get the orbit datetimes you need. We will do the fix for (a) but to ensure its correct for older GUNWs - please read the SLC id. This is thanks to @dbekaert. |
For everyone's knowledge, I updated the Hyp3 Plugin that generates gunw so the final id of this product would be something like Here is the PR: ACCESS-Cloud-Based-InSAR/DockerizedTopsApp#112 |
Fixed in #500 |
Describe the bug
This is related to hyp3 deployment and the current script to update GUNWs.
Could be potentially very simple, i.e. due to the fact that the reference date is
20230106
and GMAO is not available. If such is the case, may be helpful to create slightly better error message here.Here is the job dict:
The log (as above) is here: https://hyp3-a19-jpl-contentbucket-1wfnatpznlg8b.s3.us-west-2.amazonaws.com/5225cd05-0869-4031-a697-15778a29635f/5225cd05-0869-4031-a697-15778a29635f.log
The GUNW is here (without tropo layer): https://hyp3-a19-jpl-contentbucket-1wfnatpznlg8b.s3.us-west-2.amazonaws.com/5225cd05-0869-4031-a697-15778a29635f/S1-GUNW-D-R-048-tops-20230106_20221214-000000-00090E_00040N-PP-c254-v2_0_6.nc
So using the GUNW, this script could be re-run.
To Reproduce
Steps to reproduce the behavior:
See ASFHyP3/hyp3#1416 for exactly how raider is called.
The text was updated successfully, but these errors were encountered: