seadas 6.2 error with GUI not command line

By bmurch Date 2011-02-25 21:01 Edited 2011-02-25 21:08

I have had 6.2 via commandline in batch processing for a week without issue. However, I cannot say the same for the GUI.

Inside this directory:
http://optics.marine.usf.edu/~bmurch/seadas/test_commandline/
you will see a A2011056074000.L1A_LAC and A2011056074000.GEO file that I created perfectly
fine while using the command line.

The commands and output are contained within this file:
http://optics.marine.usf.edu/~bmurch/seadas/test_commandline/command_line_output.txt

Inside this directory:
http://optics.marine.usf.edu/~bmurch/seadas/test_seadas_gui/
This is the same PDS file that has tried to be processed with the SeaDAS GUI itself.
The output of the output to shell is contained here:
http://optics.marine.usf.edu/~bmurch/seadas/test_seadas_gui/seadas_output.txt

Both were done in the same shell, using different directories.

The cshrc file is here and almost empty:
http://optics.marine.usf.edu/~bmurch/seadas/test_seadas_gui/cshrc

My env looks like this:
http://optics.marine.usf.edu/~bmurch/seadas/test_seadas_gui/env.txt

Other users are experiencing the same issue.

PS, SeaDAS 6.1 GUI has no problem as evidenced here:
http://optics.marine.usf.edu/~bmurch/seadas/test_seadas_gui_61/

Please advise.

Thanks, Brock

By gwyn Date 2011-02-28 13:49

Brock -

I'll look into it.
I did immediately notice that the granule start/stop times are different.

For the command line,
starttime: 2011-02-25T07:40:00.077234Z stoptime: 2011-02-25T07:44:49.931040Z duration: 289.853806 seconds

For the GUI,
starttime: 2011-02-25T07:41:20.077234Z stoptime: 2011-02-25T07:43:19.931040Z duration: 289.853806 seconds

By bmurch Date 2011-02-28 16:41

As was the default output name.

modis_L1A.csh:
Output Level 1A: ./A2011056074000.L1A_LAC

seadas6.2
Output Level 1A: ./A2011056074120.L1A_LAC

But one wouldn't think that an issue.

Brock

By gwyn Date 2011-02-28 18:43

The output filename is not an issue, but the start/stop times and duration are since they are used for process control. In this case, l1agen is being asked to extract almost 5 minutes of data starting at 07:41:20 - and the L0 file just doesn't have it. Even so, it shouldn't bomb.

I haven't been able to replicate the issue here, so I'd like you to try a couple of experiments after doing SeaDAS 6.2 setups:

1. At the command line:
uname -a which modis_L1A.csh; which addsecs; which bc env | sort >! env_cmd.txt

2. At the SeaDAS prompt (IDL command line):
spawn,'uname -a' spawn,'which modis_L1A.csh; which addsecs; which bc' spawn,'env | sort >! env_gui.txt'

3. At the command line again:
/optics1/scratch/bmurch/modis/test> modis_L1A.csh MOD00.P2011056.0740_1.PDS -startnudge 0 -stopnudge 10 -save-log

That last flag will save the LogReport and *.pcf files, which may help with diagnosis.

By bmurch Date 2011-02-28 19:40

1) seabird 107 :/optics1/scratch/bmurch/modis/test> which modis_L1A.csh; which addsecs; which bc
/optics1/software/seadas/seadas_6.2/run/scripts/modis_L1A.csh
/optics1/software/seadas/seadas_6.2/run/bin/addsecs
/usr/bin/bc
seabird 108 :/optics1/scratch/bmurch/modis/test> env | sort >! env_cmd.txt

2) seabird 114 :/optics1/scratch/bmurch/modis/test> seadas
IDL Version 8.0.1 (linux x86_64 m64). (c) 2010, ITT Visual Information Solutions
Installation number: 17539.
Licensed for use by: USF Dept of Marine Sciences

SeaDAS Version 6.2 (pid = 20950)
spawn,'uname -a'SeaDAS> spawn,'uname -a'
Linux seabird.marine.usf.edu 2.6.18-194.8.1.el5 #1 SMP Thu Jul 1 19:04:48 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
SeaDAS> spawn,'which modis_L1A.csh; which addsecs; which bc'
/optics1/software/seadas/seadas_6.2/run/scripts/modis_L1A.csh
/optics1/software/seadas/seadas_6.2/run/bin/addsecs
/usr/bin/bc
SeaDAS> spawn,'env | sort >! env_gui.txt'

3)
Find output here:
http://optics.marine.usf.edu/~bmurch/seadas/test_gwyn/

as well as env_cmd.txt env_gui.txt

Thanks for all your work.

By gwyn Date 2011-02-28 21:08

I'm not seeing anything so far...

Here's another exercise:
I'm attaching a pared-down c-shell file. Please run it two ways, and put output in separate directories:

