Forum

If you can use /usr/local/bin/python3 for SeaDAS, it might be easier just to do .
Otherwise add to your bash or zsh file, start a new terminal, and start SeaDAS in that terminal.

That's interesting. I can't replicate the error you've got. Can you do SeaDAS-Toolbox -> SeaDAS/System Info and post it here? 1. Try to run l2gen without ancillary files after deleting /root/SeaDAS/ocssw/var/anc/2023/021 2. Try to run l2gen with freshly downloaded ancillary files after clicking &quo...

I assume you used collocation tool to put the L3m files together. https://seadas.gsfc.nasa.gov/help-8.3.0/collocation/CollocationTool.html Here is an example expression for the Math Band Tool for 3 files -- ((chlor_a_M > 0.0 ? chlor_a_M : NaN) + (chlor_a_D0 > 0.0 ? chlor_a_D0 : NaN) + (chlor_a_D1 > ...

l2gen on Landsat 8 collection2 seems work with SeaDAS 8.3.0 and SeaDAS Processors (OCSSW) V2022.3.

Please let us know your SeaDAS version and SeaDAS processors tag.

Please make sure you have olcis3a and/or olcis3b installed.

Also choose xfdumanifest.xml (with absolute path) as ifile on l2gen GUI

On the SeaDAS GUI, choose SeaDAS-Toolbox -> Install/Update SeaDAS Processors, check olcis3a and/or olcis3b, and click run. https://seadas.gsfc.nasa.gov/help-8.3.0/processors/InstallOCSSW.html Choose SeaDAS-Toolbox -> l2gen, choose xfdumanifest.xml as your ifile, and click run https://seadas.gsfc.nas...

If you have another copy of python3 in /usr/local/bin/, it might be easier to point SeaDAS to use that copy of python3 by adding this line export PATH="/usr/local/bin/python3:$PATH" to your bash file. And then run: /usr/local/bin/pip3 install requests If you still want to use /Users/masud/...

It's hard to tell if a .xml file is doing what it is supposed to do by just looking at it. If you share the gpt command line with the ifile name, I can test it for you. As we discussed in the post https://forum.earthdata.nasa.gov/viewtopic.php?t=3823#p13616, SeaDAS can not write to netCDF4-CF at the...

SeaDAS processors (OCSSW) V2022.3 works best with SeaDAS 8.3.0. With V2022.3, we use the new naming convention -- https://oceancolor.gsfc.nasa.gov/docs/filenaming-convention/. For A2010283180500.L1A_LAC (MODIS AUQA L1A) modis_GEO -> AQUA_MODIS.20101010T180500.GEO.hdf (GEO) from L1A modis_L1B -> AQUA...

In SeaDAS 8.3.0 GUI, can you do SeaDAS-Toolbox -> Software & System Info and post the result here? "ModuleNotFoundError: No module named 'requests'" indicates SeaDAS can't find "requests''. It's probably due to some environment variable not setting up correctly. There are a few po...