Forum

Hmm, I have a couple ideas that might resolve this issue.The newest build of OCSSW reorganized things a bit. Therefore, try running: which val_extractIt should point to: ~/seadas-7.4/ocssw/bin/val_extract instead of the old version: ~/seadas-7.4/ocssw/run/bin/linux_64/val_extractWhen you ran ~/seada...

Hi Catherine,I'm sorry that you are still experiencing difficulties with val_extract. Both methods that you described to update OCSSW in SeaDAS (GUI and command-line) are valid. Are you by any chance running on a Mac operating system instead of Linux?It appears that the Linux binaries have been ...

Hi,The val_extract binary has been updated in the latest version of SeaDAS via its copy of OCSSW. To get the mk_matchup.py script to work, you will need to update your local val_extract binary to the latest public version, which should be: val_extract=2.6.2 and val_extract-main=1.3.1.To do so, pleas...

Hi,Thank you for using the satellite-to-in-situ match-up scripts! The error you are seeing is due to the date and time information not appearing in the data matrix section of your SeaBASS file. You are correct that you file has date and time information in the metadata header, but these match-up too...

Hi Catherine,I believe that version difference is the source of the problem. However, I double-checked and val_extract version 2.5.9 is, in fact, the latest publicly available version of val_extract, which is due to a bug on our end.We will push an updated version of the val_extract binaries to the ...

Hi,Thank you for checking out the new stand-alone match-up tools, and I apologize that you are getting an error using mk_matchup.py.From the mk_matchup.py output you are providing, it sounds like your copy of SeaDAS and its OCSSW components may be an outdated version of the val_extract binary that i...