LSST DESC Note: The Twinkles1 PhoSim Pipeline and Results #451
Conversation
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
16 tasks
|
@drphilmarshall That all sounds very reasonable. |
|
Rock on! Feel free to use this thread to ask me, @danielsf, @tony-johnson or anyone else for input / help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @TomGlanzman! I started an LSST DESC Note for you, check it out:
https://github.com/LSSTDESC/Twinkles/blob/twinkles1-phosim-pipeline-note/doc/LSST_DESC_Notes/desc-0000-twinkles-1-phosim-pipeline/main.rst
As you can see, the development branch for this note is called
twinkles1-phosim-pipeline-note. We won't merge this PR until you're happy with the Note, and the group has reviewed it. I don't think this needs to be a long Note, but it should include listings of the commands that you used to execute the Run 3 image simulation jobs, I think - and then some results of the kind you've been posting to the issue threads (on job success rate, wallclock vs CPU time, long jobs, and so on). What do you think?