Has anyone successfully been able to use the category property we are using fw 1.05

[an...@os3d.se]

Has anyone successfully been able to use the category property. We are using fw 1.05 

we set the category in the launch  yaml on the worker nodes

and we set a _category in the job description..

spec:

  _category: testcategory

All fireworkers in this test has been started with a certain category. I have one specific node that is the only one that can run a specific job.. 

All fireworks has a _category set..

But when I add the job that should ONLY be run on the specific machine.. other nodes starts picking up the job. Even though they have another category set.

Is there something that can override the category setting? It feels like the category setting is ignored.

regards,

Anton Berg 

[Anubhav Jain]

Hi Anton,

My guess is that you did not set a category for the remaining FireWorkers that are unintentionally pulling your job. If you do not set a category for those FireWorkers, this defaults to pulling "any" category.

Please see the docs on controlling the worker:

https://pythonhosted.org/FireWorks/controlworker.html

which explains this and also tells you other ways to control the resource, including the _fworker variable.

Finally, note that some of this relevant code was reworked into the current version of FWS. I don't think it will affect what you are seeing, but there are other features and behavior that may be affected, particularly for certain types of raw queries within the FireWorker.

Best,

Anubhav

--
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 fireworkflow...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/3284767b-9ed5-4ea0-9999-151ef7db5ac9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.