certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions about CERTI usage and implementation


From: Pierre Siron
Subject: Re: Questions about CERTI usage and implementation
Date: Tue, 16 Oct 2007 14:18:35 +0200
User-agent: Mozilla/5.0 (X11; U; SunOS sun4u; fr-FR; rv:1.7) Gecko/20051027

Christian Stenzel a écrit :

Hello,


3)
Is it still necessary to "spin" until the join of a federate is successful
(like in Billard class)?

I know, that this was no more required for RTI1.3-NG, .  It was
necessary when using RTI-1.3v6 or lesser because the creation of a federation
needs some time. RTI 1.3-NG was ready to accept joining federates
upon return from the createFederationExecution() invocation.


Hello

4) I am thinking to another problem ("spin" in the setTimeRegulating function).

This federate does not have to spin, because the federation starts
by a synchronization point (all the federates are blocked at the time 0).
And this federate does not work if it is started after this point
because it waits after it ...

How to write a federate that must join already looping federates ?
In coordinated time, it has to catch the time before becoming
a regulator.
The invocation of the "enableTimeRegulation" service should now
be considered as an implicit "timeAdvanceRequestAvailable". I am
not sure that we are doing that.
(This can be important even for the Billard federate, in which
loop the RO or TSO messages are received at the initial time ?)
There is an argument to "timeRegulationEnabled" service that indicates
the logical time of the federate.
We have to verify the implementations of these services.

Bien cordialement,
Pierre






reply via email to

[Prev in Thread] Current Thread [Next in Thread]