Dear all,
Anyone know where to find all the ADL testing runs for all VIIRS EDRs, so that we can figure out how the inputs and outputs look like for certain EDR algorithm?
Thanks!
Jingfeng
Where to find all the example inputs for all EDR test runs?
Re: Where to find all the example inputs for all EDR test ru
The inputs and outputs are defined by the config guides in the $ADL_HOME/cfg directory. For instance, ProEdrViirsCloudsFirstController_CFG.xml is the config guide for ProEdrViirsCloudsFirstController.
Some of these files contain XML elements that look like <group name="Inputs"> and <group name=Outputs">. Look within these groups to find collection short names of inputs and outputs.
Some files don't have Inputs and Outputs. If a config guide has Controller in its name, it usually doesn't have Inputs and Outputs, and instead it will have an XML element <group name="SubAlgorithms">. In that case, you have to find other config guides that define the subalgorithms. For instance in ProEdrViirsCloudsFirstController_CFG.xml, there are four SubAlgorithms. The first one is ProAncViirsController, which has config guide ProAncViirsController_CFG.xml. That config guide also has SubAlgorithms, such as ProAncViirsGranulateTerrainGeopotentialHeight. The config guide for that one has Inputs and Outputs.
This gets pretty complicated, especially with ProAncViirsController. Most of the SubAlgorithms in ProAncViirsController actually run within ProSdrViirsController and don't have to run again in ProEdrCloudsFirstController.
A quick way to get a list of inputs is to run the ADL Chain Runner script with the -i option to list inputs for the algorithm chain. This lists inputs needed for all the algorithms up to and including the one you ask for. It actually lists more inputs than you really need, because sometimes an input that is required by one SubAlgorithm in an algorithm is produced as output by a previous SubAlgorithm. But it is much faster than looking through XML files.
The ADL Chain Runner is $ADL_HOME/script/runAdlChainRunner.pl. You need the environment variable DISPLAY to be set before you run it. (I don't think it matters what DISPLAY is set to but it must be set.) To get a usage message, run
$ADL_HOME/script/runAdlChainRunner.pl -h
Some other useful options are:
-p : preview only, ignore any run options (so don't actually run algorithms)
-v : validate inputs, check what inputs are currently in your DMS
Hope this helps....
Some of these files contain XML elements that look like <group name="Inputs"> and <group name=Outputs">. Look within these groups to find collection short names of inputs and outputs.
Some files don't have Inputs and Outputs. If a config guide has Controller in its name, it usually doesn't have Inputs and Outputs, and instead it will have an XML element <group name="SubAlgorithms">. In that case, you have to find other config guides that define the subalgorithms. For instance in ProEdrViirsCloudsFirstController_CFG.xml, there are four SubAlgorithms. The first one is ProAncViirsController, which has config guide ProAncViirsController_CFG.xml. That config guide also has SubAlgorithms, such as ProAncViirsGranulateTerrainGeopotentialHeight. The config guide for that one has Inputs and Outputs.
This gets pretty complicated, especially with ProAncViirsController. Most of the SubAlgorithms in ProAncViirsController actually run within ProSdrViirsController and don't have to run again in ProEdrCloudsFirstController.
A quick way to get a list of inputs is to run the ADL Chain Runner script with the -i option to list inputs for the algorithm chain. This lists inputs needed for all the algorithms up to and including the one you ask for. It actually lists more inputs than you really need, because sometimes an input that is required by one SubAlgorithm in an algorithm is produced as output by a previous SubAlgorithm. But it is much faster than looking through XML files.
The ADL Chain Runner is $ADL_HOME/script/runAdlChainRunner.pl. You need the environment variable DISPLAY to be set before you run it. (I don't think it matters what DISPLAY is set to but it must be set.) To get a usage message, run
$ADL_HOME/script/runAdlChainRunner.pl -h
Some other useful options are:
-p : preview only, ignore any run options (so don't actually run algorithms)
-v : validate inputs, check what inputs are currently in your DMS
Hope this helps....
Todd Simpson
Raytheon Company
Raytheon Company
Re: Where to find all the example inputs for all EDR test ru
Thank you very much, Todd,
These information are indeed very helpful!
Jingfeng
These information are indeed very helpful!
Jingfeng