Regarding cuffcompare output files, some of them appear to be deposited in the path from which you call cuffcompare (even if specifying <outprefix> using the -o option). The affected files include:
cuffcmp.stats
cuffcmp.loci
cuffcmp.combined.gtf
cuffcmp.tracking
This could lead to some confusion if you happen to be in datapath1 when you call cuffcompare on datapath2. A simple work around is to add the appropriate cd command to your scripts just prior to calling cuffcompare.
Using Cufflinks 1.0.3
cuffcmp.stats
cuffcmp.loci
cuffcmp.combined.gtf
cuffcmp.tracking
This could lead to some confusion if you happen to be in datapath1 when you call cuffcompare on datapath2. A simple work around is to add the appropriate cd command to your scripts just prior to calling cuffcompare.
Using Cufflinks 1.0.3
Comment