You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EPISODE starts by working on a local computer but in the section "Viewing the FastQC results", it suddenly mentions AWS and data transfer. The context could be better explained as follows:
If we were working on our local computers, we would be able to look at each of these HTML files by opening them in a web browser.
However, very often we use Cloud Computing like [AWS](https://en.wikipedia.org/wiki/Amazon_Web_Services) and even [High Performance Computing](https://en.wikipedia.org/wiki/High-performance_computing). Assuming these HTML files are currently sitting on our remote AWS instance, where our local computer can not see them. And, since we are only logging into the AWS instance via the command line - it does not have any web browser setup to display these files either.
So the easiest way to look at these webpage summary reports will be to transfer them to our local computers (i.e. your laptop).
To transfer a file from a remote server to our own machines, we will use scp, which we learned yesterday in the Shell Genomics lesson.
Which part of the content does your suggestion apply to?
How could the content be improved?
The EPISODE starts by working on a local computer but in the section "Viewing the FastQC results", it suddenly mentions AWS and data transfer. The context could be better explained as follows:
If we were working on our local computers, we would be able to look at each of these HTML files by opening them in a web browser.
However, very often we use Cloud Computing like [AWS](https://en.wikipedia.org/wiki/Amazon_Web_Services) and even [High Performance Computing](https://en.wikipedia.org/wiki/High-performance_computing). Assuming these HTML files
are currently sitting on our remote AWS instance, where our local computer can not see them. And, since we are only logging into the AWS instance via the command line - it does not have any web browser setup to display these files either.So the easiest way to look at these webpage summary reports will be to transfer them to our local computers (i.e. your laptop).
To transfer a file from a remote server to our own machines, we will use scp, which we learned yesterday in the Shell Genomics lesson.
Which part of the content does your suggestion apply to?
https://datacarpentry.org/wrangling-genomics/02-quality-control.html#viewing-the-fastqc-results
The text was updated successfully, but these errors were encountered: