[Feature Request] Is it possible to store/save a starry model?
See original GitHub issueI have generated a load of starry models by fitting to data, and I would like to save them so I can plot the model in future notebooks. I don’t think there is a feature to do this, and it’s not possible to use pickle
on a starry.Map
object.
I think the best way for me to do this currently is to save all the map amplitudes and dictionaries of the orbital parameters, and then re-initialize the model when I want to use it in a new notebook. I can totally do this for now, but if there is an easy way to store the models and then re-open them I’d love to use it!
Thanks C
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Feature Requests: What are they and how to manage them
Feature requests are a form of product feedback you may frequently encounter as a SaaS product manager. They typically come in the form...
Read more >Feature Requests: How to Collect Them and Engage Users in ...
Inside the idea board, customers should be able to see what other users have suggested. This way, they can check if the idea...
Read more >Feature Request Template: How to Manage Suggestions at ...
Streamline and organize user feedback with this free feature request template. Available in Google Docs and Sheets (no email required).
Read more >How To Manage Feature Requests [Template included]
This guide will teach you everything about feature requests – how to process them, manage them, respond to them, prioritize them – so...
Read more >Increase your chances of a successful feature request
Feature requests by and large are submitted via ticket systems and a gatekeeper replies before consulting with product management as he or she...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Upvoting this to allow for the combination of emcee and multiprocessing which requires a pickleable object or a new star and planet object to be created at each iteration which is a huge overhead time cost (2 ms for v0.3 or 8 ms for v1.0; that’s 100-400% of my current likelihood computation time without using starry). On a related note, v1.0 takes an order of magnitude longer just to update the map (2 us for v0.3 versus 3 ms for v1.0 for a planet that has a ydeg=1). The “Pre-computing some matrices… Done.” being repeated a million times when initialising a planet in each MCMC step is also pretty rough and is something I’ve commented out locally.
Well, after a clean install I got your snippet there working, and I coded up this:
I’m unsure, however, if that’s the correct approach here, so any guidance would be appreciated.