Improvement Description
Currently launching q2-deblur will create a deblur.log file wherever the command was run, assuming as a step baked in to deblur itself. It would be nice if this were able to be optionally created, or controllable as to where it gets placed, via a Q2 artifact or piping the output somewhere (directly into provenance?), or was just catchable output, a la q2-dada2 information.
Improvement Description Currently launching
q2-deblurwill create adeblur.logfile wherever the command was run, assuming as a step baked in todebluritself. It would be nice if this were able to be optionally created, or controllable as to where it gets placed, via a Q2 artifact or piping the output somewhere (directly into provenance?), or was just catchable output, a laq2-dada2information.