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

LSST DESC Note: Machine Learning Prediction of PhoSim CPU Time #452

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

drphilmarshall
Copy link
Contributor

@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 as desc-0000-twinkles-phosim-cpu-prediction.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 41.35% when pulling 11c5f35 on phosim-cpu-prediction-note into aaa1844 on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants