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

Parallel Processing in RMG-Py #31

Closed
rwest opened this issue Apr 16, 2010 · 2 comments
Closed

Parallel Processing in RMG-Py #31

rwest opened this issue Apr 16, 2010 · 2 comments
Labels
abandoned abandoned issue/PR as determined by actions bot stale stale issue/PR as determined by actions bot Status: Stale This issue is out-of-date and may no longer be applicable

Comments

@rwest
Copy link
Member

rwest commented Apr 16, 2010

All the computers we will be running RMG on from now on have several cores, and many of them are even clusters. It would be nice to run code on all of them at once to reduce the wall-time of our calculations.
This issue is to keep a record of work towards parallelizing [parts of] RMG-Py.

@rwest
Copy link
Member Author

rwest commented Apr 16, 2010

My first attempt was to parallelize the "react_entire_core_with_new_species" that happens when a species is added to the core. i.e. the old code from model.py
for coreSpecies in self.core.species:
if coreSpecies.reactive:
rxnList.extend(reaction.kineticsDatabase.getReactions([newSpecies, coreSpecies]))
This loop was expanded into separate tasks running on a pool of processes.
This led up to 7910541.
The problem is that each process that is creating new reactions, uses the same reaction numbers, as it doesn't know about reactions made by the other processes.

@pierrelb pierrelb added the Status: Stale This issue is out-of-date and may no longer be applicable label Aug 28, 2015
@github-actions
Copy link

This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days.

@github-actions github-actions bot added the stale stale issue/PR as determined by actions bot label Jun 22, 2023
@github-actions github-actions bot added the abandoned abandoned issue/PR as determined by actions bot label Jul 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned abandoned issue/PR as determined by actions bot stale stale issue/PR as determined by actions bot Status: Stale This issue is out-of-date and may no longer be applicable
Projects
None yet
Development

No branches or pull requests

2 participants