Re: [certi-dev] TAG and transient message

[David Come]

Hello,

I indeed used the NULL_MESSAGE_PRIM because I have been told by the original writter that it was needed otherwise the simulation was too slow.
I never asked question about it (maybe I should have).

I have just tested without it and it is working just fine with the intended behavior.

I'm using the lastest version of certi (6e7be21f6d6a7997a263be784a61a9603118f4d9), same with Jcerti (d2f82ad25ebbbe301f7414f78fe93d71af1dbeb8).

Here are the full logs I have for another run which exhibits the same behavior when running a CERTI compiled with NULL_MESSAGE_PRIM.
I got the output file logtty with export RTIG=ACDEGIMPRSTWXZ, not sure if it is the right way, couldn't find anything about it in the doc.

Thanks,
David.

Le 25/06/2015 02:46, Jean-Loup Bussenot a écrit :

Hi David !

Could you give us the commit number of your certi version ?
Do you compile using the NULL_MESSAGE_PRIM ?

According to Eric, you couldn't send a NER(0) after a NER(100)  without receiving a TAG(0)

INFO: Sending message (NEXT_EVENT_REQUEST, NO_EXCEPTION, federation time: 100.0)
INFO: Received message (NEXT_EVENT_REQUEST, NO_EXCEPTION, federation time: null)

INFO: Sending message (NEXT_EVENT_REQUEST, NO_EXCEPTION, federation time: 0.0)
INFO: Received message (NEXT_EVENT_REQUEST, NO_EXCEPTION, federation time: null)

Can you send us the RTIG log with the NULL_MESSAGE print ,

Jean-Loup

fulllogs.zip
Description: Zip archive