LSST DESC Note: Machine Learning Prediction of PhoSim CPU Time #452
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.
@digel
Hi Seth! Here's a branch and PR for your DESC Note on the PhoSim CPU Time prediction work. Looking at the code and the example hack day notebook you made with @humnaawan and @tmcclintock, I think this Note would work well as an IPython notebook, that explains the problem and your solution before demonstrating the prediction code (now checked in to the Twinkles repo as a python module) on the Run 3 OpSim data (which the notebook could download via
$ curl
). I think you have done a lot of this analysis already, and the example notebook contains useful plotting code. What do you think?I guess Humna and Tom may have some spare cycles to help out with such a notebook. (Just remember to only check in after you have cleared the nb outputs, to make it easy for git to merge contributions from multiple authors). Alternatively I'm sure they'd be happy to help with text editing etc!
I was going to run
start_paper
to make a Note folder, but then realized that as PubMgr you might like to do this yourself so that you can see how it works (and what is missing from the docs etc :-) A good short title to use could be "phosim-cpu-prediction" so that the folder comes out asdesc-0000-twinkles-phosim-cpu-prediction
.