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.
Topic SeaDAS / MODIS Direct Broadcast Support / Problems when updating LUTS in MODISL1DB v1.8 (locked)
I've installed MODISL1DB v1.8 on a 64-bit Red Hat 6.2 box like this:
curl -O ftp://samoa.gsfc.nasa.gov/seadas/modisl1db/modisl1db_1.8/modisl1db_linux.tar.gz
tar xf modisl1db_linux.tar.gz
export DBHOME=$PWD/modisl1db
source $DBHOME/run/scripts/modisl1db_env.bash
If run the LUT update script, I get the following output:
update_luts.py -v terra
Neither the L2GEN_ANC nor USER_L2GEN_ANC environment variables are set.
...using the current working directory for ancillary file download.
[ MODIS ]
+ leapsec.dat
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ utcpole.dat
[ MODIS: TERRA ]
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
- OPER:MOD02_Reflective_LUTs.V6.1.12.3a.hdf
- OPER:MOD02_QA_LUTs.V6.1.12.3a.hdf
- OPER:MOD02_Emissive_LUTs.V6.1.12.3a.hdf
+ OPER:MOD02_Emissive_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
+ OPER:MOD02_QA_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
+ OPER:MOD02_Reflective_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_Emissive_LUTs.V6.1.12.3a.hdf
+ EVAL:MOD02_Emissive_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ EVAL:MOD02_Emissive_LUTs.V6.1.14.1.hdf
Connection error, retrying up to 5 more time(s)
+ EVAL:MOD02_QA_LUTs.V6.1.12.3a.hdf
+ EVAL:MOD02_QA_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_QA_LUTs.V6.1.14.1.hdf
Connection error, retrying up to 5 more time(s)
+ EVAL:MOD02_Reflective_LUTs.V6.1.12.3a.hdf
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ EVAL:MOD02_Reflective_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_Reflective_LUTs.V6.1.14.1.hdf
[ Done ]
Is this normal behavior? It looks like it completed successfully, but the number of error messages is a bit disconcerting.
Liam.
curl -O ftp://samoa.gsfc.nasa.gov/seadas/modisl1db/modisl1db_1.8/modisl1db_linux.tar.gz
tar xf modisl1db_linux.tar.gz
export DBHOME=$PWD/modisl1db
source $DBHOME/run/scripts/modisl1db_env.bash
If run the LUT update script, I get the following output:
update_luts.py -v terra
Neither the L2GEN_ANC nor USER_L2GEN_ANC environment variables are set.
...using the current working directory for ancillary file download.
[ MODIS ]
+ leapsec.dat
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ utcpole.dat
[ MODIS: TERRA ]
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
- OPER:MOD02_Reflective_LUTs.V6.1.12.3a.hdf
- OPER:MOD02_QA_LUTs.V6.1.12.3a.hdf
- OPER:MOD02_Emissive_LUTs.V6.1.12.3a.hdf
+ OPER:MOD02_Emissive_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
+ OPER:MOD02_QA_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
+ OPER:MOD02_Reflective_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_Emissive_LUTs.V6.1.12.3a.hdf
+ EVAL:MOD02_Emissive_LUTs.V6.1.12.3b.hdf
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ EVAL:MOD02_Emissive_LUTs.V6.1.14.1.hdf
Connection error, retrying up to 5 more time(s)
+ EVAL:MOD02_QA_LUTs.V6.1.12.3a.hdf
+ EVAL:MOD02_QA_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_QA_LUTs.V6.1.14.1.hdf
Connection error, retrying up to 5 more time(s)
+ EVAL:MOD02_Reflective_LUTs.V6.1.12.3a.hdf
Connection error, retrying up to 5 more time(s)
Connection error, retrying up to 4 more time(s)
+ EVAL:MOD02_Reflective_LUTs.V6.1.12.3b.hdf
+ EVAL:MOD02_Reflective_LUTs.V6.1.14.1.hdf
[ Done ]
Is this normal behavior? It looks like it completed successfully, but the number of error messages is a bit disconcerting.
Liam.
Liam,
It's normal. A long story to explain why you see that, but since you get the [Done] message, all is well.
The disconcerting nature of the message was recently pointed out, so a future update to the script will
modify the message to be less ominous :)
Sean
It's normal. A long story to explain why you see that, but since you get the [Done] message, all is well.
The disconcerting nature of the message was recently pointed out, so a future update to the script will
modify the message to be less ominous :)
Sean
Topic SeaDAS / MODIS Direct Broadcast Support / Problems when updating LUTS in MODISL1DB v1.8 (locked)