OSTIA L4 Gobal MD5 CheckSum Error

OSTIA L4 Gobal MD5 CheckSum Error

Postby ncms_avmet » Tue Nov 05, 2019 10:20 pm

Hello All,

I am struggling with an issue where the MD5 file for the L4 global data file for UKMO OSTIA data file does not compare with a local MD5 output of the file downloaded. I am doing this for sanity check of the downloaded file.

The process I use works without any trouble with the MUR and OUR_OCEAN data-sets, so there is no issues in my script, unless the MD5 for OSTIA is calculated differently.

Any thoughts are appreciated,
Best Regards,
Greg
ncms_avmet
 
Posts: 2
Joined: Tue Nov 05, 2019 9:00 pm

Re: OSTIA L4 Gobal MD5 CheckSum Error

Postby yiboj » Sun Nov 10, 2019 1:19 pm

Hi Greg,
Thanks for your inquiry.
The checksum is mainly used to make sure no error when we ingest the data from provider to our system. You may just removed the remote file path "/critical/fpos2/cylc-run/mi-ay290/share/cycle/" in the UKMO OSTIA md5 file and it should work. PLease try and let us know.
Regards,
-PODAAC DE
yiboj
 
Posts: 96
Joined: Mon Mar 30, 2015 11:22 am

Re: OSTIA L4 Gobal MD5 CheckSum Error

Postby ncms_avmet » Mon Nov 11, 2019 7:28 pm

Hello PODAAC,

Thank you for spending the time looking at this.

I have found the extra path; this path is not present in the MD5 file for MUR and OUR_OCEAN data sets.

I manually removed the path as a test and the compare is successful.

Regards,
Greg
ncms_avmet
 
Posts: 2
Joined: Tue Nov 05, 2019 9:00 pm


Return to Data Access