Ocean Color Forum - Not logged in
I recently downloaded SeaDAS 4.8 01 and am trying to run the modis_L0_to_L1A_GEO.csh script on our PDS files. I can get it to work no problem if I change the PDS name to the something like a1.05274.1641.pds, but it will not work if I leave the files in their native naming format of P1540064*001.PDS. When I try to run it on files names that way I get the message:
*** modis_L0_to_L1A_GEO.csh: ERROR: Unable to determine platform from filename.
The filename of the Level L0 PDS file must be in one of the following formats:
Aqua: a1.YYDDD.HHMM.pds or MOD00.PYYYYDDD.HHMM_*.PDS
Terra: t1.YYDDD.HHMM.pds or MOD00.AYYYYDDD.HHMM_*.PDS
The Help notes for this script mention that P1540064* is an acceptable naming convention. It certainly would make things easier if I could keep the files with this naming. Any help would be greatly appreciated!
I think you might be getting our MODISL1DB package mixed up with our SeaDAS package. SeaDAS 4.8 will not allow you to use the P1540064* file naming convention, but the MODISL1DB package will. We added that capability to the MODISL1DB package after we released SeaDAS 4.8. The next release of SeaDAS will have that capability. But for now, you probably want to get the MODISL1DB package if you really want to keep that naming convention:http://oceancolor.gsfc.nasa.gov/seadas/modisl1db/
Yes you are right - I was confused. I think because on http://oceancolor.gsfc.nasa.gov/seadas/modisl1db/
"Please be aware that if the SeaDAS software package is already installed on your computer, you will already have full access to ALL of the functionality of MODISL1DB."
I thought this meant that everything would work the same.
I'm still a bit confused how to use MODISL1DB and SeaDAS together to end up with L2 products since MODISL1DB scripts only get you as far as the L1B level, and you need SeaDAS can get you to L2, yet both cannot be enabled at the same time. Is there a way around this? Maybe I need to wait till the next SeaDAS release (when is that scheduled)?
Thanks for the quick response.
Yes, that "Please be aware..." comment was initially true, until we made a few enhancements just prior to the MODISL1DB release. Sorry about that.
As far as using MODISL1DB and SeaDAS together, they were really not intended to be used together. The MODISL1DB package was intended for Direct Broadcast users that only wanted to process to L1B and did not want all of the extra baggage associated with SeaDAS. If you are interested in L2 products, then you should probably stick with SeaDAS. But your immediate problem is how to do this without having to change the filename format. I am not sure if it would work, as I've not tried it yet, but it's possible that you could take the scripts out of the etc directory from the MODISL1DB package and drop them into the etc directory of your SeaDAS installation, and that might work so that you don't have to change the input filenames. You should probably make backup copies of the scripts you replace, just in case it doesn't work out.
Moving the MODISL1DB scripts into the SeaDAS directory did the trick ... everything seems to be working.
Thanks for your help!