-
Notifications
You must be signed in to change notification settings - Fork 24
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
basic_ios::clear: iostream error #42
Comments
Hi, What version of AdapterRemoval are you using and what command-line arguments did you use when running it? |
Hi, This was a conda install: AdapterRemoval v.2.3.0 Command: |
I am not sure why the error message is so uninformative, and I am currently exploring how to fix that, but the cause is most likely that AdapterRemoval cannot create the output file, possibly because the directory "analysis_ready" does not exist or because you do not have sufficient permissions to write to it. Can you check if "analysis_ready" exists and that you have permission to write to it? I.e. what is the output of running the following command in the same folder where you are running AdapterRemoval:
|
Actually, this is silly, but apparently this is a simple typo error. I have "analysis_ready" in one spot and "analyis_ready" in another. It is now working. Sorry about that. I should have caught that. |
Also, thank you for your time. |
You're welcome. I'll release a small update to AdapterRemoval sometime this week to improve the error message; it's easy to make a typo like that, so the error message should at least point in the right direction and not be this uninformative. |
I have tried to run AdapterRemoval on two operating systems, and have received the following error on both:
Trimming paired end reads ...
Opening FASTQ file 'PCS_S21_L001_R1_001.fastq', line numbers start at 1
Opening FASTQ file 'PCS_S21_L001_R2_001.fastq', line numbers start at 1
ERROR: Unhandled exception in thread:
basic_ios::clear: iostream error
ERROR: AdapterRemoval did not run to completion;
do NOT make use of resulting trimmed reads!
The first os was macOS Catalina v10.15.1, while the second was on a server and was CentOS Linux v7. I'm not sure how to handle the error?
The text was updated successfully, but these errors were encountered: