WDL: best way to tell when a task with no output is done?

myourshawmyourshaw University of ColoradoMember

I'm developing a pipeline that includes some tasks that do not produce an output file but only write to a database. Other tasks should not run until the db-writing tasks are complete, because they read the db. I have been setting stdout() as a dummy output for the db-writing tasks [stdout is empty], and then requiring that task's stdout as an input to the downstream tasks. Is there a more elegant or standard way to set this up?

Tagged:

Best Answer

Answers

Sign In or Register to comment.