[mira_talk] Re: Bug report mira verison 3.9.9
- From: John Nash <john.he.nash@xxxxxxxxx>
- To: mira_talk@xxxxxxxxxxxxx
- Date: Thu, 10 Jan 2013 18:22:59 -0500
On 2013-01-10, at 5:29 PM, Bastien Chevreux wrote:
> On Jan 10, 2013, at 23:02 , "Langhorst, Brad" <Langhorst@xxxxxxx> wrote:
>> here's my header…
>> this assembly is still running though.
>>
>>> This is MIRA 3.9.9 ().
>
> Good. Or rather not. Looks like I'm mixing up things: I promoted that warning
> to a full blown bug, but only during christmas (i.e., after 3.9.9) and it's
> in my current development head. I think I even worked on a similar bug report
> during that time and I found the reason for the problem, but I'm too tired to
> fire up and check in the version control right now.
>
> John, Brad: I'll have a look at whether the head is currently stable enough
> to eventually compile some special version for both of you to help me either
> confirm my suspicion or hunt down that bug if it still exists.
>
> In the mean time: don't panic :-) Your assembly is (probably) as good as it
> would be without that minor bug.
Thanks Bastien,
I do have a safety mechanism and it may prove helpful. Currently, my students
are assembling genomes from a number of food pathogen ioslates which appear to
be clonal. We have an Opgen optical map, and we are also running concurrent
reference assemblies, so if anything weird happens, we will know.
John
--
You have received this mail because you are subscribed to the mira_talk mailing
list. For information on how to subscribe or unsubscribe, please visit
http://www.chevreux.org/mira_mailinglists.html
Other related posts:
