Replies: 1 comment
-
|
Hi, does SQANTI reads just stay frozen at a step or do you get the ERROR of everything filtered out as you mentioned? If it gets frozen, perhaps it is due to the size of your dataset. How many reads do you have in total? Also, keep in mind that SQANTI3 reads was originally designed to work at read level, rather than at transcript level, to act a quality control for experiments. I have personally never tried it with the results of rescue. However, it should work though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to run SQANTI-reads on three samples to test out, but the process does not finish and no report is generated. Ran each through IsoQuant w/ GENCODE reference, SQANTI3 QC, filter, and rescue. Files used for SQANTI-reads input are those generated furthest down the SQANTI3 pipeline (after rescue). I verified that there is an "FL" column in the classification.txt file that has counts. Any suggestions on what to try?
The error message I am getting: ERROR: The filtering was too scrict and no genes were found that meet the criteria.
Input directory is structured like this. All files were generated by running SQANTI3. I renamed some of the files to fit with SQANTI-reads nomenclature requirements:
├── NT_rep1
│ ├── NT_rep1_classification.txt
│ ├── NT_rep1_corrected.gtf
│ └── NT_rep1_junctions.txt
├── NT_rep2
│ ├── NT_rep2_classification.txt
│ ├── NT_rep2_corrected.gtf
│ └── NT_rep2_junctions.txt
└── NT_rep3
├── NT_rep3_classification.txt
├── NT_rep3_corrected.gtf
└── NT_rep3_junctions.txt
Design file looks like this:
Tried relaxing the filter arguments to be less stringent:
Beta Was this translation helpful? Give feedback.
All reactions