[mira_talk] Re: It is an error? A bug? Or, I am doing something wrong

  • From: Marcelo Brandão <brandao.marcelo@xxxxxxxxx>
  • To: mira_talk@xxxxxxxxxxxxx
  • Date: Thu, 11 Sep 2014 14:16:32 -0300

Well,
I've just resume the run, and after a while this comes up:
Dynamic s allocs: 0
Dynamic m allocs: 0
Align allocs: 0

Internal logic/programming/debugging error (*sigh* this should not have
happened)

********************************************************************************
* Sf1P14657-5-1: Found diginorm multiplier of 0?
    *
********************************************************************************
->Thrown: int32 Read::getDigiNormMultiplier() const
->Caught: main

Aborting process, probably due to an internal error.

If you want to report the error, please do so on
        http://sourceforge.net/p/mira-assembler/tickets/
and also give a short notice on the mira talk mailing list.

If reporting, please do not delete the log and checkpoint directories,
there may
be files in them which could be needed to find the problem.
Subscribing / unsubscribing to mira talk, see:
//www.freelists.org/list/mira_talk

CWD: /thunderstorm/SPD_RNA-seq/MIRA
Thank you for noticing that this is *NOT* a crash, but a
controlled program stop.
Failure, wrapped MIRA process aborted.


2014-09-11 8:39 GMT-03:00 Marcelo Brandão <brandao.marcelo@xxxxxxxxx>:

> Ok,
> Here it comes.
> 1) I will send you the manifest file
> 2) I just resume the mira run
> 3) Yes it is ECC, the machine I've used has 64GB
>
> Cheers
>
> Marcelo
>
> 2014-09-11 3:55 GMT-03:00 Bastien Chevreux <bach@xxxxxxxxxxxx>:
>
> On 11 Sep 2014, at 0:32 , Marcelo Brandão <brandao.marcelo@xxxxxxxxx>
>> wrote:
>> > It is MIRA version 4.0.1 running on a Rocks Cluster.
>>
>> Hmmm, bad news for me as nothing was fixed between 4.0.1 and 4.0.2 which
>> would explain this error.
>>
>> OK, three things:
>> 1) can you please send me (off-list) the manifest file so that I can
>> start a bug hunt
>> 2) can you please resume the assembly? (mira -r …) There’s a slight
>> chance that the bug is not triggered if MIRA takes a different path.
>> 3) Can you ask whether your cluster has ECC RAM? As far as I remember
>> I’ve never been reported this bug, and you wouldn’t be the first to run
>> into trouble with MIRA because of a memory error.
>>
>> B.
>>
>>
>> --
>> 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
>>
>
>
>
> --
> Marcelo Mendes Brandão
> Laboratório de Biologia Integrativa e Sistêmica - CBMEG / UNICAMP
> Website: http://www.bioinfoguy.net/BBCA/
> AtPIN: http://bioinfo.esalq.usp.br/atpin
> SKYPE: mmbrand
>



-- 
Marcelo Mendes Brandão
Laboratório de Biologia Integrativa e Sistêmica - CBMEG / UNICAMP
Website: http://www.bioinfoguy.net/BBCA/
AtPIN: http://bioinfo.esalq.usp.br/atpin
SKYPE: mmbrand

Other related posts: