-
Notifications
You must be signed in to change notification settings - Fork 36
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
Reject products with missing expected layers #382
Conversation
@sssangha interesting as I've processed thousands of ifgs over the East Coast and have not hit this. Are you certain it's not unique to this ifg / frame? |
The product you mentioned was processed during earlier validation and testing this year. Please filter these out. I think we must have a small handful that were delivered to UAT as a test and/or by accident. This is a good thing to keep in mind. Sorry for this extra overhead. You can filter out using ASF metadata as indicated below, use products that were processed/generated in the last week.
Note the processing date of this problematic product. Also, regarding the spatial issue, note that the product doesn't have a frame number in the json umm metadata accessed via
The products that were meant to be there will have If there are a number of products, we can chat, but I would filter out by processing date. You could probably use ASF search directly using one of the keyword arguments directly. I definitely did several hyp3 tests over one of the Los Angeles tracks. I can't imagine there are more than a handful of products because the tests were done without UAT delivery, I think. If there are more, please let us know. Will be good to have an idea when we officially deliver them to the DAAC. |
In cases where there are multiple scenes for a given pair and at least one has missing expected layers, then this leads to a crash later when the program attempts to sort the dictionary of products.
Specifically, compare this product with missing tropo/SET/iono layers:
vs this overlapping product with all expected layers available:
Downstream sorting of these products for the same IFG leads to this error (note e.g. the eroneous assignment of the
productBoundbox
layer to thesolidEarthTide
in the absence of asolidEarthTide
layer for this product):