When I run WDL workflows that have input{} and output{} blocks in addition to my command{} block, the Monitor tab shows that there are 3 jobs: "common", the actual task, and then "outputs" (screenshot below). The price for common and outputs has so far always been ~$0, making me wonder if these are just virtual.
Are VMs being spun up for the input and output blocks, or is this just a "virtual" artifact of how DNANexus structures the WDL conversion? Is this already addressed in a Best Practices document?
[Image: image]
Yes, this is a common pattern that only happen when you compile the applet from WDL code rather than using native DNAnexus applet. I honestly don't fully understand the architecture reason behind it. I understood that it got to do with allowing additional feature that WDL have and also for controlling input/output. The instance did run, but just for a second (it doesn't download, execute, or upload anything. It just relay info among jobs), so the cost is close to zero.
Comments
1 comment
Yes, this is a common pattern that only happen when you compile the applet from WDL code rather than using native DNAnexus applet. I honestly don't fully understand the architecture reason behind it. I understood that it got to do with allowing additional feature that WDL have and also for controlling input/output. The instance did run, but just for a second (it doesn't download, execute, or upload anything. It just relay info among jobs), so the cost is close to zero.
Please sign in to leave a comment.