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

Error in Aberrant Expression Analysis with only external counts #561

Open
bijuissac opened this issue Jul 23, 2024 · 2 comments
Open

Error in Aberrant Expression Analysis with only external counts #561

bijuissac opened this issue Jul 23, 2024 · 2 comments
Assignees

Comments

@bijuissac
Copy link

Hi Team

I am trying to run AE pipeline with only external counts but it gives error

Quitting from lines 62-67 [unnamed-chunk-5] (/hpcdata/scratch/25550129.1.all.q/RtmpUSQCPG/file3e615edaefc8/SampleAnnotation.spin.Rmd)
Error in file.exists():
! invalid 'file' argument
Backtrace:

  1. sa[, :=(aux1, file.exists(RNA_BAM_FILE))]
  2. data.table:::[.data.table(sa, , :=(aux1, file.exists(RNA_BAM_FILE)))
  3. base::eval(jsub, SDenv, parent.frame())
  4. base::eval(jsub, SDenv, parent.frame())
  5. base::file.exists(RNA_BAM_FILE)
    Execution halted

However, if I provide even a single BAM, it seems to proceed to next step.

Does the pipeline work if we only have external counts? Does the pipeline need a BAM?

@AtaJadidAhari
Copy link
Collaborator

Hi @bijuissac,

Thanks for using DROP!
I checked and there is indeed a problem on how we check the non-existent RNA_BAM_FILEs. Currently if all of the samples are external, your error will occur. Thanks for noticing this, we will fix it in the next DROP release!

As a workaround, as you mentioned you can add one dummy sample and fill the RNA_BAM_FILE entry in sample_annotation file, a dummy path like test.bam will work since the BAM file doesn't need to exist. Also give that sample a different DROP_GROUP name and run the pipeline again.

@AtaJadidAhari AtaJadidAhari self-assigned this Jul 26, 2024
@vyepez88
Copy link
Collaborator

Hi, to add to this, we initially designed DROP not to accept external counts only, as if you already have the count matrix of your cohort, you can simply run OUTRIDER on it in 4 lines:

  1. convert the count matrix to an ods object
  2. filter it
  3. run OUTRIDER
  4. extract the results

which is way easier than setting up DROP.

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

No branches or pull requests

3 participants