SSEC forums

Looks like you've discovered a minor flaw in how the code was packaged and/or the install instructions.

When will ADL4.0 be ready for distribution? It's been weeks with no announcement.

Hi, Liqin - ProCmnMethodAudit.cpp|206|ProCmnViirsRDRItem[18ProCmnViirsRDRItem]::swapAggZoneOrCalDataZoneBlock(VIIRS-SCIENCE-RDR) [0x12658c90] ROOT PRO_FAIL did not find synch word 0xff000063; found 0xdeaddead instead. from file ProCmnViirsRDRItem.cpp, line 1413 We've had the same error; it can occur...

It was announced at the Common CM workshop that ADL 4.0 had just been released. Judging from the quite recent updates to ADL 4.0 folders in the download area, it seems that the SSEC team is actively working on getting it ready for us users.

Any ETA? Thanks!

The examples are given with the default value for proxy data:
export NPP_GRANULE_ID_BASETIME=1300968033000000

NPP data was generated with the updated granule basetime:
export NPP_GRANULE_ID_BASETIME=1698019234000000

The ADL unpacker works, but gives me the same file I could download from the USNO. No point in grabbing the H5 file when we can download the content directly. Carol Davidson gave me her converter a few weeks ago, but it requires the Land PEATE environment. I wrote a lighter-weight version in IDL, wh...

ADL expects USNO-PolarWander-UT1-ANC to be input as a binary/metadata file pair. USNO-PolarWander-UT1-ANC files are delivered in HDF5. ADL_Unpacker outputs an ASCII file, in the same format as the USNO's finals2000A.all. I know others have developed tools to write the equivalent binary. Is there on...

ADL 3.1 envSetup.* includes a value for NPP_GRANULE_ID_BASETIME: # The value of this variable affects the granule ID utility. It is set # correctly for data that ships with ADL and prelaunch proxy data. If real # NPP data is processed by ADL, this variable will need to be updated. That # value will ...

Scott M:

Could you notify us when there are new downloads available?
Either email or the ADL Announcements board would work for me.

Thanks,
Gwyn

Those vars are set in envSetup.csh, but not in envSetup.ksh - at least not after running support/installAdl3.0.sh. We'll have to add them ourselves, using envSetup.ksh.org for reference.

Yeah, they didn't reply to my post but did put up a new version.

We're using gcc 4.5.2, with libz not installed at the system level. I'm having to make some changes to get it to compile here; will summarize when it's working.