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

Eel pond mRNAseq tutorial #2

Open
wants to merge 18 commits into
base: old
Choose a base branch
from
Open

Eel pond mRNAseq tutorial #2

wants to merge 18 commits into from

Conversation

ctb
Copy link
Member

@ctb ctb commented Aug 1, 2013

No description provided.

like so::

cd /mnt/work
python /usr/local/share/khmer/sandbox/write-trimmomatic.py > trim.sh
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A script that... writes another script? This can be useful, but it's not common practice.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See https://github.com/ged-lab/khmer/blob/bleeding-edge/sandbox/write-trimmomatic.py for the script source.

Yeah, I struggled with this for a while. It seemed easier to write it in Python... but that was before I invested in all the other shell stuff below. Sigh.


And, finally, you can toss the pe.fq.gz files, because you've turned *those*
into .pe and .se files.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add :: so "rm *.pe.qc.fq.gz" shows up as code

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is done in the latest version, right?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In doc/mrnaseq/1-quality.txt:

+Yikes! What to do?
+
+Well, first, you can get rid of the original data. You already have it on a
+disk somewhere, right? ::
+

  • rm *.fastq.gz

+Next, you can get rid of the 'pe.fq.gz' and 'se.fq.gz' files, since you
+only want the QC files. So::
+

  • rm _.pe.fq.gz *.se.fq.gz

+And, finally, you can toss the pe.fq.gz files, because you've turned *those_
+into .pe and .se files.
+
This is done in the latest version, right?

Nope still just a white space with an indentŠ


Reply to this email directly or view it on GitHub
https://github.com/ngs-docs/edda/pull/2/files#r5820320 .

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed! (in the khmer-protocols version)

On Fri, Aug 16, 2013 at 03:12:06PM -0700, LSheneman wrote:

+Yikes! What to do?
+
+Well, first, you can get rid of the original data. You already have it on a
+disk somewhere, right? ::
+

  • rm *.fastq.gz

+Next, you can get rid of the 'pe.fq.gz' and 'se.fq.gz' files, since you
+only want the QC files. So::
+

  • rm _.pe.fq.gz *.se.fq.gz

+And, finally, you can toss the pe.fq.gz files, because you've turned *those_
+into .pe and .se files.
+

In doc/mrnaseq/1-quality.txt:

+Yikes! What to do?
+
+Well, first, you can get rid of the original data. You already have it on a
+disk somewhere, right? ::
+

  • rm *.fastq.gz

+Next, you can get rid of the 'pe.fq.gz' and 'se.fq.gz' files, since you
+only want the QC files. So::
+

  • rm _.pe.fq.gz *.se.fq.gz

+And, finally, you can toss the pe.fq.gz files, because you've turned *those_
+into .pe and .se files.
+
This is done in the latest version, right?

Nope still just a white space with an indent??

???
Reply to this email directly or view it on GitHub
https://github.com/ngs-docs/edda/pull/2/files#r5820320 .


Reply to this email directly or view it on GitHub:
https://github.com/ngs-docs/edda/pull/2/files#r5826092

C. Titus Brown, [email protected]

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

Successfully merging this pull request may close these issues.

6 participants