Add AlchemiscaleClient
methods set_tasks
and set_transformations_tasks
#293
Milestone
AlchemiscaleClient
methods set_tasks
and set_transformations_tasks
#293
There are users and downstream projects, such as
asap-alchemy
, that are more interested in ensuring that a certain number ofTask
s exist perTransformation
than in creating newTask
s.This is especially the case when a user creates many iterations of
AlchemicalNetwork
s in the sameScope
that feature manyTransformation
s in common. In this scenario, simply callingcreate_tasks
orcreate_transformations_tasks
on everyTransformation
of the submittedAlchemicalNetwork
may generate more work than is necessary given existing results. A user that wants to only create newTask
s for entirely newTransformation
s would need to do a number of client calls to determine whichTransformation
s have noTask
s before creating new ones.To address this, we should create two new methods on the
AlchemiscaleClient
:set_tasks
: set the minimum number ofTask
s on the givenTransformation
(and optionallyextends
ing anotherTask
)set_transformations_tasks
: set the minimum number ofTask
s for multipleTransformation
(and optionallyextends
ing anotherTask
), in a single callThese methods are functionally idempotent versions of
create_tasks
andcreate_transformations_tasks
that already exist in theAlchemiscaleClient
. They should take the same inputs as these existing methods, but will only create newTask
s where an insufficient number already exist.The text was updated successfully, but these errors were encountered: