Not logged inOcean Color Forum

The forum is locked.

The Ocean Color Forum has transitioned over to the Earthdata Forum (https://forum.earthdata.nasa.gov/). The information existing below will be retained for historical reference. Please sign into the Earthdata Forum for active user support.

Up Topic SeaDAS / SeaDAS - General Questions / off line SeaDAS install (locked)
- By alaroy Date 2014-06-19 15:44
We would like to set up a complete SEADAS installation (processing and visualization) on a Linux computer that is isolated from the outside network (why is a long story that I'll skip for now).

What files do I need to download to my media? Is there a way to do the "installer's" job manually and / or without internet access?

-Andrew L.
- By dshea Date 2014-06-19 23:06
Andrew,

The SeaDAS GUI installer does not need internet access, so installing that is easy.

Installing the science software is not bad since Sean added the "local" option to install_ocssw.py

Go to this page:

http://oceandata.sci.gsfc.nasa.gov/ocssw/

- create a directory for the bundles ($bundleDir)
- Download the script "install_ocssw.py" and set execution bits on it
- Download the files and bundles listed on the above web page into $bundleDir
- Assuming SeaDAS was installed into "~/seadas", run the installer

install_ocssw.py -i ~/seadas/ocssw -l $bundleDir --aqua --seawifs <others...>


You might have trouble with the lut updating scripts at the end of the install.  This only applies to MODIS and VIIRS.
- By ghulampitt Date 2014-06-21 03:52
sorry to interrupt, like you say before, i get a problem with luts when i trying instal seadas 7.02 processor manually with instal_ocssw.py. do you have solution with that kind of problem?:cry:
- By seanbailey Date 2014-06-23 09:10
Have you tried running the update_luts.py script directly?  Do so with the verbose option (-v, --verbose) to see what it's doing:

update_luts.py -v viirsn

Regards,
Sean
- By ghulampitt Date 2014-06-28 02:31
i have tried to update_luts.py manually like you suggested before, and i have this kind of results:

---------------------------------------------------------------------------------------------------------------------------------

- OPER:VIIRS-SDR-F-LUT_npp_OBPG20130805.h5
Traceback (most recent call last):
  File "./seadas-7.0.2/ocssw/run/scripts/update_luts.py", line 65, in <module>
    l.update_modis_viirsn()
  File "/home/ghulam/seadas-7.0.2/ocssw/run/scripts/modules/lut_utils.py", line 224, in update_modis_viirsn
    localpath=outputdir, timeout=self.timeout, verbose=self.verbose)
  File "/home/ghulam/seadas-7.0.2/ocssw/run/scripts/modules/ProcUtils.py", line 119, in httpdl
    shutil.copyfileobj(response, file)
  File "/usr/lib/python2.7/shutil.py", line 49, in copyfileobj
    buf = fsrc.read(length)
  File "/usr/lib/python2.7/socket.py", line 380, in read
    data = self._sock.recv(left)
  File "/usr/lib/python2.7/httplib.py", line 561, in read
    s = self.fp.read(amt)
  File "/usr/lib/python2.7/socket.py", line 380, in read
    data = self._sock.recv(left)
socket.error: [Errno 104] Connection reset by peer

i dont have any idea about my problem, or this problem caused by my network connection?
- By seanbailey Date 2014-06-28 15:13
The "socket.error: [Errno 104] Connection reset by peer" error means our server terminated the connection.
This can happen if you have a poor connection and there is what the server considers a long time between
packets sent.  The VIIRS LUT directory is particularly troublesome as there is a LOT in there (most of it
probably unnecessary, but rather than throw the baby out with the bathwater, we've left it all in there)

You can bootstrap the process but manually grabbing the viirsn directory from our data server an putting
it in your $OCSSWROOT/run/var/ directory.  The tree to replicate is:

http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/

You can use the example commands on our Data Access FAQ
to grab the files "in bulk".

For example, to get the files under:
   
    http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/cal/OPER

you could use the following:

    wget -q -O - http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/cal/OPER |grep -i npp|wget -N --wait=0.5 --random-wait --base=http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/cal/OPER/ --force-html -i -


Sean
- By ghulampitt Date 2014-07-05 06:37
thanks, the proccess to get bulk run percfectly, and now im starting to proccess L1a viirsn data that i get from ocean color web,,
but unfortunetely, i get this kind of error to:

---------------------------------------------------------------------------------------------------------------------------------------------------------
execution exception: java.io.IOException: l2gen failed with exit code 1.
Check log for more details.
Input file /home/ghulam/1/SVM01_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5 is VIIRS Level-1B standard product.
/home/swdev/ocssw/build/src/l2gen/getformat.c, 442: VIIRS HDF 5 file
Loading default parameters from /home/ghulam/seadas-7.0.2/ocssw/run/data/common/msl12_defaults.par
Loading default parameters for VIIRSN from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/msl12_defaults.par
Loading parameters for suite OC from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/msl12_defaults_OC.par
Loading command line parameters

Loading user parameters for VIIRSN

Opening filter file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/msl12_filter.dat
Setting 25 x 7 straylight filter on HILT mask

Filter Kernel
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Minimum fill set to 1 pixels

Setting 25 x 7 straylight filter on CLDICE mask

Filter Kernel
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Minimum fill set to 1 pixels

Loading characteristics for VIIRSN
Opening sensor information file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/msl12_sensor_info.dat
  Bnd   Lam       Fo    Tau_r     k_oz    k_no2    t_co2   awhite       aw      bbw
    0  410.000  171.134 3.175e-01 6.080e-04 5.951e-19 1.000e+00 1.000e+00 1.528e-01 3.297e-03
    1  443.000  190.214 2.328e-01 3.349e-03 4.997e-19 1.000e+00 1.000e+00 3.484e-02 2.411e-03
    2  486.000  198.774 1.600e-01 2.000e-02 2.990e-19 1.000e+00 1.000e+00 7.198e-02 1.622e-03
    3  551.000  184.122 9.738e-02 8.937e-02 1.041e-19 1.000e+00 1.000e+00 9.721e-02 9.680e-04
    4  671.000  150.456 4.395e-02 4.406e-02 1.015e-20 1.000e+00 8.871e-01 4.755e-01 4.200e-04
    5  745.000  127.643 2.865e-02 1.111e-02 2.547e-21 1.000e+00 7.872e-01 2.806e+00 2.683e-04
    6  862.000   96.031 1.594e-02 2.319e-03 4.358e-22 1.000e+00 6.486e-01 4.590e+00 1.448e-04
    7 1238.000   45.606 3.650e-03 0.000e+00 0.000e+00 9.994e-01 0.000e+00 1.370e+02 2.874e-05
    8 1601.000   25.084 1.305e-03 0.000e+00 0.000e+00 9.890e-01 0.000e+00 7.857e+02 9.496e-06
    9 2257.000    7.732 3.294e-04 0.000e+00 0.000e+00 9.696e-01 0.000e+00 2.180e+03 2.156e-06

  Bnd   Lam
-I- /home/swdev/ocssw/build/src/l2gen/l1_viirs_h5.c , 1097: Geolocation is Terrain Corrected
   10 3700.000
   11 4050.000
   12 8550.000
   13 10763.000
   14 12013.000

Calibration to be applied:
Calfile:  /home/ghulam/seadas-7.0.2/ocssw/run/var/viirsn/cal/OPER/VIIRS-SDR-F-LUT_npp_OBPG20130805.h5
Vicarious Gain[1]=0.960500 +/-0.000000, Offset[1]=0.000000
Vicarious Gain[2]=1.001900 +/-0.000000, Offset[2]=0.000000
Vicarious Gain[3]=1.007800 +/-0.000000, Offset[3]=0.000000
Vicarious Gain[4]=0.972400 +/-0.000000, Offset[4]=0.000000
Vicarious Gain[5]=1.014600 +/-0.000000, Offset[5]=0.000000
Vicarious Gain[6]=1.038900 +/-0.000000, Offset[6]=0.000000
Vicarious Gain[7]=1.000000 +/-0.000000, Offset[7]=0.000000
Vicarious Gain[8]=1.000000 +/-0.000000, Offset[8]=0.000000
Vicarious Gain[9]=1.000000 +/-0.000000, Offset[9]=0.000000
Vicarious Gain[10]=1.000000 +/-0.000000, Offset[10]=0.000000

VIIRS filename for M01: /home/ghulam/1/SVM01_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M02: /home/ghulam/1/SVM02_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M03: /home/ghulam/1/SVM03_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M04: /home/ghulam/1/SVM04_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M05: /home/ghulam/1/SVM05_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M06: /home/ghulam/1/SVM06_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M07: /home/ghulam/1/SVM07_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M08: /home/ghulam/1/SVM08_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M09: /home/ghulam/1/SVM09_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M10: /home/ghulam/1/SVM10_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M11: /home/ghulam/1/SVM11_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M12: /home/ghulam/1/SVM12_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M13: /home/ghulam/1/SVM13_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M14: /home/ghulam/1/SVM14_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M15: /home/ghulam/1/SVM15_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5
VIIRS filename for M16: /home/ghulam/1/SVM16_npp_d20130901_t0616362_e0618004_b09560_obpg_ops.h5

VIIRS calibration starting
Input calibration from file: /home/ghulam/seadas-7.0.2/ocssw/run/var/viirsn/cal/OPER/VIIRS-SDR-F-LUT_npp_OBPG20130805.h5
Reading in F LUT: /home/ghulam/seadas-7.0.2/ocssw/run/var/viirsn/cal/OPER/VIIRS-SDR-F-LUT_npp_OBPG20130805.h5
Granule time is: 1756707431228276
itim1: 608, t1: 1756684834000000, t2: 1756771234000000
Interp factor from t2: 0.261542

The F LUT found in the SDR is: VIIRS-SDR-F-LUT_npp_Unity_HG
Found a unity F table designation in the SDR
Completed calibration using F LUT file(s)

/home/swdev/ocssw/build/src/l2gen/l1_viirs_h5.c: total # inst scans: 48, dataset scans: 48
Allocated 5004812 bytes in L1 record.
Allocated 2816012 bytes in L2 record.

Opening: /home/ghulam/1/V2013244061636.L2_NPP
Reading Thuillier_F0.dat

The following products will be included in /home/ghulam/1/V2013244061636.L2_NPP.
0 chlor_a
1 Kd_490
2 aot_862
3 angstrom
4 Rrs_410
5 Rrs_443
6 Rrs_486
7 Rrs_551
8 Rrs_671
9 pic
10 poc
11 par
12 l2_flags

Begin l2gen Version 6.7.0 Processing
Sensor is VIIRSN
Sensor ID is 14
Sensor has 10 reflective bands
Sensor has 5 emmissive bands
Number of along-track detectors per band is 16
Number of input pixels per scan is 3200
Processing pixels 1 to 3200 by 1
Processing scans 1 to 768 by 1
Ocean processing enabled
Land processing enabled
Atmospheric correction enabled

Begin MSl12 processing at 2014186113306000

Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
Allocated 5004812 bytes in L1 record.
/home/swdev/ocssw/build/src/l2gen/viirs_utls.c: Reading leap second information from file /home/ghulam/seadas-7.0.2/ocssw/run/var/modis/leapsec.dat
Loading radiance to brightness temperature from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/bt_viirsn.hdf
Loading land mask file from /home/ghulam/seadas-7.0.2/ocssw/run/data/common/landmask.dat
Loading bathymetry mask file from /home/ghulam/seadas-7.0.2/ocssw/run/data/common/watermask.dat
Loading ice mask file from /home/ghulam/seadas-7.0.2/ocssw/run/data/common/ice_climatology.hdf
Loaded monthly NSIDC ice climatology HDF file.
Loading elevation file from /home/ghulam/seadas-7.0.2/ocssw/run/data/common/ETOPO1_ocssw.nc
Loading climatology file /home/ghulam/seadas-7.0.2/ocssw/run/data/common/sst_climatology.hdf
Loading SSS reference from Climatlogy file: /home/ghulam/seadas-7.0.2/ocssw/run/data/common/sss_climatology_woa2009.hdf

Opening meteorological files.
  met1   = /home/ghulam/seadas-7.0.2/ocssw/run/data/common/met_climatology.hdf
  met2   =
  met3   =
  ozone1 = /home/ghulam/seadas-7.0.2/ocssw/run/data/common/ozone_climatology.hdf
  ozone2 =
  ozone3 =
  no2    = /home/ghulam/seadas-7.0.2/ocssw/run/data/common/no2_climatology.hdf

/home/swdev/ocssw/build/src/l2gen/anc_acq.c, 126: Currently, no ECMWF climatology exists, assuming standard ancillary

Opening ozone file /home/ghulam/seadas-7.0.2/ocssw/run/data/common/ozone_climatology.hdf

Opening NO2 file /home/ghulam/seadas-7.0.2/ocssw/run/data/common/no2_climatology.hdf

Opening NO2 frac file /home/ghulam/seadas-7.0.2/ocssw/run/data/common/trop_f_no2_200m.hdf

Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_410_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_443_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_486_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_551_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_671_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_745_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_862_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_1238_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_1601_iqu.hdf
Loading Rayleigh coefficients from /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/rayleigh/rayleigh_viirsn_2257_iqu.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_410.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_443.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_486.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_551.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_671.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_745.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_862.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_1238.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_1601.hdf
Loading polarization file /home/ghulam/seadas-7.0.2/ocssw/run/data/viirsn/cal/polcor_viirsn_2257.hdf

Using  862.0 nm channel for cloud flagging over water.
Using  410.0 nm channel for cloud flagging over land.

Processing scan #     0 (1 of 768) after      1 seconds

Loading SSES table from /home/ghulam/seadas-7.0.2/ocssw/run/data/modisa/cal/sst_sses_modisa_v5.hdf
-E- /home/swdev/ocssw/build/src/l2gen/sst.c:  Error opening file /home/ghulam/seadas-7.0.2/ocssw/run/data/modisa/cal/sst_sses_modisa_v5.hdf.

--------------------------------------------------------------------------------------------------------------------------------------------------------

im sorry (again), i dont understand about this problem..
i need your suggestion to solve this problem..

¬ghulam
- By seanbailey Date 2014-07-06 15:51
We do not currently support VIIRS SST processing, but unfortunately with a recent update,
I failed to reset the viirs default to not process SST.   So, SST processing is on, but since we
don't have coefficient tables for VIIRS we use MODIS.  The code is looking for those tables
and you don't have them
Either set proc_sst=0 or install the MODIS-Aqua data files. 

Regards,
Sean
- By arunocean Date 2014-08-21 05:25
Hello

I need to install processors offline. I could able to manage installation of modis, meris etc processors. However, I couldn't get the LUT for MODIS. Seadas is showing error when I'm trying to convert my MODIS L1A file to MODIS GEO. Can anyone help me to install the ancillary data offline in SEADAS. I'm using virtual machine on windows 7 platform which has no INTERNET CONNECTION. I need to bring files from another file and copy. Awaiting positive reply.

thanks
Arun
- By gnwiii Date 2014-08-21 09:36
It would be easier to help you if we could be sure exactly what you tried to do. 

I'll assume you used the bundles but, as predicted, encountered the "trouble with the lut updating scripts at the end of the install.  This only applies to MODIS and VIIRS.".  Later in this thread, an example was given using "wget" to obtain the VIIRS LUTS.   I can guess that
you can't use this example directly because your internet connected system runs Windows and you don't have the "wget" and ""grep" utilities in the following suggested wizardly incantation for obtaining VIIRS LUTS:


wget -q -O - http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/cal/OPER |grep -i npp|wget -N --wait=0.5 --random-wait --base=http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/viirsn/cal/OPER/ --force-html -i -


Actually, for modisa you don't want the " |grep -i npp" filter, so you would have:


wget -q -O - http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/modisa/cal/OPER |wget -N --wait=0.5 --random-wait --base=http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/modisa/cal/OPER/ --force-html -i -


There are ways to run  "wget" on Windows.  Here, I use the Cygwin 64-bit tools (note that these can be installed without "admin"
privileges by running setup-x86_64.exe with the "--no-admin").  Cygwin is very
useful if you are experienced in (or want to gain experience with) linux command-line (bash shell) tools,  but you can also download the files manually using a web browser as follows:

Click on modisa/cal/OPER.  You should see
something like:


Index of: http://oceandata.sci.gsfc.nasa.gov/Ancillary/LUTs/modisa/cal/OPER

SHA1 Checksums

Filename  Last Modified  Size
  MYD02_Emissive_LUTs.V6.1.17.24_OC.hdf          2014-04-08 04:10:02.361161  279459
  MYD02_QA_LUTs.V6.1.17.24_OC.hdf          2014-04-08 04:10:02.361161  102020
  MYD02_Reflective_LUTs.V6.1.17.24_OC.hdf  2014-04-08 04:10:02.373161  6879984
Page Last Updated: Thursday, 21 August 2014


You need to download these three files can copy them to "$OCSSWROOT/var/run/modisa/cal/OPER" in your virtual machine.

The other files you may need for MODIS Aqua are $OCSSWROOT/run/var/modis/leapsec.dat and $OCSSWROOT/run/var/modis/utcpole.dat, found in Ancillary/LUTS/modis.
- By hazyhu Date 2014-08-25 08:17
I did it under the direction, but I cannot setup the processors. Anybody know how to do the off line installing?
- By gnwiii Date 2014-08-25 09:28
You will have to provide more details of your problem.  Is this a fresh offline install or are you just having problems with your installation from: After I finished the Installation of Seadas7.0... where you seem to have been able to make some progress towards installing the processing system.
- By hazyhu Date 2014-08-27 22:25
Firstly?thanks for your reply. My OS is Ubuntu14, and I have installed the seadas7 . I have finished my seadas installation, and now I share my installation progress with all who need to do just like me. Just like above descried, after  I have installed  the standard seadas , I cannot not install the seadas processing module. I used the direction just described above, but I cannot install it  because of the net error.  Then I download the file required(http://oceandata.sci.gsfc.nasa.gov/ocssw/), and move it to the dir(home/seadas-7.0.2/ocssw/), then I continue to intall the processing module under the direction(http://seadas.gsfc.nasa.gov/installers/),then I finished it. But I encounter another question just descried below.

execution exception: java.io.IOException: install_ocssw.py failed with exit code 1.
Check log for more details.
Installing bundles.sha256sum (1 of 13)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  2423  100  2423    0     0   3597      0 --:--:-- --:--:-- --:--:--  3600
Installing common (2 of 13)
??? stash?
Installing OCSSW_bash.env (3 of 13)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  2815  100  2815    0     0   3637      0 --:--:-- --:--:-- --:--:--  3641
Installing README (4 of 13)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3358  100  3358    0     0   4504      0 --:--:-- --:--:-- --:--:--  4501
Installing ocrvc (5 of 13)
??? stash?
Installing modis (6 of 13)
??? stash?
Installing modisa (7 of 13)
** Resuming transfer from byte position 321481968
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
???? '/home/hq/seadas-7.0.2/ocssw/run/data/modisa'...
?????:   0% (1/283)  
?????:   1% (3/283)  
......
  
?????:  99% (281/283), 305.81 MiB | 27.79 MiB/s  
?????: 100% (283/283), 306.59 MiB | 27.78 MiB/s, done.
?? delta ?:   0% (0/42)  
.........
?? delta ?: 100% (42/42), done.
????... ???
Checking out files:   9% (18/187)  
.......  
Checking out files: 100% (187/187), done.
?? http://oceandata.sci.gsfc.nasa.gov/ocssw/modisa
   f3eb1ad..d0f30c8  master     -> origin/master
Installing hmodisa (8 of 13)
** Resuming transfer from byte position 4031753
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
???? '/home/hq/seadas-7.0.2/ocssw/run/data/hmodisa'...
?????:   0% (1/177)  
...... 
?????: 100% (177/177), 3.84 MiB | 0 bytes/s, done.
?? delta ?:   0% (0/14)  
......
?? delta ?: 100% (14/14), done.
????... ???
?? http://oceandata.sci.gsfc.nasa.gov/ocssw/hmodisa
   7141349..509d355  master     -> origin/master
Installing bin (9 of 13)
??? stash?
Installing bin3 (10 of 13)
??? stash?
Installing scripts (11 of 13)
Python version acceptable
Installing aqua-luts (12 of 13)
Traceback (most recent call last):
  File "/home/hq/seadas-7.0.2/ocssw/run/scripts/update_luts.py", line 65, in <module>
    l.update_modis_viirsn()
  File "/home/hq/seadas-7.0.2/ocssw/run/scripts/modules/lut_utils.py", line 250, in update_modis_viirsn
    localpath=outputdir, timeout=self.timeout, verbose=self.verbose)
  File "/home/hq/seadas-7.0.2/ocssw/run/scripts/modules/ProcUtils.py", line 119, in httpdl
    shutil.copyfileobj(response, file)
  File "/usr/lib/python2.7/shutil.py", line 49, in copyfileobj
    buf = fsrc.read(length)
  File "/usr/lib/python2.7/socket.py", line 380, in read
    data = self._sock.recv(left)
  File "/usr/lib/python2.7/httplib.py", line 567, in read
    s = self.fp.read(amt)
  File "/usr/lib/python2.7/socket.py", line 380, in read
    data = self._sock.recv(left)
socket.timeout: timed out
Error - Could not install luts for aqua

HazyHu
- By gnwiii Date 2014-08-28 07:55
The install_ocssw.py script requires a robust internet connection, something that isn't always easy to find these days.   With a robust internet connection it is more convenient to have python scripts handle the downloads, but in some situations using a web browser or the wget program will successfully download files even though the python scripts fail.  

It looks like you are nearly finished, but for others in a similar situation it is worth considering Ocean Data Science Software Repositories where installation using the install_ocssw.py with the --local option is mentioned.

I think your installation is lacking only the final update_luts.py step to install the aqua (and any other processor you need) luts.   You should have a file home/seadas-7.0.2/ocssw/README which tells you how to set up a command-line environment for the OCSSW processing tools.   This isn't required to run the tools from the GUI, but as you can see, the bash command line makes it much easier to post details to this form.

You can check the command line setup as follows:


$ which update_luts.py
~/ocssw/run/scripts/update_luts.py
$ update_luts.py --help
Usage:
    update_luts.py [OPTIONS] MISSION

    MISSION is either seawifs, aqua, terra, aquarius, or viirsn

Options:
  --version          show program's version number and exit
  -h, --help         show this help message and exit
  -v, --verbose      print status messages
  --timeout=TIMEOUT  set the network timeout in seconds


It is worth trying to run the update_luts.py script again from the command line:


$ update_luts.py -v aqua
[ MODIS ]
+ leapsec.dat
+ utcpole.dat
[ MODIS: AQUA ]
+ OPER:xcal_modisa_axc26f_412.hdf
+ OPER:xcal_modisa_axc26f_443.hdf
+ OPER:xcal_modisa_axc26f_469.hdf
+ OPER:xcal_modisa_axc26f_488.hdf
+ OPER:xcal_modisa_axc26f_531.hdf
+ OPER:xcal_modisa_axc26f_547.hdf
+ OPER:xcal_modisa_axc26f_555.hdf
+ OPER:xcal_modisa_axc26f_645.hdf
+ OPER:xcal_modisa_axc26f_667.hdf
+ OPER:xcal_modisa_axc26f_678.hdf
+ OPER:xcal_modisa_axc26f_748.hdf
+ OPER:xcal_modisa_axc26f_859.hdf
+ OPER:xcal_modisa_axc26f_869.hdf
[ Done ]


If this fails on several attempts then you can use offline installation, e.g., download the required files (using the locations given in this thread) and manually move them to the appropriate directories.
- By hazyhu Date 2014-08-28 21:03
I  updated the luts under your direction, but I encountered another problem as below. How can I do?

hq@hq-Latitude-3330:~/seadas-7.0.2/ocssw/run/scripts$ python update_luts.py 
Usage:
    update_luts.py [OPTIONS] MISSION

    MISSION is either seawifs, aqua, terra, aquarius, or viirsn

Options:
  --version          show program's version number and exit
  -h, --help         show this help message and exit
  -v, --verbose      print status messages
  --timeout=TIMEOUT  set the network timeout in seconds
hq@hq-Latitude-3330:~/seadas-7.0.2/ocssw/run/scripts$ python update_luts.py Mission
Mission needs to be one of:
seawifs
aqua
terra
aquarius
viirsn
- By gnwiii Date 2014-08-29 07:19
You appear to be missing some background in linux command-line concepts (which is why I suggested looking at some introductory references in another post).  GUI interfaces allow you to avoid such details, but for those of us who can't always use the GUI (e.g., because we have a poor internet connection) the command-line provides a way to obtain detailed information about problems in a text form that can be posted to the forums.   Often the command-line version of the tools provides options that were not available in the GUI (if the GUI included every possible option you would need a very large screen to hold all the options, and it would be hard to find the important ones).  It is quite possible that your network problems can be resolved by increasing the "timeout" value (see below), something the GUI doesn't allow.

The first concept you need to study is the executable "PATH" variable.  You have set the current working directory to the location of the "update_luts.py" script and invoked it using the "python" program.  The
the instructions in "~/seadas-7.0.2/ocssw/README":


export OCSSWROOT=$HOME/seadas-7.0.2/ocssw
export OCSSW_DEBUG=0               # set to 1 for debugging
source $OCSSWROOT/OCSSW_bash.env


will set the "PATH" variable so that the processing commands, including "update_luts.py" can be run from any directory.   This is important because there are several
directories (bin, bin3, and scripts) that contain programs you may need.  You can check that this worked with the "which" command (as shown in the previous post).
Unfortunately, you need to run these every time you log in.  A good tutorial will describe ways to have these commands run for you when you log into your system. 

Many commands will give you a help message if you run them without any additional arguments:

$ which
Usage: /usr/bin/which [options] [--] COMMAND [...]
Write the full path of COMMAND(s) to standard output.

  --version, -[vV] Print version and exit successfully.
  --help,          Print this help and exit successfully.
  [...]


This brings us to the next concept: the shorthand notation used to describe command-line invocations, or "Usage".    The usage line:


update_luts.py [OPTIONS] MISSION


Gives the name of the program or script (e.g., "update_luts.py") followed by a pattern that describes the arguments accepted by the program.

The second entry, described as "[OPTIONS]", is enclosed in square brackets.  The brackets indicate that the entry is optional.  The section called "Options:" lists
the optional arguments accepted by the update_luts.py script.  In general, these optional arguments can be either a single letter preceded by a dash ("-") or a
multi-letter (long form) argument preceded by two dashes.  When you first use a new command or are trying to resolve a problem, you should look for options called
"verbose" or "debug".  In this case you might want to include the "--verbose" (or "-v") option in your command line.

Finally, you have the "MISSION" entry, whcih is mandatory.  On the command line, you need to replace "MISSION" with the actual name of the Mission whose luts you need.
Putting all this together, and using Mission="aqua", gives:  "update_luts.py --verbose aqua".  There is an example (using the  "-v" shorthand) earlier in this thread.

If you encounter network problems running "update_luts.py --verbose ..." you can try adjusting the network timeout value, e.g.,  "update_luts.py --verbose --timeout=20 aqua" (I chose 20 seconds because it is double the default value of 10 seconds, if that still fails, you can try 40 seconds or look for a better internet connection elsewhere).

All this may seem like a lot to deal with, but I think you are close to being able to use the processing tools.
Up Topic SeaDAS / SeaDAS - General Questions / off line SeaDAS install (locked)

Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill