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

Set surface_quality command not multi-threading #410

Open
sbembenek18 opened this issue Dec 3, 2024 · 2 comments
Open

Set surface_quality command not multi-threading #410

sbembenek18 opened this issue Dec 3, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@sbembenek18
Copy link

I know Pymol will run certain commands in parallel/multi-thread (e.g. ray tracing).

I'm wondering if the command: can 'set surface_quality' can be handled this way.

For example, if you're looking for high quality surfaces and run (like: 'set surface_quality, 4'), it's a lot of overhead depending on how many entries you have, and would be something you would want all the processors working on.

@JarrettSJohnson JarrettSJohnson added the help wanted Extra attention is needed label Jan 25, 2025
@JarrettSJohnson
Copy link
Member

I had a mostly working implementation that I might throw up on a branch; but I am unsure if I have the time to finish it. If there's anyone that feels like they can take that to completion, let me know.

Relevant code in master:

SurfaceJob* surf_job = SurfaceJobNew(G);

@sbembenek18
Copy link
Author

Thanks for the update. I'm still interested in this feature and think that overall this would be a real value add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants