Page 2 of 3

Error using l3bin

Posted: Thu May 30, 2019 6:23 am America/New_York
by gnwiii
The OCSSW Processing System doesn't always change with a minor version update of the GUI.  The processing software is at git branch 7.5.   The l3bin program does require a name for the output file, so if the filename is missing that would explain your problem.   Either the GUI update failed or you have more than one SeaDAS GUI installation.  Installation failures may result from permission problems or running out of space on the device.  Your best bet may be to delete the previous install(s) after making a backup of your ~/.seadas directory.

I did try messing the the input list file and the errors were not exactly like the error you encountered.  I'm not near the MacOS system at present, but when I get the chance I'll try running l3bin with missing output file name.

Error using l3bin

Posted: Thu May 30, 2019 10:22 am America/New_York
by OB SeaDAS - knowles
You might have installed SeaDAS 7.5.3 in your existing directory which is named 7.5.2.   Though confusing, this wouldn't be a problem.   Do you have both a 7.5.3 directory and a 7.5.2 directory?

What is your environment variable $OCSSWROOT set to?  At command line type:
echo $OCSSWROOT

In the GUI, under Menu > OCSSW > Update Data Processors what is the "Local install-dir"

Danny

Error using l3bin

Posted: Thu May 30, 2019 11:47 am America/New_York
by bbroman93
The local install-dir is /Applications/seadas-7.5.3/ocssw

Error using l3bin

Posted: Thu May 30, 2019 12:37 pm America/New_York
by bbroman93
Is this error something I will be able to fix?

Error using l3bin

Posted: Mon Jun 03, 2019 7:35 am America/New_York
by OB SeaDAS - knowles
How about the other questions I asked like the OCSSWROOT environment variable and having 1 or 2 seadas directories?  We need to know this in order to understand what your error is.

Danny

Error using l3bin

Posted: Mon Jun 10, 2019 10:25 am America/New_York
by bbroman93
I'm sorry this took me so long to answer. I am relatively new to coding, and it took a friend helping me to understand what your question meant/how to find the proper information.

My $OCSSWROOT environment is /Applications/seadas-7.5.3/ocssw

Error using l3bin

Posted: Mon Jun 10, 2019 10:25 am America/New_York
by bbroman93
It does not appear to have 2 variables as far as I can tell. I have also uninstalled all older versions of SeaDAS.

Error using l3bin

Posted: Mon Jun 10, 2019 12:17 pm America/New_York
by bbroman93
Hi Danny -- Removed all seadas directories and reinstalled a fresh copy of seadas visualizer and processing packages.  I set the OCSSWROOT system variable to /Applications/seadas-7.5.3/ocssw and sourced the OCSSW_bash.env file in my bash_profile.

when I type echo $OCSSWROOT at the terminal window I get /Applications/seadas-7.5.3/ocssw

By when I run the l3bin function the error indicates seadas is trying to find the hdf5 library in /Users/seadas/ocssw/...  Might this path be hardcoded somewhere in the l3bin function???

Here is the specific error message:
execution exception: java.io.IOException: l3bin failed with exit code 255.
Check log for more details.
L3BIN 5.12 (Dec 19 2018 12:40:40)
HDF5-DIAG: Error detected in HDF5 (1.8.19) thread 0:
  #000: /Users/seadas/ocssw/opt/src/hdf5/hdf5-1.8.19/src/H5F.c line 433 in H5Fis_hdf5(): no file name specified

Hope this helps you help me! :)

Bianca

    major: Invalid arguments to routine
    minor: Out of range
Input listing file: "" not found.

Error using l3bin

Posted: Mon Jun 10, 2019 2:13 pm America/New_York
by OB SeaDAS - dshea
The error message is saying that the file name the HDF is trying to read in is empty.  The /Users/seadas/... file is where the source code was on our machine when it was compiled.

More than likely you have an error in your input text file, like an extra line feed at the end of the file, or it is not a plain ASCII text file.

don

Error using l3bin

Posted: Mon Jun 10, 2019 2:58 pm America/New_York
by bbroman93
there is no error because when I run it from the command line, it works. it does not work from the visualization tool, and I have checked all of the txt files for spaces.