-
Notifications
You must be signed in to change notification settings - Fork 2
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
PREOPS-4646: feature- Support addition of opsim data to an archive for use by schedview-prenight #20
Merged
+798
−7
Merged
PREOPS-4646: feature- Support addition of opsim data to an archive for use by schedview-prenight #20
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
e2ac8e7
Start of sim archiving
ehneilsen 503ff55
Add opsim archive validation function
ehneilsen 7736e46
Add validation and contents to sim archive tests
ehneilsen 9b56db7
include environment files in opsim archive
ehneilsen 0e95d4f
Add tags and label to sim metadata
ehneilsen 0983f8d
add func for querying sim archive metadata
ehneilsen 8ce01c7
replace printing with logging
ehneilsen 0525e94
follow module conventions
ehneilsen 18dd899
include lsst.resources to support sim_archive
ehneilsen ef07272
initial cli for sim_archive
ehneilsen 6d8271a
include conda package dependency
ehneilsen bdfd4fb
Support getting sunset from local date
ehneilsen f7bdb65
driver to run sim and archive results in one command
ehneilsen 7a50d30
match api if drive_sim to sim_runner
ehneilsen 05c0ae7
improve help for make_sim_archive
ehneilsen bf9afed
be robust wrt absent rewards in archive
ehneilsen 554b4cc
set nside in DDFs so roi works correctly
ehneilsen 13b1f32
install lsst.resources in github actions
ehneilsen b05caea
skip test that requires schedview if it is not installed.
ehneilsen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading status checks…
install lsst.resources in github actions
commit 13b1f3256d5b6f10369685b2a5809c4391182dc6
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should get this into conda-forge ...
but I'm wondering if we can't add it to the requirements.txt file anyway?
If it's not necessarily for most uses, but only for the ones we're in control of for now, this is probably fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, requirments.txt is just a simple text list of packages, and I don't think this format supports pip/pypi packages. Such packages are supported by the conda's yaml format for specifying environments, and perhaps we should move to that format, but maybe that should be done as a separate issue (and corresponding PR).