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

add explicit commands to copy fastq files from .backup into dc_workshop/data #140

Closed
taylorreiter opened this issue Feb 5, 2019 · 3 comments
Assignees
Labels
high priority Need to be addressed ASAP status:in progress Contributor working on issue

Comments

@taylorreiter
Copy link
Contributor

We need to add explicit instructions to the episode 02 Assessing Read Quality to copy the fastq files from .backup/untrimmed_fastq/*fastq.gz.

The download worked quickly for some learners, but was very slow for others. An alternative would be to use a different instance type, as t2.medium has slow/moderate network speeds that are less reliable than other instances. However, this may cost most. A t2.medium costs $0.0464 per Hour and Low to Moderate network performance. A t3.medium costs $0.0416 per Hour and has up to 5 Gbps. An m5a.large costs $0.086 per Hour and has up to 10 Gbps.

@taylorreiter
Copy link
Contributor Author

@ErinBecker

potential improvement for the AWS image, upgrade from t2.medium to t3.medium

@ErinBecker
Copy link
Contributor

@taylorreiter - I'm looking into changing our AMI setup to be able to use the t3 instance type instead of t2, but think we should also include the command for copying data from .backup/, as even with the faster instance type, some learners will still experience problems with the large data download. I'm working on a PR to add this command now.

@ErinBecker ErinBecker added the status:in progress Contributor working on issue label Apr 10, 2019
@taylorreiter
Copy link
Contributor Author

@ErinBecker I totally agree! Thank you for working on upgrading to t3 and for working toward adding a copying command!

ErinBecker added a commit that referenced this issue Apr 10, 2019
zkamvar pushed a commit that referenced this issue May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority Need to be addressed ASAP status:in progress Contributor working on issue
Projects
None yet
Development

No branches or pull requests

2 participants