Closed marwa38 closed 10 months ago
You can always try running the individual workflow functions instead of the high-level one (see the vignette for how to). You could also try the DEXSeq-based test - but in general, I would not recommend changing the FDR cutoff.
And just a reminder: It could also be true that your data has no switches.
@kvittingseerup
The depth of my (PE150; paired-end each have 150 reads) sequencing is 20M sequences per read (40M per sample), do you consider that is good enough for alternative splicing and/or soform switches analysis? I ran the analyses on 4 different comparisons (same above codes) and couldn't find any isoform switches, although Atlantic salmon (my model species) is quite known for gene duplication.
Having post-translational pathways enriched doesn't that imply that isoform switches is possibly present?
I used kallisto in the upstream analysis and transcriptome (cDNA) for annotation. In contrast to human and mouse, not all species have haplotype information available. The message notes that there is no alternative assembly, including haplotypes, for Atlantic Salmon (salmo_salar) in the Ensembl database.
Last but not least, could you please let me know what are the default FDR (alpha), and dIFcutoff? As I am writing currently and need to report that I ran the analysis (with details) and results showed no isoform switches. Anyway is it possible to run analysis only on Ss4R duplicates only in Atlantic salmon? as in this study https://onlinelibrary.wiley.com/doi/10.1111/mec.14533 Many thanks for your comment in advance.
Many thanks for the great package I am using the same database, version, etc but I am getting the following error, Please let me know why I might be getting the following error? How I could change the pvalue cut-off to make it less stringent?