-
Notifications
You must be signed in to change notification settings - Fork 2
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
Run FASTQC on a subset of reads #74
Labels
done
Issues that have been addressed in dev branch, but not reflected in master branch
enhancement
New feature or request
priority_1
time&cost
Changes to improve the pipeline's runtime and computational cost
Comments
I still think just running FastQC on a subset of reads makes sense, but you might also consider using Falco to speed things up (#78) |
Por qué no los dos?
…On Mon, 21 Oct 2024 at 12:00, Michael McLaren ***@***.***> wrote:
I still think just running FastQC on a subset of reads makes sense, but
you might also consider using Falco to speed things up (#78
<#78>)
—
Reply to this email directly, view it on GitHub
<#74 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADWVV6SCDNHVD62W6RJSHZDZ4UQI7AVCNFSM6AAAAABQCCO262VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGA4TENJQGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ambiguous grammar, I was trying to suggest doing both of
|
harmonbhasin
added
the
in-progress
Mark this label when the assignee is actively working on this item.
label
Nov 13, 2024
We're now planning to implement this early next quarter by moving FASTQ downstream of the subsetting used at the start of the PROFILE workflow. (Strictly speaking this is downstream of implementing #129.) |
This was referenced Dec 17, 2024
willbradshaw
added
the
time&cost
Changes to improve the pipeline's runtime and computational cost
label
Dec 17, 2024
harmonbhasin
removed
the
in-progress
Mark this label when the assignee is actively working on this item.
label
Jan 6, 2025
harmonbhasin
added
the
done
Issues that have been addressed in dev branch, but not reflected in master branch
label
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
done
Issues that have been addressed in dev branch, but not reflected in master branch
enhancement
New feature or request
priority_1
time&cost
Changes to improve the pipeline's runtime and computational cost
Given that FASTQC takes a large chunk of time, Mike suggested running FASTQC on a subset of reads. Will agrees that this would be good to do, we would just need to calculate the total number of reads per sample separately (plus some other overall metrics) since that's currently being pulled from FASTQC.
The text was updated successfully, but these errors were encountered: