Chimera Config File
Confidence Level Moderate This article includes input from several JPLers. Multiple subject matter experts can indicate that a page is more frequently reviewed and updated. |
|---|
This file is intended to tell Chimera which module to import and the adaptation class for every Chimera step. For each adaptation step the class must be subclass of the respective Chimera classes.
The module path should be the path to the implemented subclasses.
Use the following template:
# module_path is a path to where the given class can be found
# This tells Chimera how to load in the precondition functions class in order to do the input preprocessor step.
# class_name must be a subclass of Chimera's PreConditionFunctions class.
preprocessor:
module_path: [path.to.preconditions.module]
class_name: [Name of PreConditionFunctions Adaptation SubClass]
# This tells Chimera how to load in the job submitter class in order to do the PGE job submission step.
# class_name must be a subclass of Chimera's PgeJobSubmitter class.
job_submitter:
module_path: [path.to.pge_job_submitter.module]
class_name: [Name of PgeJobSubmitter Adaptation SubClass]
# This tells Chimera how to load in the post processor class in order to run any custom post processing.
# class_name must be a subclass of Chimera's PostProcessFunctions class.
postprocessor:
module_path: [path.to.post_processor.module]
class_name: [Name of PostProcessFunctions Adaptation SubClass]Details of how the module_path and class_name are used can be found on the Wiki pages of each Chimera step.
Related Articles: |
|---|
Have Questions? Ask a HySDS Developer: |
Anyone can join our public Slack channel to learn more about HySDS. JPL employees can join #HySDS-Community
|
JPLers can also ask HySDS questions at Stack Overflow Enterprise
|
Page Information: |
|---|
Was this page useful? |
Contribution History:
|
Subject Matter Expert: @Namrata Malarout
|
Find an Error? Is this document outdated or inaccurate? Please contact the assigned Page Maintainer: @Lan Dang |