Earthdata Forum

Posted: **Tue Apr 22, 2025 11:25 am America/New_York**

Good Morning!

I upgraded from OCSSW 2025.V0 to 2025.V1, after which I started getting a new error message.

I'm calling a command of the form:

Code: Select all

l2gen maskland=0 proc_cloud=0  maskcloud=on cloud_thresh=0.1  maskhilt=0 maskstlight=0 resolution=1000 gas_opt=8 l2prod=rhos_NNNN,rhos_MMMM,rhos_PPPP ifile=S20250420170000-L1A-NPP-OBPG.nc geofile=S20250420170000-GEO-NPP-OBPG.nc ofile=/data/NC/L2/FAI/2025-04-20/S20250420170000-L2-NPP-OBPG.nc.tmp

It runs for a while producing warnings (or maybe those are non-fatal errors?) about vectorAtSat() failure before emitting the following error and exiting:

Code: Select all

VcstCmnGeo::NOVAS-C function local_planet returned error code.
VcstCmnGeo::Lunar vectorAtSat() failure at scan 201
VcstCalNetcdfInputItem::readNetcdfDynamic() Failure opening LUT file: /marine-services/ocssw/var/viirsn/cal/OPER/
VIIRS_NPP_CAL_RSB_DYNAMIC_LUT_20111122_20240107_v3.1.0.25_20230901_obpg.nc
VcstCalNetcdfInputItem::getData(iet) Failure reading netCDF dynamic file for LUT F_PREDICTED_LUT
VcstObc:: LUT initialization failure
VcstViirsCal::Granule initialization failure

Error in initialization.

I ran update_luts, tried again and got the same results

.

I then looked in /marine-services/ocssw/var/viirsn/cal/OPER/ and there was a file

"VIIRS_NPP_CAL_RSB_DYNAMIC_LUT_20111122_20250428_v3.1.0.39_20241218_obpg.nc"

but no

"VIIRS_NPP_CAL_RSB_DYNAMIC_LUT_20111122_20240107_v3.1.0.25_20230901_obpg.nc"

So based on the datecodes in the filename it is failing because I have a newer RSB LUT file than expected???

As an experiment I created a symbolic link from the older filename to the newer one and that granule (and many others) processed normally - so it works with a "hacky solution" but I would really like to know the "correct" fix.

How is this RSB LUT filename determined? Is there some environment variable and/or configuration parameter that I can use to adjust it

Thank you!
-Andrew L.

Posted: **Tue Apr 22, 2025 2:27 pm America/New_York**

Andrew,

The issue is that the LUT in var was updated after the tag was released. You can resolve the issue by updating $OCDATAROOT/viirs/npp/instrument_defaults.par to include the updated LUT from var (i.e. replace the path of rsb_dynamic_lut_file to point to the one in $OCVARROOT/viirsn/cal/OPER/)

Sean

Posted: **Fri Apr 25, 2025 2:52 pm America/New_York**

Sean,

Thank you for your reply, I'll try it once I get some VIIRS data far enough through the system to be able to test it.

I'd like to make a suggestion, please, that future versions of l2gen by default look for the most recent calibration files in the appropiate directory rather than it being set manually in a configuration file.

-Andrew L.

Posted: **Fri Apr 25, 2025 2:54 pm America/New_York**

Already done, just not released

Posted: **Fri Apr 25, 2025 3:07 pm America/New_York**

Great minds think alike

Earthdata Forum

SeaDAS RSB LUT filename issue

SeaDAS RSB LUT filename issue

Re: SeaDAS RSB LUT filename issue

Re: SeaDAS RSB LUT filename issue

Re: SeaDAS RSB LUT filename issue

Re: SeaDAS RSB LUT filename issue