- (16.16 KiB) Downloaded 40 times
The processing component (OCSSW) is distinct from the visualization component and can be installed independently. So you could use the OCSSW distributed with SeaDAS 8, but visualize the outputs with SeaDAS 7. Or visualize with another tool (I'd be sad, but you needn't worry about my feelings on the matter ). You'd have to use the command line to run the processing, but it isn't really that hard to do.
Thanks for the help. I think I have to go with SeaDAS 7 for now, but I may try to use the OCSSW for SeaDAS 8. I'm processing Landsat data for chl using l2gen. Is there any meaningful difference between the 7 and 8 OCSSWs for this task? And don't worry I'll always visualize with SeaDAS.
My other question is: Is there a guide somewhere for how to interact with SeaDAS via the command line? I am going to be processing a lot of images and would like to do them in bulk anyway. I know that there is a lot of information on how to set up the OCSSW environment, but what are the actual commands once I do this? I'll be using the Franz et al. 2015 paper as a starting point for the processing method. Thank you for your help!
- Subject Matter Expert
- Posts: 64
- Joined: Tue Feb 09, 2021 5:42 pm America/New_York
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 ... or.html#cl
The current OCSSW installer has a "--benchmark" option that installs a level-0 file and a bash script that does end-to-end processing from level-0 to a mapped image.lukecarberry wrote: ↑Fri Apr 23, 2021 1:06 pm America/New_York I am going to be processing a lot of images and would like to do them in bulk anyway. I know that there is a lot of information on how to set up the OCSSW environment, but what are the actual commands once I do this? I'll be using the Franz et al. 2015 paper as a starting point for the processing method.
This is useful to check that your installation is working and also for examples of a processing workflow. The multi-level processor works well for NASA's workflows, but many workflows need other tools so I generally end up using shell scripts. If you have access to a high-end linux system you may want to investigate GNU parallel to run multiple jobs at the same time, but note that the "optimal" number of jobs is usually far less than the number of cores -- I usually start with 2 jobs and keep doubling until the thruput falls off. This can be due to I/O bottlenecks or heat causing reduced clock rates.
If you are not comfortable with shell scripts you will find the time spent learning basics of command-line processing is well spent.
Thank you for the help. I've been able to install the command line processing for OCSSW and now I'm trying to process a Landsat image. Again, I'm using Seadas 7.5.3 because Seadas 8 doesn't run on my computer (even though the OCSSW would technically work). I am getting the error "/Users/seadas/ocssw/src/l2gen/l2_generic.c line 458: product angstrom_1609 not found." Any thoughts? I attached a document with a full dialogue from the command line. Thank you for any help you can offer!
- (21.3 KiB) Downloaded 15 times
I have an older system running linux that did random freezes. Google found that other users with similar hardware were also having problems, and a bug report that identified an error in the linux kernel. I had to use and older kernel until the error was fixed in a current kernel. Some distros backport such fixes to older kernels. You may want to investigate reports from linux users of similar probelms with your hardware (graphics, network, CPU).
The code only supports angstrom derived from visible and NIR wavelengths. You could simply select angstrom (as you have done) without wavelength specificity. This will provide the angstrom between 443nm and 865nm (or the closest bands to those for the instrument).I am getting the error "/Users/seadas/ocssw/src/l2gen/l2_generic.c line 458: product angstrom_1609 not found." Any thoughts?
P.S. Since this is a separate topic from the original issue, you should post a new question.