search

dchackett / taxi

Lightweight portable workflow management system for MCMC applications
MIT License
3 stars 1 forks source link

Allocation specified in taxi.sh #24

Closed dchackett closed 6 years ago

dchackett commented 7 years ago

At present, taxi.sh for (e.g.) running on Janus includes a line at the top specifying which allocation to use. This needs to be specified elsewhere, as taxi.sh should only be specific to the computer, not the project/allocation/user.

It might be sufficiently graceful to change this to just something the user provides in the run-specification script. This also opens up the possibility of having taxi choose between multiple allocations, which might be useful.

dchackett commented 6 years ago

Pool now keeps track of both which taxi an allocation should run on, and which queue (i.e. machine, e.g. bc or ds on USQCD machines) the taxi should be submitted to. All further action to do with queues and allocations occurs in local_queue.py. fnal localization uses allocation appropriately, cu_hep localization warns if an allocation was specified.