-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reproducible full report #819
Comments
Would the json report fulfill these requirements? I do not see any speed reporting there. |
Kind of, but that is the machine readable report, while the full report is human readable ;) |
Good idea. Note that I purposefully omitted runtime from the JSON output so that it would be reproducible. But the normal report is older, and I didn’t think about reproducible output at that time. I’m trying to avoid adding more command-line options if I can, so I’m wondering whether writing the final runtime to stderr would be an option. Cutadapt currently sends the report to stdout (if you use
So information about runtime is already available and doesn’t actually need to be in the part of the report that is sent to stdout. @nr0cinu Do you use Cutadapt with |
I do.
that would work for me :) |
Hi,
would be nice if there would be a command line flag to enable reproducible full reports, i.e., the report is always the same if the input is the same. Right now, with the processing time and speed being added, the report always changes.
Thanks,
Bela
The text was updated successfully, but these errors were encountered: