Activity for Bastien Chevreux
-
Bastien Chevreux modified a wiki page
Home
-
MIRA failed with error code 100
-
No response, closed.
-
Unfortunately, the reason for the crash cannot be deduced from your report. Please look through the directory C:\Users\helen\Geneious 2021.2 Data\transient\1634201381381\x\8 to see whether you can find a log file which, hopefully, Geneious saved to the given directory.
-
\o/ :-) On 18. May 2021, at 9:39 , Maeva perez maeperez@users.sourceforge.net wrote: Oh nevermind. The issue was in the manifest.conf file. I replace the line segment_naming = FR by segment_naming = solexa and it worked. Thanks for a great program. [tickets:#44] https://sourceforge.net/p/mira-assembler/tickets/44/ MIRA 4 cannot recognise paired reads Status: open Version: 4.0.1 Created: Tue May 18, 2021 07:16 AM UTC by Maeva perez Last Updated: Tue May 18, 2021 07:18 AM UTC Owner: nobody Attachments:...
-
A bug of the C++ libraries which I learned to circumvent in later versions of MIRA. Should you insist on using 4.0.2, the workaround is: export LC_ALL=C in the shell, then it will work. Though I would suggest you use mirabait from either 4.9.6 or from 5rc1 (on GitHub). I think I slightly changed the commandline interface for mirabait inbetween 4.0.x and 4.9.x, so MITObim might need slight adaptation. But the core functionality of mirabait remained the same.
-
Shouldn't be, that'd be a first. Can you please check wether you are calling the right binary? Either via "which mirabait", then check path, or call the downloaded binary directly with full path.
-
Problems with Mira-V5rc1
-
I suspect the runtime error on the distant machine somehow really being by some sort of incopatibility between the compiled binary and available system libraries. But I have no idea what causes it. Regarding compilation error: that was a bug fixed in git, but I did not make a release before. There's now rc2 as release on GitHub Best, Bastien
-
The log says MIRA was killed. I suspect the OS did that, the reason might be MIRA was using too much memory. Check the limits which are available on your system. And also whether the project you have might not be too large for MIRA.
-
MIRA 4.0 crashed in Geneious 10.0.5
-
I'm sorry, without log-file or data to test, I cannot look at this bug as I don'z...
-
MIRA 4.0 crashed in geneious 10.0.5
-
I'm sorry, without log-file or data to test, I cannot look at this bug as I don'z...
-
I'm sorry, without log-file or data to test, I cannot look at this bug as I don'z...
-
MIRA 4.0 crashed
-
MIRA "operation failed" in Geneious 7.1.9
-
If I guess right, this looks to be a memory problem: although you seem to have 32...
-
Any feedback?
-
Internal error: " from + len > size of contig? "
-
Fixed in current dev version.
-
Internal logic/programming/debugging error
-
No feedback, closing report.
-
Error on loading fastq files either compressed or uncompressed
-
assembly failure
-
Sorry, misclassified the error. However, I suspect the bug is fixed in the current...
-
assembly failure
-
MIRA probably got killed by the OS, I suspect because of memory problems.
-
4.0.2 internal error
-
This is a know bug which has been bixed in the current development version. Please...
-
I have seen this before, I think even on one of my machines. I think I got it fixed...
-
error: "cout" is not a member of "std"
-
Fixed in dev version. Thank you for the report.
-
Error: More than 2^31 skim hits would be taken
-
Terribly sorry, the data you are using is simply too big for MIRA4. Won't fix.
-
Probably process got killed by system for using too much memory. Not a loading p...
-
Compiling process always failed
-
Fatal error (may be due to problems of the input data or parameters)
-
For this kind of questions, please use the MIRA talk mailing list where other people...
-
I do not think the the problem is you being a Linux newcomer :-) You truncated the...
-
2.0.0b10: Programs not starting on OSX Yosemite
-
MIRA crashed in Geneious
-
This is probably a memory problem: a project too big and not enough RAM. Also, MIRA...
-
Problem with gap handing in output files
-
The consensus generation does not rely primarily on base counts, but uses base and...
-
While differences in run time are to be expected, having runs between 16 and 44 hrs...
-
Closed as no further feedback provided.
-
Ouch: found 0 coverage
-
compiler detection breaks when using clang
-
MIRA 4.0.x supports only gcc atm, please use that for the time being. clang support...
-
Any news on this ticket? If not, I'll close it.
-
Am I guessing right that this was a RNASeq/EST assembly? If yes, did you filter out...
-
Closed, no further feedback was given.
-
Aborting process, probably due to an internal error.
-
Space character in path name of executable causes failure
-
Fixed in 4.0.1
-
Hmmm ... the errors which are dumped out at the end make not much sense to me as...
-
Home
-
Home
-
The problem you are seeing indeed comes from something I had not foreseen: using...
-
If you could upload to Dropbox one of the small test sets which failed and then send...
-
Any news on whether the error is still present in 4.0rc5? I'm wrapping up things...
-
Startup time too long: ~3m when missing internet connections
-
Hmmm, strange. Good, two things: 1. thank you for creating a smaller data set in...
-
Am I correctly reading some slight irony in your comment? :-) What you stumbled upon...
-
Mira stops with error when parsing valid parameters
-
status: open --> closed
-
It was always active. Anyway, 4.0rc5 now has the correct documentation for -ED:mace...
-
Description has changed: Diff: --- old +++ new @@ -1,4 +1,3 @@ - I am trying to run...
-
Failure, wrapped MIRA process aborted. While writing normalized skim block
-
Error after use CL:qc=yes and CL:qcmq=23
-
status: open --> fixed
-
Fixed in 4.0rc5
1
