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 at stage filter_transcripts #58

Closed
mei-du opened this issue May 14, 2021 · 10 comments
Closed

error at stage filter_transcripts #58

mei-du opened this issue May 14, 2021 · 10 comments

Comments

@mei-du
Copy link

mei-du commented May 14, 2021

Hi team,

I've run into a std::regex_error when running JAFFAL with default parameters and the provided hg38 reference. The same error occurred with both ONT and PacBio data. Any clarification would be much appreciated, thank you!

JAFFAL error

@nadiadavidson
Copy link
Member

Hi,
This looks like the same error as issue #57. I believe this is resolved if you switch to gcc version 4.9 or higher and reinstall JAFFA (remove the tools directory and rerun the installation script). Please let us know if that works for you.

Cheers,
Nadia.

@mei-du
Copy link
Author

mei-du commented May 14, 2021

Hi @nadiadavidson, that worked but I encountered another error during genome mapping.

image

@nadiadavidson
Copy link
Member

Hi,
Did you remove the old run with the std::regex_error? I wonder if rerunning from that point would create some empty files that might give you this error. Can you please send me the result of "ls -l" in the sample directory where the results are being written. ie:
ls -l S6R_polyA*.fastq/
Cheers,
Nadia.

@mei-du
Copy link
Author

mei-du commented May 14, 2021

Hi Nadia
You were right about the empty files, thanks!. I removed them and re-installed the tools just in case. The pipeline was working well until the genome mapping stage. This has happened twice.

Screen Shot 2021-05-14 at 16 50 46

Screen Shot 2021-05-14 at 20 29 33

@nadiadavidson
Copy link
Member

Hi,
It sounds like you removed all the results file which were empty within "S1R_...ccs.fastq", and then reran is that right? It's odd that the .txt file is still empty after rerunning. Can you send me the results of ls -l inside the directory were you placed the reference files? Even with non-tumour samples, the .txt file usually has a few candidates reported, so it's very usually that that stage would complete okay and the output be empty. Is there anything usual about your sample?

Have you been able to run JAFFAL or any of JAFFA's other modes on other dataset (e.g the short read demo data or long read simulation from https://github.com/Oshlack/JAFFA/wiki/Example)?

If you can send me your .paf file, or any reproducible example, I'm happy to investigate what's going on.

Cheers,
Nadia.

@mei-du
Copy link
Author

mei-du commented May 18, 2021

Hi Nadia,
Sorry the ls -l image I sent was before removing and rerunning.

References:
image

I was able to successfully run JAFFA assembly, direct and hybrid on the demo data.

I'm getting the same error with JAFFAL and the long read simulation data, just during the minimap2_genome stage:
image

@mei-du
Copy link
Author

mei-du commented May 19, 2021

Hi Nadia, sending a link to my JAFFAL outputs run with the simulation data.
https://drive.google.com/drive/folders/19_1ZLdTX4Z9DeqN4uU0iJ_bB-ZnhO6ML?usp=sharing

@nadiadavidson
Copy link
Member

Thanks! Everything prior to the minimap2 aligning to the genome looks perfect. I'm now wondering if minimap2 might have run out of memory. How much memory do you give the job? JAFFAL needs about 20GB per sample, so you could set to 25GB to be safe.

@mei-du
Copy link
Author

mei-du commented May 19, 2021

Ah yes, I think that did the trick! An easy fix for an ominous error message. I tried 2 samples with 50GB. Thank you so much for your help!

image

@nadiadavidson
Copy link
Member

Glad to hear it! and happy to help if you run into any other errors.

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

2 participants