I have two installations of SeaDAS v1.3, one in McMurdo, Antarctica, and one in Tromsų, Norway. In both places, the modis_update_luts.csh script apparently found a new LUT file and rewrote the modisl1db_env.* files. In McMurdo, however, it did so incorrectly. See the contents of the modisl1db_env.csh file below, and note that there is no file name assigned to the AQUA_REFL_LUT variable:
setenv SEADAS $DBHOME
setenv SDSDATA $DBHOME/data
setenv MODIS_GEO .
setenv MODIS_L1A .
setenv MODIS_L1B .
setenv MODIS_ATTEPH $SDSDATA/modis/atteph
setenv AQUA_REFL_LUT /home/oper/modisl1db/data/modisa/cal/
setenv AQUA_EMIS_LUT /home/oper/modisl1db/data/modisa/cal/MYD02_Emissive_LUTs.V5.0.7.13a.hdf
setenv AQUA_QA_LUT /home/oper/modisl1db/data/modisa/cal/MYD02_QA_LUTs.V5.0.7.13a.hdf
setenv TERRA_REFL_LUT /home/oper/modisl1db/data/modist/cal/MOD02_Reflective_LUTs.V5.0.6.20.hdf
setenv TERRA_EMIS_LUT /home/oper/modisl1db/data/modist/cal/MOD02_Emissive_LUTs.V5.0.6.20.hdf
setenv TERRA_QA_LUT /home/oper/modisl1db/data/modist/cal/MOD02_QA_LUTs.V5.0.6.20.hdf
set path=(. $DBHOME/scripts $DBHOME/bin $path)
I can't tell you how the circumstances differed between the two sites. Maybe the retrieval of the new LUTs failed midstream, maybe not.
HAVING SAID THAT, I see that both sites just got new LUTs (today), and both have correctly rewritten modisl1db_env.* files. So, you probably don't want to waste time investigating this!
Jeff
If anybody cares (we do!), it just happened again. This time, however, it was the Terra LUT entry that wasn't updated. As before, it had the path, but no file name.
Jeff
By mark
Date 2006-10-23 20:01
Jeff,
Does this happen every time, or just intermittently? Also, can you provide us with the script output so that maybe we can get an idea where it is failing?
Thanks, Mark
Topic SeaDAS / MODIS Direct Broadcast Support / modis_update_luts.csh incorrectly writes modisl1db_env.* (locked) (11902 hits)