from the command line:
times.csh MOD00.P2011056.0740_1.PDS > l0times.txt

from the SeaDAS IDL line:
spawn,'times.csh MOD00.P2011056.0740_1.PDS > l0times.txt'

of course use the full path to times.csh and to your L0 file.

Attachment: times.csh (1.9k)

By bmurch Date 2011-03-01 15:03 Edited 2011-03-01 15:23

For both I recieved errors with your times.csh:

/optics1/software/seadas/seadas_6.2/run/bin_debug/l0cnst_write_modis: Command not found.

I do not have a bin_debug directory.

seabird 161 :/optics1/scratch/bmurch/modis/times_command> env | grep DEBUG
OCSSW_DEBUG=0

So I changed the times.csh to comment out the OCSSW_DEBUG line

That ran OK. Diff in start stop times.

starttime: 2011-02-25T07:50:00.077234Z
stoptime: 2011-02-25T07:34:59.931040Z
---
starttime: 2011-02-25T07:41:00.077234Z
stoptime: 2011-02-25T07:43:59.931040Z

PS, I noticed the only other diffs were like this:

< BEGIN_PGE: Tue Mar 1 09:57:10 2011
---

> BEGIN_PGE: Tue Mar 1 09:57:40 2011

from the command line:
http://optics.marine.usf.edu/~bmurch/seadas/times_command/

from the SeaDAS IDL line:
http://optics.marine.usf.edu/~bmurch/seadas/times_seadas/

Thanks,
Brock

By gwyn Date 2011-03-01 15:36

Those times don't look good at all! In fact, the offsets are multiplied by 10 when called from the SeaDAS IDL command line:

Before nudge:
starttime: 2011-02-25T07:40:00.077234Z
stoptime: 2011-02-25T07:44:59.931040Z
duration: 299.853806 seconds
Nudge:
startnudge: 60
stopnudge: 60
After nudge:
starttime: 2011-02-25T07:50:00.077234Z
stoptime: 2011-02-25T07:34:59.931040Z
duration: 179.853806 seconds

It looks like we may have a problem with the "addsecs" routine.

One MORE thing! Please "unsetenv OCSSW_DEBUG", then try the inside-SeaDAS test again, using my unaltered script. Thanks!

By bmurch Date 2011-03-01 17:02

unsetenv the OCSSW_DEBUG

seabird 209 :/optics1/scratch/bmurch/modis> env | grep OCSSW_DEBUG
seabird 210 :/optics1/scratch/bmurch/modis>

and ran your script within seadas with the original times.csh in the output directory below.

ran spawn,'times.csh MOD00.P2011056.0740_1.PDS > l0times.txt'

output is here:

http://optics.marine.usf.edu/~bmurch/seadas/times_seadas_2/

By bmurch Date 2011-03-01 20:37

(different input file) I also noticed that the getanc script returns a // in the anc paths, but know that doens't hurt anything.

seadog 579 :/tmp/test> $SEADAS/run/scripts/getanc /tmp/test/A2011060163500.ECARIB.L1B_LAC -no-no2
Determining pass start and end times..

Input file : /tmp/test/A2011060163500.ECARIB.L1B_LAC
Start time : 2011060163500
End time : 2011060163949

*** WARNING: No optimal OZONE files found.

Created 'A2011060163500.ECARIB.L1B_LAC.anc' l2gen parameter text file:

met1=/optics1/software/seadas/seadas_6.1/var/anc//2011/060/S201106006_NCEP.MET
met2=/optics1/software/seadas/seadas_6.1/var/anc//2011/060/S201106006_NCEP.MET
met3=/optics1/software/seadas/seadas_6.1/var/anc//2011/060/S201106006_NCEP.MET
sstfile=/optics1/software/seadas/seadas_6.1/var/anc//2011/059/N2011059_SST_OIV2AVAM_24h.nc
icefile=/optics1/software/seadas/seadas_6.1/var/anc//2011/058/N201105800_SEAICE_NSIDC_24h.hdf

By gwyn Date 2011-03-01 20:52

Brock,

The problem seems to be coming from the addsecs routine, but only when invoked from the SeaDAS IDL environment and possibly only on 64-bit. I can't narrow it down more than that at this time. I know that routine will be replaced in a future SeaDAS release.

Thanks for bringing this issue to our attention,
Gwyn

By bmurch Date 2011-03-02 14:40 Edited 2011-03-02 15:06

Gwyn,

When you say 'future' SeaDAS release, do you mean an update to 6.2 or the java python version of SeaDAS 7?

SeaDAS is extremely important in our lab as you probably know, and SeaDAS 6.2 had some great changes in it. Dr. Hu and our students use the GUI extensively.

I know there is a 32 bit version, but can the 64 bit version be invoked as 32 bit as idl can (idl -32)? Will the 32 bit SeaDAS version run on a 64 bit machine?

We have only 64bit servers here!

Thanks,
Brock