Forum

I downloaded all the KD_490 files you listed and was only able to open and display two of them A20040922004121.L3m_MO_KD490_Kd_490_4km A20112742011304.L3m_MO_KD490_Kd_490_4km. It's a known issue for SeaDAS 8.0.0 in reading files with null value attributes in metadata. The fix will be in the next rel...

Did you install SeaDAS 8.0.0 on Windows? Can you do "SeaDAS-OCSSW -> SeaDAS/System Info" and share the output here?

Please let us know if you are running SeaDAS 7.5.3 or SeaDAS 8. Also, what operating system do you have?

According to the 2019 post: https://forum.earthdata.nasa.gov/viewtopic.php?f=7&t=1759&p=5659&hilit=LANDSAT+7&sid=876582abaa0bbc82dad74fa4ffc96b44#p5659 The l2gen code *does* have support for Landsat 5 & 7 - but it may not be fully baked, so we've not really advertised it. In fact...

Here is the link to the help pages of SeaDAS 8: https://seadas.gsfc.nasa.gov/help/8.0.0/ If you click -> SeaDAS TOolbox -> OCSSW -> multilevel_processor -> Command Line Usage, you 'll find the help for multilevel_processor's command line usage: https://seadas.gsfc.nasa.gov/help/8.0.0/processors/Proc...

Can you do SeaDAS-OCSSW->SeaDAS/System Info?

When yo do SeaDAS-OCSSW->Install/update OC processors you need to check "VIIRS DEM files" too.

SeaDAS 7 should not be the problem. I have both SeaDAS 7 and 8 on my Mac.

What operating system are you using?

What is your geographic location?

We are scratching our heads. The lock file looks suspicious. I wonder what is in that file. You can try "rm ~/.seadas8/lock" before you attempt to open seadas8 on the command line. If frozen again, "ls -al ~/.seadas8" and check if the lock file show up. Or you can also try "...