[cc-ing list]
> python /usr/bin/run_grit.py --threads 8 --rnaseq-read-type backward
> --rnaseq-reads wgEncodeCshlLongRnaSeqMcf7CellPapFastqRd1Rep1.STAR_2.3.0e.bam
> --ofprefix
> GRIT-1.1.0-wgEncodeCshlLongRnaSeqMcf7CellPapFastqRd1Rep1.STAR_2.3.0e &
>
It looks like I introduced another bug when I changed the argument
parsing. I'll upload a fix tonight.
Also, you'll need to either provide poly(A) and CAGE or RAMPAGE reads,
or reference poly(A)'s and promoters.
> What exactly is the CONTROL file supposed to contain and do? I could not
> find any example so I did not specify any
For now, you can use a control file of the form:
# comment line
# *'s indicate merged
#sample_type rep_id assay paired
stranded read_type filename
AdMatedF_Ecl_20days_Heads rep1 rnaseq true true
auto AdMatedF_Ecl_20days_Heads.biorep1.rnaseq.chr4.bam
AdMatedF_Ecl_20days_Heads rep1 cage false true
auto AdMatedF_Ecl_20days_Heads.biorep1.cage.chr4.bam
AdMatedF_Ecl_20days_Heads rep1 polya false true
auto AdMatedF_Ecl_20days_Heads.biorep2.passeq.chr4.bam
I've put an example data set with a control file and README at:
http://grit-bio.org/GRIT_example.tar.gz
Note that to use read type 'auto' you'll need to provide a reference
annotation (even GENCODE chr20 will work - GRIT just needs genes so
that it can determine the gene strand).
> P.S. Am I correct in my guess the read-type should be "backward" for dUTP?
Yes.
Thanks for your interest - sorry about the bug.
Best, Nathan