Re: [certi-dev] CERTI deadlock

[Michael Raab]

Yes and No,

for all our "active" federates,
lookahead is 60 for the complete simulation.

For our "oberserver" federate
the initialization/runtime looks like this:

- joinFederation
- enableTimeRegulation( 0.0, 0.0 )

// start all active federates...

disableTimeRegulation()

enableAsynchronousDelivery()

while(true)
{
        tick(0.1,
0.5)
        
        queryLTBS();

        //
display current simulation time based on LTBS
}

So for the startup phase lookahead of
the observer is 0, but after calling disableTimeRegulation() this shouldn't
matter. Or am I wrong?

Thanks,
Michael



Von:      
 Eric Noulard <address@hidden>
An:      
 CERTI development discussions
<address@hidden>
Datum:      
 15.06.2012 08:42
Betreff:    
   Re: [certi-dev]
CERTI deadlock
Gesendet von:    
   address@hidden

---

2012/6/15 Michael Raab <address@hidden>:
> I think it may help to forward all RTIA output messages to a certain
log
> file. I tried the following:
>
> // redirect std::out and std::cerr to file
>
> // get process id
> DWORD pid = GetCurrentProcessId();
> stringstream outfilename;
> outfilename << "d:\\rtia_" << pid << ".log";
>
> ofstream logfile;
> logfile.open (outfilename.str().c_str());
>
> cout.rdbuf(logfile.rdbuf());
> cerr.rdbuf(logfile.rdbuf());
>
> But unfortunately nothing seems to be dropped to this file.
> May be its because the PrettyDebug code has the following static var:
> std::ostream PrettyDebug::_defaultOutputStream(std::cerr.rdbuf());
> Is it somehow already possible to redirect the output?

I'm just coming back from a 4 days trips
"off network"

I'll try to help you out in a couple of hour.

Just to be sure, we have a bug concerning Zero-Lookahead deadlock:
https://savannah.nongnu.org/bugs/?34922

but in your case all federate do have non-zerol LK right?
-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org

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