Skip to content

Separate input and output path specification for flexibility #495

Description

@leewujung

A common use/test scenario is that many people pull input data from the same location but generate outputs (e.g., consolidate NASC files and reports) in a different location. So we should change the way input and output paths are set up now so that the input can use the same approach (right now a single DATA_ROOT) and the output paths can be specified in a more granular way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions