Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] fatal error in SQANTI3_report.R #278

Closed
1 of 2 tasks
diekhans opened this issue Mar 26, 2024 · 3 comments
Closed
1 of 2 tasks

[BUG] fatal error in SQANTI3_report.R #278

diekhans opened this issue Mar 26, 2024 · 3 comments
Labels
triage For developers to check

Comments

@diekhans
Copy link
Contributor

diekhans commented Mar 26, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Have you loaded the SQANTI3.env conda environment?

  • I have loaded the SQANTI3.env conda environment

Problem description

SQANTI3_report.R fails with. cryptic error:

Error in `[.data.frame`(t3.a.SJ, , c(1, 5, 6)) :
  undefined columns selected
Calls: rbind ... standardGeneric -> eval -> eval -> eval -> [ -> [.data.frame
Execution halted

Code sample

data files and script to reproduce the problem are here

https://hgwdev.gi.ucsc.edu/~markd/crg/crg-sqanti-err.tar.gz

data and script to do the full squant3 run is here

https://hgwdev.gi.ucsc.edu/~markd/crg/crg-sqanti-err-full.tar.gz

Error

Error in [.data.frame(t3.a.SJ, , c(1, 5, 6)) :
undefined columns selected
Calls: rbind ... standardGeneric -> eval -> eval -> eval -> [ -> [.data.frame
Execution halted

Anything else?

No response

@diekhans diekhans added the triage For developers to check label Mar 26, 2024
@alexpan00
Copy link
Collaborator

Hi,

I think I have suffered this error myself before, it was caused by not having any transcript with non-canonical junctions. This also happens in the classification file you have provided.

Thanks for reporting this bug,
Alejandro.

@TianYuan-Liu
Copy link
Member

Hi,

I think I have suffered this error myself before, it was caused by not having any transcript with non-canonical junctions. This also happens in the classification file you have provided.

Thanks for reporting this bug, Alejandro.

Hi Alejandro, thanks for reporting this bug and sharing your experience. I'll address this issue related to transcripts with non-canonical junctions in the R report to prevent future occurrences. Your input is invaluable in improving our processes.

TianYuan-Liu added a commit to diekhans/SQANTI3 that referenced this issue Mar 26, 2024
@carolinamonzo
Copy link
Contributor

This error has now been fixed in v5.2.1. Thank you Mark and Tian!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage For developers to check
Projects
None yet
Development

No branches or pull requests

4 participants