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

Docs: "Performance and Parallelization" appendix out of date #23

Closed
josePhoenix opened this issue Nov 14, 2014 · 4 comments
Closed

Docs: "Performance and Parallelization" appendix out of date #23

josePhoenix opened this issue Nov 14, 2014 · 4 comments
Assignees
Labels
Milestone

Comments

@josePhoenix
Copy link
Collaborator

A user asked me about webbpsf.settings.use_multiprocessing and it looks like that's no longer supported. He saw it in Appendix: Performance and Parallelization, which we should update before releasing 0.3.0.

@mperrin
Copy link
Owner

mperrin commented Nov 14, 2014

It's actually just a setting in poppy now. For a while I had cloned those settings into webbpsf also, and the webbpsf setting would get applied to update the poppy setting, but in retrospect that was a bad idea and just introduced needless complexity. The functionality is all there in poppy's config and we should update the docs accordingly.

Just got off the plane back from Chile. Let's plan to meet Mon?

  • Marshall

On Nov 14, 2014, at 10:48 AM, Joseph Long <notifications@github.commailto:notifications@github.com> wrote:

A user asked me about webbpsf.settings.use_multiprocessing and it looks like that's no longer supported. He saw it in Appendix: Performance and Parallelizationhttp://www.stsci.edu/%7Emperrin/software/webbpsf/performance.html, which we should update before releasing 0.3.0.


Reply to this email directly or view it on GitHubhttps://github.com//issues/23.

@josePhoenix
Copy link
Collaborator Author

I grepped around and pointed the user towards the poppy setting, so that's good to hear it does what he wanted.

@mperrin mperrin added the docs label Nov 17, 2014
@josePhoenix josePhoenix mentioned this issue Nov 24, 2014
15 tasks
@josePhoenix josePhoenix modified the milestone: 0.3 Dec 11, 2014
@mperrin
Copy link
Owner

mperrin commented Jan 21, 2015

Was this handled as part of the docs refresh you just checked in, or is there still more to do on this one?

@josePhoenix josePhoenix self-assigned this Jan 23, 2015
@josePhoenix
Copy link
Collaborator Author

Yes, this is done! 7ae1ddc

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

No branches or pull requests

2 participants