-
Notifications
You must be signed in to change notification settings - Fork 23
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
"OperationalError: attempt to write a readonly database" and others #301
Comments
Hi again, In the meantime other TriSeq commands that I was running on smaller alignments (50 kb alignments from across the genome) also started to fail with a different (but possibly related?) error. I'm going to post this error here as well in case it is somehow related:
Again, thank you! |
Dear Mafalda, Let's try to cover some basics possible errors first. Best |
Thank you for responding. I cannot find a
Would this be the correct directory? If so, there should be enough space (180T) to right here, since this is within my home folder. As for the Thanks, |
Hi Mafalda, I'll try to address all the issues you raised. The first one, with the error Regarding the |
Hello Diogo,
I am using TriSeq to filter positions with missing data from different types of alignments (whole chromosome to smaller alignments). I am getting an error particularly when I try to run TriSeq on whole chromosomes. TriSeq starts, but it ends up failing.
At first I was using gnu parallel to run TriSeq with 10 chromosomes at the same time but I got errors. When I thought parallel could be the issue, I decided to copy and paste a TriSeq command for each chromosome to four different bash scripts so, each script would run TriSeq for 5 different chromosomes at the same time. The same error happens. This is the command I am using:
TriSeq -in chr_2_full_algn.fa -of fasta -o chr_2_noMiss_TriSeq --upper-case --missing-filter 0 0
And I get the following error:
I tried googling this error but found little help. I then thought this could be from running TriSeq with parallel or in parallel for several chromosomes at the same time (maybe memory issues?). I tried to call one chromosome at the time. This is what I'm getting:
Which is... odd. In the server partition I'm currently working on, we have 604T of space available. My home folder (the one in the error messages - /home/mf239/) has 180T of space available. Could this be related to some other place in the server where TriSeq is trying to write to? For example, a tmp folder? We do have limited space on the default tmp folder, and usually I need to specify a tmp folder on my working space. However, reading the TriSeq options it doesn't seem I can specify this in the command.
Anyway, do you have any idea what could be happening or what I could test to try and solve this?
Thank you very much,
Mafalda
The text was updated successfully, but these errors were encountered: