Forum

Just fixed this.  Please update you OCSSW and all should be well.

George, you are correct.  A new OCSSW_bash.env got pushed to the web server accidentally.

Try updating OCSSW.  It should work now.

don

When I save a par file with  l2prod=Lt_nnn, SeaDAS changes it to l2prod=Lt_iii, Lt_vvv when saving.  That works fine when reading the par file.

don

It looks like this library did not get built when you built the third party libs.OCSSW/lib3/EOS/lib/macintel64/libPGSTK.aIf that library does not exist on your system then you need to rebuild lib3/src/sdptk.  You do not have to rebuild all of lib3.  You can "cd" to that directory...

Thanks for the bug report and this was the correct place to report it.  The next release of the software is "really soon", so I can't promise that a fix will get in this release.

don

also note that l3bindump does not have an XML output for the data.  The "dump_options_xmlfile" outputs an XML file describing the command line options.

don

We are in the final testing phase for SeaDAS 7.5 which will be able to read the new OLI format.  Sorry I can't give you an exact target date, but we are close.

don

Yes, it seems there is a bug with the filename guessing logic in the GUI.  For now just run the programs on the command line:

modis_GEO.py A2013237033500.L1A_LAC.x.hdf
modis_L1B.py A2013237033500.L1A_LAC.x.hdf

a 250m file is going to be pretty big.  Processing it with l2gen on the command line should not be a problem, but loading the file into SeaDAS might fill up your memory.  How much RAM did you allocate to your virtual machine?

don

We will need a bit more information to help answer this question.

What OS are you using?
What Java are you using?

I have seen problems like this on Linux when using openJDK.  If that is the case we suggest using the JDK from Oracle.\

Hope that helps.

don