Individual VIIRS algorithms in runDemos

[houchin]

Hi,

I have installed and built ADL 3 per the instructions on the wiki, and it appears to have built normally. In the runDemos support script, it wants to run ProSdrViirsVerifiedRdr.exe, ProSdrViirsGeo.exe and ProSdrViirsCal.exe. However, when I look at what was actually built, all that I see there is the ProSdrViirsController.exe. I also don't see any of the input config files named like "viirsVerifiedRdrLwFile.xml".

Did I miss installing or configuring something?

[JimBiard]

Hey.

That's just how it should be. In ADL 3.0 introduces the controller object, which is able to chain together groups of algorithms. The ProSdrViirsControllerLwFile.xml is the sample config file to use, and it specifies which granule to process. It also specifies loading the ProSdrViirsController_CFG.xml file. This specifies the algorithms to run. The CFG file provided runs the algorithms you want run, as well as a number of others. If you want to limit it to running just the three you mentioned, you can make a new CFG file that doesn't include the other algorithms (name it ViirsControllerBasic_CFG.xml, for example), and make a new Lw File (name it ViirsControllerBasicLwFile.xml) that references your new CFG file. Run with the new Lw file and it will run the algorithms you want run.

Grace and peace,

Jim Biard

[houchin]

So the short answer is the runDemos script is not updated for ADL 3?

Once I create the new files you mention, do I need to rebuild ADL, or is this just a runtime specification?

[JimBiard]

No recompilation is required.

Hmmmm... I don't have a runDemos script in my distribution. The runDemoAlgorithms script runs the VIIRS SDR controller app correctly. I will say, though, that I have found that a number of the EDR apps are failing, and it seems to be because the input data folders don't have correct contents. I haven't had time to see if I did something wrong there or not.

[houchin]

runDemos is part os the UW provided support scripts.

[scottm]

runDemos is used with ADL 2.0.

ADL 3.0 has a script in the ADL directory to run groups of algorithms. Check the option for individual sensors.

[kbisanz]

No recompilation is required.

Hmmmm... I don't have a runDemos script in my distribution. The runDemoAlgorithms script runs the VIIRS SDR controller app correctly. I will say, though, that I have found that a number of the EDR apps are failing, and it seems to be because the input data folders don't have correct contents. I haven't had time to see if I did something wrong there or not.

Regarding the data, in ADL 3.0 the code was separated from the data and the data broken up into several packages to make downloads smaller. It's possible you need to download additional data from the UW site.

[kbisanz]

Hi,

I have installed and built ADL 3 per the instructions on the wiki, and it appears to have built normally. In the runDemos support script, it wants to run ProSdrViirsVerifiedRdr.exe, ProSdrViirsGeo.exe and ProSdrViirsCal.exe. However, when I look at what was actually built, all that I see there is the ProSdrViirsController.exe. I also don't see any of the input config files named like "viirsVerifiedRdrLwFile.xml".

Did I miss installing or configuring something?

The executables ProSdrViirsVerifiedRdr.exe, ProSdrViirsGeo.exe, and ProSdrViirsCal.exe (among others) did exist in ADL 2.0, but do not exist in ADL 3.0. In ADL 3.0 the executables reflect what is running in the operational IDPS system (with controllers to run multiple sub algorithms). If you have the executables you listed, it sounds like ADL 3.0 was installed over the top of ADL 2.0. I would not recommend doing that. It would be best to install ADL 3.0 in its own empty directory.

[scottm]

The runDemos script is for ADL 2.0 only.

Please use runDemoAlgorithms.ksh in the ADL root directory.

[JimBiard]

No recompilation is required.

Hmmmm... I don't have a runDemos script in my distribution. The runDemoAlgorithms script runs the VIIRS SDR controller app correctly. I will say, though, that I have found that a number of the EDR apps are failing, and it seems to be because the input data folders don't have correct contents. I haven't had time to see if I did something wrong there or not.

Regarding the data, in ADL 3.0 the code was separated from the data and the data broken up into several packages to make downloads smaller. It's possible you need to download additional data from the UW site.

I pulled down all the DVD images, and I thought I had installed them all. That doesn't mean I did, though. I got pulled off on a different fire drill and haven't got back to it yet. I'll be certain to let you know what happened once I get back on it.