Is there an existing issue for this?
Have you loaded the SQANTI3.env conda environment?
Are you running SQANTI3 on its latest release?
Problem description
Hi,
I opened a new bug, because, if I am correct, it may be worth removing the --skip_orf flag. So It is a different issues from #607
When running sqanti3_qc.py without --skipORF, ORF prediction is still skipped by default (log shows: Skipping ORF prediction because user requested it. All isoforms will be non-coding!, even though I never requested this). This happens consistently across fresh output directories, ruling out caching. After digging into sqanti3_config.yaml, I found include_ORF: false is the actual default, and the CLI flag --include_ORF must be explicitly passed to trigger TD2/Psauron. This is confusing given --skipORF still exists and reads as the expected opt-out mechanism for a default-on behavior (consistent with older GeneMarkS-T-era docs/behavior), when in practice ORF prediction is now default-off and requires opting in via a separate, not very discoverable flag. I am missing somethihg?
Code sample
No response
Error
No response
Anything else?
No response
Is there an existing issue for this?
Have you loaded the SQANTI3.env conda environment?
Are you running SQANTI3 on its latest release?
Problem description
Hi,
I opened a new bug, because, if I am correct, it may be worth removing the --skip_orf flag. So It is a different issues from #607
When running sqanti3_qc.py without --skipORF, ORF prediction is still skipped by default (log shows: Skipping ORF prediction because user requested it. All isoforms will be non-coding!, even though I never requested this). This happens consistently across fresh output directories, ruling out caching. After digging into sqanti3_config.yaml, I found include_ORF: false is the actual default, and the CLI flag --include_ORF must be explicitly passed to trigger TD2/Psauron. This is confusing given --skipORF still exists and reads as the expected opt-out mechanism for a default-on behavior (consistent with older GeneMarkS-T-era docs/behavior), when in practice ORF prediction is now default-off and requires opting in via a separate, not very discoverable flag. I am missing somethihg?
Code sample
No response
Error
No response
Anything else?
No response