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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
Instructions for setting up a Conda development environment
Creating a Conda development environment
We recommend that you set up a Python environment for developing quantecon that is separate from the "default" Python environment that you use in your own research. This will allow you to contribute to quantecon without worrying about corrupting the Python environment on which your other work depends.
Below are instructions for building a separate development environment for contributing to the quantecon package using the Conda package management system which comes bundled with the Anaconda Python distribution provided by Continuum Analytics.
Step 1:
Fork and clone a copy of the quant-econ repository on to your local machine.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extracting paired FASTQ read data from a BAM mapping file
Sometimes FASTQ data is aligned to a reference and stored as a BAM file, instead of the normal FASTQ read files. This is okay, because it is possible to recreate raw FASTQ files based on the BAM file. The following outlines this process. The useful software samtools and bedtools are both required.
From each bam, we need to extract:
reads that mapped properly as pairs
reads that didn’t map properly as pairs (both didn’t map, or one didn’t map)