On modifying attributes

[olsonanl]

Is it possible to modify the attributes of a task while the task is running? I am running the RASTtk pipeline under AWE, and would like to be able to use the attributes in AWE as a mechanism for stashing status of the individual pieces of the pipeline. If it were possible to update the userattr at runtime that would probably suit. I didn't see anything in the API docs that seemed relevant.

Thanks,
--bob

[teharrison]

Currently the attributes of a task are immutable after the workflow is
submitted. In our pipeline I have been stashing status of individual tasks
in Shock. The AWE client places the task attributes as a JSON file in the
task working dir, then whatever script my task runs loads that (along with
anything else it calculates) into the attributes of the output Shock
nodes. I have also implemented a mechanism to have an AWE task update the
attributes of a Shock node created in a previous task without making a new
Shock node.

• Travis

On Mon, Jul 7, 2014 at 1:40 PM, olsonanl notifications@github.com wrote:

Is it possible to modify the attributes of a task while the task is
running? I am running the RASTtk pipeline under AWE, and would like to be
able to use the attributes in AWE as a mechanism for stashing status of the
individual pieces of the pipeline. If it were possible to update the
userattr at runtime that would probably suit. I didn't see anything in the
API docs that seemed relevant.

Thanks,
--bob

—
Reply to this email directly or view it on GitHub
#254.

[narayandesai]

For my 2c, I think it would be really cool if there were a persistent per-job scratchpad between job stages. the json could be mapped into the execution context, and copied out at the end.

[wgerlach]

I am closing this old ticket. If such a feature is still relevant, we would have to discuss this in context of CWL workflows, which soon will be supported by AWE.