I am facing a problem recently,
why seadas6.2 and even the its latest version 6.3 could not read 4-byte flat file?
I generated flat files from seawifs data also by using seadas.
But when I tried to read the flat file using GUI, I got the following messages:

GENERIC_FILE_TYPE detected a non-HDF file.
GENERIC_FILE_TYPE detected a SEAWIFS L0 file.

And

the "Selection For SeaWiFS L0 File" came up, showing bands (412, 443, ..., 865) to be selected.

Why can this problem happen? Any way to fix it?

Thank you.

Eko

Eko,

There was a problem with 6.2.
However, 6.3 should work (it does for me).

When running 6.3, make sure that the environment variable $OCSSW_BIN points to your $SEADAS/run/bin/<arch> directory
(where <arch> is the OS-specific directory, e.g. linux; linux_64; macosx_intel)

Sean

Sean,

I saw the last sentences in OCSSW.env are like below;

if ( "$OCSSW_DEBUG" == "1" ) then
   setenv OCSSW_BIN $OCSSWROOT/run/bin_debug/$OCSSW_ARCH
else
   setenv OCSSW_BIN $OCSSWROOT/run/bin/$OCSSW_ARCH
endif

# executable path
set path=($OCSSW_BIN $OCSSWROOT/run/scripts $LIB3_BIN $path)
setenv PATH `echo $PATH | tr ':' '\n' | perl -e 'while (<>) { print $_ unless $s{$_}++; }' | tr '\n' ':' | sed 's/::/:/g'| sed 's/:$//'`

So, do I need to change something like:

if ( "$OCSSW_DEBUG" == "1" ) then
   setenv OCSSW_BIN $SEADAS/run/bin/linux
else
   setenv OCSSW_BIN $SEADAS/run/bin/linux
endif

BUT, How about OCSSWROOT below?

# executable path
set path=($OCSSW_BIN $OCSSWROOT/run/scripts $LIB3_BIN $path)
setenv PATH `echo $PATH | tr ':' '\n' | perl -e 'while (<>) { print $_ unless $s{$_}++; }' | tr '\n' ':' | sed 's/::/:/g'| sed 's/:$//'`

One more thing, do I need to install both linux and linux_64?

Thank you.

Eko

Eko,

All is as it should be for 6.3, you need not change anything.  OCSSWROOT is set in the seadas.env file - it is equivalent to $SEADAS
You only need to install one version - e.g. if you have a 64bit linux OS, install the linux_64.

Make sure that you are not somehow mixing 6.2 and 6.3 in your environment. 

Sean

Sean,

I have both seadas6.1 and seadas6.3 installed in my fedora 16.
Seadas6.1 is in /home/eko/seadas61
Seadas6.3 is in /home/eko/seadas63

Will two different version seadas installation somehow mix the environment?
I need to keep seadas6.1 installed as it can read flat file.

If this double installation can be a problem. I will remove one of them.

Thank you.

Eko

See: http://oceancolor.gsfc.nasa.gov/forum/oceancolor/topic_show.pl?tid=3030.  In your case, the seadas environment settings are done by sourcing ~/seadas6.N/config/seadas.env.    There is a risk that a variable defined for SeaDAS 6.1 is no longer required by SeaDAS 6.3 but (due to some oversight) is still recognized and could cause problems if set.  If you need to switch back and forth many times the PATH variable will keep growing and a different approach may be required if you don't want to log out and back in to reset the PATH.

Providing a convenient (and robust) way to switch between two or more different versions of an app is a very common problem for UNIX/linux system administrators, which means many different approaches to the problem have been developed over the years.   If you know an experienced administrator, they should be able to help you chose, and there are forums such as http://stackoverflow.com/ devoted to such problems.  Three examples
are:

"environment modules"  http://modules.sourceforge.net/

virtual machines (for those lucky enough to buy a large disk before the floods in Thailand caused prices to increase)

chroot