Satellite validation granule locator tool - known issue (fd_matchup.py script)

jpsco · by **jpsco** » Tue Feb 27, 2018 4:42 pm America/New_York

The fd_matchup.py script that is part of the stand-alone satellite match-up tools within OCSSW has a known bug due to a change in the NASA Earthdata Common Metadata Repository (CMR) API.

This bug will prevent satellite granules from being located due to fundamental restructuring of the API's invocation syntax.

Fortunately, a fix has been found, implemented, tested, and will be released publicly in an upcoming OCSSW/SeaDAS version. Until then, we appreciate your patience and acknowledge that this script will not perform as intended.

csprh · by **csprh** » Wed Mar 14, 2018 6:17 am America/New_York

Hi, I noticed this bug yesterday. Do you know if fd_matchup.py has been updated yet?

I think I should be able to re-write the code but if you have done so already then it would save me a lot of time to get your new version

regards

Paul

jpsco · by **jpsco** » Wed Mar 14, 2018 8:24 am America/New_York

Hi Paul,

The code has been fixed and committed to our internal code repository. However, it has not been made available to the public in an official release yet.

You are welcome to adjust to code yourself to correct the bug. Simply do a find-and-replace on the script changing 'entry_title' to 'short_name' in all of the calls to the Earthdata CMR API.

Cheers,
Joel

csprh · by **csprh** » Wed Mar 14, 2018 9:30 am America/New_York

Hi Joel

Thank you so much for this!

I had figured that the CMR had changed as it wasn't outputting any L2 granules when I was debugging fd_matchup. I was close to finding the change that was causing the problem, but now I don't have to spend an afternoon searching through the CMR API man pages.

Thanks again.

Paul