I'm still facing this problem. :-(
Could you please tell me, which component
decides whether a requested time advancement can be granted?
Thanks,
Michael
Dipl.-Inform. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Von:
Eric Noulard <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
06.06.2012 15:06
Betreff:
Re: [certi-dev]
CERTI deadlock
Gesendet von:
address@hidden
2012/6/6 Michael Raab <address@hidden>:
> OK,
>
> the execution using the recent CERTI version and
> CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL works and is much faster.
When using NER (Next Event Request) CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL
may give you huge boost in performance because it lowers the number
of NULL message to a quasi minimal value...
> The deadlock appears much later but it still appears :-(
>
> I set RTIA_CONSOLE_SHOW to true but still no console pops up.
Did you recompile from scratch and relink your app?
> I would like to try the default billard example.
> What do I need to do to get that running?
You don't need anything special to have the billard running.
On Windows you don't have the graphical version "billard"
but you should have the text-only "billard-nogui" version.
in order to run billard you should
1) run
rtig
2) run
billard-nogui -n "Name1" -fTest -FTest.fed -t10
will make one billard running fro 10 seconds.
you can [theoretically] launch as many billard as you want.