Settings 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.

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.

The settings.yaml file is something that exists under conf directory for missions like NISAR and SWOT. This file contains all PGE product types and its naming convention and metadata extraction information.

For the purposes of Chimera we need to know:

The HySDS venue. This is read in from the sds config file. Leave ln 1 below untouched.
Whether to simulate the PGE run if the actual PGE is not available.
The Composite Release ID of the PGE (mission term for version of PGE)
For every PGE, which type of job to submit and which queue to submit the job to.

It needs to be included in the settings.yaml file as follows:

VENUE: '{{VENUE}}'
PGE_SIMULATION_MODE: !!bool true
CRID: ID

CHIMERA:
    JOB_QUEUES:
        PGE_1: queue1
        PGE_2: queue2
    JOB_TYPES:
        PGE_1: job-PGE_1
        PGE_2: job-PGE_2

To learn how to write this file, read Update settings.yaml file

Related Articles:
Page: Chimera Config File Page: Input Preprocessor Page: PGE Config File Page: PGE Execution Page: Post Processor Page: Settings File

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?

Yes No

Contribution History:

Topher Allen (1586 days ago)
Namrata Malarout (1624 days ago)

Subject Matter Expert:

@Namrata Malarout

Find an Error?

Is this document outdated or inaccurate? Please contact the assigned Page Maintainer:

@Lan Dang