Open olgabot opened 7 years ago
I guess the validated exons should also be explicit:
$ ls outrigger_output
all_events.psi.csv
all_events.summary.csv
gencode.vM10.annotation.gtf
gencode.vM10.annotation.gtf.db
gencode.vM10.annotation.novel_exons.gtf
mxe.event.bed
mxe.event.validated.bed
mxe.events.csv
mxe.events.validated.csv
mxe.exon1.bed
mxe.exon1.validated.bed
mxe.exon2.bed
mxe.exon2.validated.bed
mxe.exon3.bed
mxe.exon3.validated.bed
mxe.exon4.bed
mxe.exon4.validated.bed
mxe.intron.bed
mxe.intron.validated.bed
mxe.psi.csv
mxe.summary.csv
mxe.splice_sites.csv
se.event.bed
se.event.validated.bed
se.events.csv
se.events.validated.csv
se.exon1.bed
se.exon1.validated.bed
se.exon2.bed
se.exon2.validated.bed
se.exon3.bed
se.exon3.validated.bed
se.intron.bed
se.psi.csv
se.summary.csv
se.splice_sites.csv
junctions.csv.......................................[replacing `junctions/metadata.csv`]
junction_reads.csv
Description
Right now, the outrigger output is a big nested mess:
Proposal
Here's a proposed, flat structure of the
outrigger_output
folder:@alaindomissy what do you think?
Versions
This would greatly change the usability and would be a
2.0.0
release.EDIT: No exon4 for SE events .. copy/paste mistake