Hi,
There are many existing features to control where a job gets run, and to categorize different jobs for different workers in both simple and more complex ways. They are outlined in the second half of this tutorial:
https://pythonhosted.org/FireWorks/controlworker.html
Please take a look and let me know if that solves most if not all of your issue.
If you are looking to manually launch a specific FireWork, a few notes on that:
i) The “priority” will determine which jobs gets run first. If you modify the priority to be very high, it will be run next: https://pythonhosted.org/FireWorks/priority_tutorial.html
ii) The “rlaunch singleshot” command actually has a “–fw_id” option that lets you run a very particular FireWork.
iii) Note that the “qlaunch” command does not have a “–fw_id” option, but user gpetretto is working on a fork of FWS that has that feature along with a bunch of other things. He will be merging his code when ready; no due date but I expect in the next month or two.
Best,
Anubhav
···
On Mon, Aug 24, 2015 at 7:00 AM, Chris H [email protected] wrote:
I guess one way to phrase this without reworking the code is to have a separate mongodb collection and/or db for serial workflows, or a process that creates one collection per user behind the scenes.
Am I thinking about that correctly? But it still seems like “run this workflow by id” is a desirable code feature, versus the rapidfire generic “run all ready workflows”.
–
You received this message because you are subscribed to the Google Groups “fireworkflows” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/023455d4-ff3a-4c5e-a9c8-f05b03aff2da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.