AW: [certi-dev] Question about NextEventRequest Service

[Roth, Christoph]

Hi Eric,

I tried

cmake -DMAKE_INSTALL_PREFIX=/home/roth/certi-3.4.0 
-DCERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL=ON ../CERTI-3.4.0cvs-Source

as well as

cmake -DMAKE_INSTALL_PREFIX=/home/roth/certi-3.4.0 
-DNULL_PRIME_MESSAGE_PROTOCOL=ON ../CERTI-3.4.0cvs-Source

but the behavior is the same. The tick2 function still has a delay of several 
seconds if the NMR parameter has a high value.

Both parameters are also not visible in the cmake gui? Are they correct?

Regards,
Christoph

-----Ursprüngliche Nachricht-----
Von: address@hidden [mailto:address@hidden Im Auftrag von Eric Noulard
Gesendet: Freitag, 29. Oktober 2010 23:24
An: CERTI development discussions
Betreff: Re: [certi-dev] Question about NextEventRequest Service

2010/10/29 Eric Noulard <address@hidden>:
> You can try it by defining the CMake option
> CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL
> to ON.
>
> (Use cmake-gui or command line -D argument)
>
> Normally this algorithm should do just what you expect:
> bump in the nearest future for both your federate doing NMR.

Christoph,

Some more remarks/question.

1) If you try NULL_PRIME_MESSAGE_PROTOCOL
    please give us feedback in order to know if it works
    for you or not.

2) Did you try your test case with other RTI?
    If yes how do they behave?

3) May be you can send us a simple piece of code
   (ideally a single federate C++ source file)
    which exhibit this issue? This way we can use it
    as a unit test in HLA TestsSuite.

Thank you for using CERTI.
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel