Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DM-21916: SQuaSH upload of Gen 3 Measurements #77

Merged
merged 14 commits into from Feb 23, 2021
Merged

Conversation

kfindeisen
Copy link
Member

@kfindeisen kfindeisen commented Feb 20, 2021

This PR moves the make_job_document.py script, and the jobReporter module that backs it, from metric-pipeline-tasks, and generalizes it to work on a broader range of instrumented Gen 3 repositories. This includes three UI changes:

  • the script is renamed to gen3_to_job.py, both because the old name is ambiguous in a package where most scripts make jobs, and to avoid confusion with the backwards-compatible version added on DM-21916: SQuaSH upload of Gen 3 Measurements faro#66.
  • the --metrics_package argument now defaults to allowing all metrics, regardless of namespace.
  • the --dataset_name argument now has no default, and is mandatory.

This PR also adds support for Faro's butler_generation tag to the existing Gen 2 MetricTask support code.

The jobReporter script has been moved from the 'tickets/DM-21916-transfer'
branch of lsst-dmsst/metric-pipeline-tasks (soon to be lsst/faro).
The metric-pipeline-tasks/faro repository used a 110-character limit;
verify uses 80.
This change allows for less code duplication between make_job_document.py
and a compatibility version in metric-pipeline-tasks/faro.
This change prevents any name collissions with the compatibility script
in metric-pipeline-tasks, and is less ambiguous in the context of other
lsst.verify scripts.
This allows package documentation builds with Documenteer 0.6.
This change requires moving the script's parser into python.
JobReporter continues to always provide a physical filter, but now only
deduces one if it's not in the data ID.
The previous defaults were customized for validate_drp processing. The
alternative CLI in metric-pipeline-tasks/faro keeps the defaults, for
those who want them.
Copy link
Contributor

@SimonKrughoff SimonKrughoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me

@kfindeisen kfindeisen merged commit 3e22ff4 into master Feb 23, 2021
@kfindeisen kfindeisen deleted the tickets/DM-21916 branch February 23, 2021 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants