GenEditID

A flexible, open-access workflow to facilitate the identification of cell clones that have desirable CRISPR-Cas9-induced gene edits.

View My GitHub Profile

Detailed steps for testing with real data subset

:memo: Demo steps

Running the analysis below will take about an hour on a laptop.

:one: Start GenEditID WebApp, and setup a demo project for analysing

Create a project, upload the submission spreadsheet associated with this project from data/submission_spreadsheets/demo.xlsx into the WebApp.

The active environment, the one you are currently using, is shown in parentheses () or brackets [] at the beginning of your command prompt.

(geneditid) $

if not, activate it using conda activate geneditid before running the next steps.

:two: Download and prepare fastq files

While waiting for the submission spreadsheet to load, open a new terminal and download the public fastq files. Don’t forget to activate conda’s environment using conda activate geneditid before merging the reads.

cd ~/GenEditID/
./scripts/get_data_demo.sh

All the fastq files related to this project will be stored in the PROJECTS/demo folder. Combine paired-end reads by merging reads to generate .fqjoin.gz files for amplicount analysis (seqkit needs to be installed).

cd PROJECTS/demo
../../scripts/run_mergereads.sh

Move the joined fastq files into the PROJECTS/GEPID/fastq/ replacing GEPID with the identifier of this project.

mv *.fqjoin.gz ../GEP00001/fastq/.

:three: Run amplicount analysis

cd ~/GenEditID
source venv/bin/activate
cd PROJECTS/GEP00001
geneditid_run_amplicount

Replace GEPID with the identifier of this project.

:four: Visualise results

:memo: Three real data projects to analyse if you wish

:house: Back to the main manual

GenEditID Manual: detailed steps