-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test SWOT 2.0 collections with L2ss-py service #51
Comments
@davidcolemanjpl please test these collections in HiTIDE UI or directly with harmony (test both l2ss-py and concise). ** Test in UAT only ** Also some collections are getting renamed. Refer to this for the new names: Thanks! |
Note: SIDE Observation SWOT_L2 collection are not currently visible in EDSC (UAT): SWOT_L2_NALT_GDR_GDR_2.0 - Unable to locate collection in EDSC - 0 Matching Collections SWOT_L2_NALT_GDR_SGDR_1.0 = C1256783374-POCLOUD - (Unable to currently locate collection in EDSC) |
@davidcolemanjpl yeah some of them might not be ready. Can you put results with the ones that actually do work? Good idea to test in EDSC. Thanks! |
HiTIDE UI (UAT) v4.17.0-RC.6 Test with l2ss-py service: |
L2SS-py v2.8.0rc3 SWOT_L2_NALT_GDR_GDR_2.0 (Test directly through harmony or data-subscriber) - Unable to currently locate collection in EDSC - 0 Matching Collections (C1256783373-POCLOUD) SWOT_L2_NALT_GDR_SGDR_2.0 (Test directly through harmony or data-subscriber) - (C1261072651-POCLOUD) SWOT_L2_NALT_GDR_SSHA_2.0 (Test directly through harmony or data-subscriber) - (C1261072652-POCLOUD) SWOT_L2_NALT_IGDR_GDR_2.0 (Test directly through harmony or data-subscriber) (C1261072654-POCLOUD) SWOT_L2_NALT_IGDR_SGDR_2.0 (Test directly through harmony or data-subscriber) (C1261072655-POCLOUD) SWOT_L2_NALT_IGDR_SSHA_2.0 (C1261072656-POCLOUD) SWOT_L2_NALT_OGDR_GDR_2.0 (C1261072658-POCLOUD) SWOT_L2_NALT_OGDR_SSHA_2.0 (C1261072659-POCLOUD) SWOT_L2_RAD_GDR_1.0 (C1261072660-POCLOUD) SWOT_L2_RAD_IGDR_2.0 (C1261072661-POCLOUD) SWOT_L2_RAD_OGDR_2.0 (C1261072662-POCLOUD) SWOT_L2_LR_SSH_BASIC_2.0 (C1261072645-POCLOUD) SWOT_L2_LR_SSH_EXPERT_2.0 (C1261072646-POCLOUD) SWOT_L2_LR_SSH_WINDWAVE_2.0 (C1261072648-POCLOUD) |
@davidcolemanjpl there was some renaming of collections and stuff when you did that last test so the results may be bad. It should be ironed out now. |
Re-TEST: SWOT_L2_LR_SSH_BASIC_2.0 (C1261072645-POCLOUD) related data subscriber issue: UPDATE(030824): SWOT_L2_LR_SSH_BASIC_2.0 (C1261072645-POCLOUD) note: Harmony - request works okay, L2SS-Py step(s) succeeds in Harmony UAT when the subset=lon info removed from API request: SWOT_L2_LR_SSH_EXPERT_2.0 (C1261072646-POCLOUD) note: the Harmony - request still FAILs - the L2SS-Py step(s) failed in Harmony UAT when the subset=lon (and/or subset=lat) info removed from request: (See Job Statuses: https://harmony.uat.earthdata.nasa.gov/jobs/3cc72a0f-244e-43e8-a9eb-9e80df90726c or https://harmony.uat.earthdata.nasa.gov/jobs/1baf824d-8d11-4830-8cec-72a4b2cd92a5) SWOT_L2_LR_SSH_WINDWAVE_2.0 (C1261072648-POCLOUD) |
L2SS-py v2.9.0rc3 SWOT_L2_LR_SSH_BASIC_2.0 (C1261072645-POCLOUD) Harmony (UAT) - request - FAIL - L2SS-py step did not succeed in Harmony UAT (see Harmony Job status: https://harmony.uat.earthdata.nasa.gov/jobs/8f28329f-9207-4388-b38f-45c582efe11a) note: Harmony - request works okay (PASSED), the L2SS-Py steps were successful in Harmony UAT when the subset=lon info was removed from API request: SWOT_L2_LR_SSH_EXPERT_2.0 (C1261072646-POCLOUD) Harmony - request - FAIL - L2SS-py steps do not succeed in Harmony UAT see Harmony Job status: https://harmony.uat.earthdata.nasa.gov/jobs/67da5d3d-8459-425f-87a1-857507d8db3f SWOT_L2_LR_SSH_WINDWAVE_2.0 (C1261072648-POCLOUD): Harmony-request - FAIL - L2SS-py step does not succeed in Harmony UAT as expected : (see recent Harmony Job Statuses: https://harmony.uat.earthdata.nasa.gov/jobs/61488a2a-8a2a-4e4f-b8bb-7c41533a8070 or https://harmony.uat.earthdata.nasa.gov/jobs/1e30e025-213d-4e04-b34e-b5a0a8c7c907 ) see related test case: |
L2SS-py v2.9.0rc3 SWOT_L2_NALT_GDR_GDR_2.0 - (C1261072650-POCLOUD) SWOT_L2_NALT_GDR_SGDR_2.0 - (C1261072651-POCLOUD) SWOT_L2_NALT_GDR_SSHA_2.0 - (C1261072652-POCLOUD) SWOT_L2_NALT_IGDR_GDR_2.0 - (C1261072654-POCLOUD) SWOT_L2_NALT_IGDR_SGDR_2.0 - (C1261072655-POCLOUD) SWOT_L2_NALT_IGDR_SSHA_2.0 - (C1261072656-POCLOUD) SWOT_L2_NALT_OGDR_GDR_2.0 (C1261072658-POCLOUD) SWOT_L2_NALT_OGDR_SSHA_2.0 (C1261072659-POCLOUD) SWOT_L2_RAD_GDR_2.0 (C1261072660-POCLOUD) SWOT_L2_RAD_IGDR_2.0 (C1261072661-POCLOUD) SWOT_L2_RAD_OGDR_2.0 (C1261072662-POCLOUD) see related test case: |
Hi @davidcolemanjpl Looks like you made good progress here. Nice! It could be helpful to see all this in a table. Like have each collection listed and for each environment tested have a cell for each data subscriber, data-downloader, harmony, hitide, l2ss, concise, thumbnails, footprints, info, etc so we can see exactly which still need work. |
Hi @davidcolemanjpl. We updated l2ss-py in UAT so you could try some of your failed UAT tests again. |
L2SS-py v2.10.0rc4 - UAT When re-testing SWOT_L2 collections that previously failed tests in Harmony UAT env, user received error results as before: E.g.,
note: when user attempted to remove the time parameter from the CMR request, also received error : {
Harmony-request - FAIL - L2SS-py step does not succeed in Harmony UAT as expected :
podaac-data-subscriber - FAIL - see Harmony job status: https://harmony.earthdata.nasa.gov/jobs/5f65f5db-96f7-4085-ad02-a817cd7d5794 NOTE: the Harmony UAT Request succeeded when using following request (25 granules): https://harmony.uat.earthdata.nasa.gov/C1261072646-POCLOUD/ogc-api-coverages/1.0.0/collections/all/coverage/rangeset?forceAsync=true&subset=lat(34.84931%3A35.83342)&subset=time(%222020-01-01T18%3A00%3A00%2B00%3A00%22%3A%222024-12-21T07%3A00%3A00%2B00%3A00%22)&skipPreview=true |
UAT
|
OPS
|
I have ran some of these swot collections and some granules succeed and some fails, what i notice is that those that fails also have a bounding box. So most likely is that the data being subsetted isn't falling in the bounding box and creates an empty granule. Although it still subset the resulting granule seem to make harmony throw an error. Will talk to harmony to see why that is . |
Hi @davidcolemanjpl |
OPS
podaac-data-subscriber - PASS ( see job status https://harmony.earthdata.nasa.gov/jobs/6df1d4b1-5da6-4b3d-8904-b578e631939a) Harmony - API request - FAIL - (see job status https://harmony.earthdata.nasa.gov/jobs/c2f20760-20e9-46df-9288-1e59f480cb6d) - 10 of 43 granules failed subsetting (note: same results occur if/ when using a curl request and submitting to Harmony) UAT
note: Harmony - API request works okay for SWOT_L2_LR_SSH_BASIC_2.0, L2SS-Py steps were successful in Harmony UAT when the subset=lon info removed from Harmony API request: |
Hi @davidcolemanjpl we made a new release of l2ss-py 2.11.0 and concise 0.9.0. |
@davidcolemanjpl can you update this table with your results too? |
L2SS-Py - v2.11.0 / CONCISE v0.9.0 UAT L2SS-Py v2.11.0rc9 / CONCISE v0.9.0rc5 (v0.10.0rc2) SWOT_L2_LR_SSH_BASIC_2.0 (C2799465428-POCLOUD): - OPS SWOT_L2_LR_SSH_BASIC_2.0 (C1261072645-POCLOUD) - UAT SWOT_L2_LR_SSH_WINDWAVE_2.0 (C2799465507-POCLOUD): Harmony - request - PASS - (see job status https://harmony.earthdata.nasa.gov/jobs/561c03e4-93b6-4795-abef-770f813220a0) SWOT_L2_LR_SSH_WINDWAVE_2.0 (C1261072648-POCLOUD) - UAT SWOT_L2_NALT_GDR_GDR_2.0 (C2799465509-POCLOUD): Harmony - request - PASS - (see job status https://harmony.earthdata.nasa.gov/jobs/bf163e41-4762-4537-b3c3-23de6d47f623) SWOT_L2_NALT_GDR_GDR_2.0 (C1261072650-POCLOUD) - UAT SWOT_L2_NALT_GDR_SGDR_2.0 (C2799465518-POCLOUD) - OPS podaac-data-subscriber - PASS (see https://harmony.earthdata.nasa.gov/jobs/e6e280e5-acad-486e-bdf6-9d0e9e652f8a) SWOT_L2_NALT_GDR_SGDR_2.0 (C1261072651-POCLOUD) - UAT SWOT_L2_NALT_GDR_SSHA_2.0 (C2799465522-POCLOUD: SWOT_L2_NALT_GDR_SSHA_2.0 (C1261072652-POCLOUD) - UAT SWOT_L2_NALT_IGDR_GDR_2.0 (C2799465526-POCLOUD): SWOT_L2_NALT_IGDR_GDR_2.0 (C1261072654-POCLOUD) - UAT SWOT_L2_NALT_IGDR_SGDR_2.0 (C2799465529-POCLOUD) SWOT_L2_NALT_IGDR_SGDR_2.0 (C1261072655-POCLOUD) - UAT SWOT_L2_NALT_IGDR_SSHA_2.0 (C2799465538-POCLOUD) SWOT_L2_NALT_IGDR_SSHA_2.0 (C1261072656-POCLOUD) - UAT SWOT_L2_NALT_OGDR_GDR_2.0 (C2799465542-POCLOUD) - OPS SWOT_L2_NALT_OGDR_GDR_2.0 (C1261072658-POCLOUD) - UAT SWOT_L2_NALT_OGDR_SSHA_2.0 (C2799465544-POCLOUD) - OPS SWOT_L2_NALT_OGDR_SSHA_2.0 (C1261072659-POCLOUD) - UAT NOTE: UAT CONCISE updated to version 0.10.0rc2 during testing. SWOT_L2_RAD_GDR_2.0 (C2799438350-POCLOUD) SWOT_L2_RAD_GDR_2.0 (C1261072660-POCLOUD) SWOT_L2_RAD_IGDR_2.0 (C2799438351-POCLOUD) - OPS SWOT_L2_RAD_IGDR_2.0 (C1261072661-POCLOUD) - UAT SWOT_L2_RAD_OGDR_2.0 (C2799438353-POCLOUD) - OPS SWOT_L2_RAD_OGDR_2.0 (C1261072662-POCLOUD) - UAT |
@davidcolemanjpl can you include the failed harmony api request fails, the job status or the harmony api call itself, i can't tell what service is failing with the "Error: No matching granules found." |
looks like the longitude and latitude search yields 0 granules in that space so there is nothing to subset or concatenate, if you used a wider search for longitude and latitude could get something |
Test with l2ss-py service:
SWOT_L2_LR_SSH_BASIC_2.0 (Test subset and merge/concise in HITIDE-UI)
SWOT_L2_LR_SSH_EXPERT_2.0 (Test subset and merge/concise in HITIDE-UI)
SWOT_L2_LR_SSH_WINDWAVE_2.0 (Test subset and merge/concise in HITIDE-UI)
SWOT_L2_NALT_GDR_GDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_GDR_SGDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_GDR_SSHA_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_IGDR_GDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_IGDR_SGDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_IGDR_SSHA_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_OGDR_GDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_NALT_OGDR_SSHA_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_RAD_GDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_RAD_IGDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
SWOT_L2_RAD_OGDR_2.0 (Test with EDSC, or directly through harmony or data-subscriber)
The text was updated successfully, but these errors were encountered: