SSEC forums

I have just downloaded ADL4.0 to our machine. However I found there are overlapped files in adlSoftware.tgz and idpsAlgorithms.tgz which result in errros in md5sum checks, because I untar idpsAlgorithms after adlSoftware, some of the files from the latter were overwritten:

md5sum -c adlSoftware.md5 | grep -v OK
ADL/ANC/Imakefile: FAILED
ADL/ANC/OMPS/include/ProAncOmpsClimoStructs.h: FAILED
ADL/CMN/Appl/src/Imakefile: FAILED
ADL/CMN/Imakefile: FAILED
ADL/CMN/ProcessingIO/src/Imakefile: FAILED
ADL/CMN/ProcessingIO/src/ProCmnQualityItem.cpp: FAILED
ADL/CMN/SrcAutogen/src/Imakefile: FAILED
ADL/CMN/Utilities/Dictionary/src/Imakefile: FAILED
ADL/CMN/Utilities/FileEndianConverter/src/AdlFileEndianConverter.cpp: FAILED
ADL/CMN/Utilities/FileEndianConverter/src/Imakefile: FAILED
ADL/CMN/Utilities/math/src/Imakefile: FAILED
ADL/EDR/Imakefile: FAILED
ADL/GIP/Imakefile: FAILED
ADL/GIP/VIIRS/TileInterfaces/src/Imakefile: FAILED
ADL/Geolocation/Imakefile: FAILED
ADL/Geolocation/Util/src/Imakefile: FAILED
ADL/Imakefile: FAILED
ADL/SDR/Imakefile: FAILED
ADL/build/envSetup.csh: FAILED
ADL/build/envSetup.ksh: FAILED
ADL/cfg/GuideList.txt: FAILED
ADL/imakeconf/PRO_Config: FAILED
ADL/include/viirs_RDR.h: FAILED
ADL/include/viirs_SDRf.h: FAILED
ADL/runDemoAlgorithms.ksh: FAILED
ADL/script/build_adl.pl: FAILED
ADL/script/checkEnv.pl: FAILED
ADL/script/runAllTests.ksh: FAILED
ADL/xml/Imakefile: FAILED


My question is: for the above files, should I use the ones in the adlSoftware.tgz or idpsAlgorithms.tgz?

Looks like you've discovered a minor flaw in how the code was packaged and/or the install instructions. But it shouldn't affect the end results.

As you've probably discovered:
--adlSoftware.tgz contains the files for the ADL "framework" only (formerly known as "ADL Lite"), but not IDPS algorithms. The adlSoftware.md5 file contains checksums for those files.
--idpsAlgorithms.tgz contains files related to IDPS algorithms as well as updates to a few files in adlSoftware.tgz. The idpsAlgorithms.md5 file contains checksums for those files. The file idpsAlgorithms.tgz is NOT a stand alone package. It must be installed on top of adlSoftware.tgz. There is no single .md5 file that contains checksums for all files plus the IDPS algorithms. The checksums for the framework files exist in the .md5 file for adlSoftware.tgz. But as you've discovered when you unpack the idpsAlgorithms.tgz file, it changes some files. You could use adlSoftware.md5 but you'll see the fails you have below. Or you could use idpsAlgorithms.md5, but you won't check the files in the framework (unchanged from adlSoftware.tgz).

The ideal way to do it would have been:
1. Untar adlSoftware.tgz
2. md5sum -c adlSoftware.md5
3. Untar idpsAlgorithms.tgz
4. md5sum -c idpsAlgorithms.md5

However, I don't think that order is described any place, so you didn't know you should have done it that way.

All of the files you listed appear to be ones modified by idpsAlgorithms.tgz, so I would expect the FAILED messages using adlSoftware.md5. You should be able to run "md5sum -c idpsAlgorithms.md5" and see no fails. If you can do that, I'm pretty confident you have it installed correctly.

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.

Just minutes ago I posted a response to the same question.

See viewtopic.php?f=24&t=228

Basically you can download the source (https://jpss-adl-wiki.ssec.wisc.edu/med ... /Downloads), but UW is still tweaking the virtual appliance.