Re: [certi-dev] CERTI deadlock

[Eric Noulard]

2012/6/14 Michael Raab <address@hidden>:
> Hi Eric,
>
> I'm still facing this problem. :-(
> Could you please tell me, which component decides whether a requested time
> advancement can be granted?

The time advancing code is located in RTIA (TimeManagement.cc)
and libRTI (tick, TAR, NER, ...)

Once the federate did set their lookahead and requested to advance with
(TAR, TARA, NER, NERA) the main time advancing path is:

1) libRTI::tick_kernel --> Message::TICK_xxx
2) RTIA::processFederateRequest
3) RTIA::chooseFederateProcessing(
4) case Message::TICK_xxxx
      RTIA::processOngoingTick

You'll find some figure describing the usual LRC-CRC-LRC process.
The tick should not reach RTIG, the time advancing request
(TAR, TARA, NERA, NER) must generate some NULL message which are
broadcasted by RTIG to the concerned RTIA.

NULL Message Prime protocol adds extra message generated by the RTIG
itself when he knows it's possible.

-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org

federate_LRC_CRC.png
Description: PNG image