Skip to content
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

Open
nr0cinu opened this issue Nov 18, 2024 · 4 comments
Open

Reproducible full report #819

nr0cinu opened this issue Nov 18, 2024 · 4 comments

Comments

@nr0cinu
Copy link

nr0cinu commented Nov 18, 2024

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

@rhpvorderman
Copy link
Collaborator

Would the json report fulfill these requirements? I do not see any speed reporting there.

@nr0cinu
Copy link
Author

nr0cinu commented Nov 18, 2024

Kind of, but that is the machine readable report, while the full report is human readable ;)

@marcelm
Copy link
Owner

marcelm commented Nov 18, 2024

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 -o to send trimmed reads to a file) and prints a progress report to stderr that already contains the runtime. This line:

[ 8<---------] 00:00:03     1,740,000 reads @   1.7 µs/read;  35.26 M reads/minute

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 -o?

@nr0cinu
Copy link
Author

nr0cinu commented Nov 18, 2024

Do you use Cutadapt with -o?

I do.

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.

that would work for me :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants