[codes-ross-users] ROSS debugging?

[Christopher D. Carothers]

Hi Jian;

Good question. So, ROSS does not keep "un-handled" events. Instead, it
"drops" any event scheduled after the "end time" you've specificed for your
simulation run. Thus, when the simulation ends, there are zero events in
the pending event list.

So, it sounds like you want to capture/record any events that are scheduled
beyond end time, which you can do with
a tw_output -- that will output only the commited event drops because of
optimistic event processing. So, here you compare the event's time stamp
you are about to schedule into the future with tw_event_new to g_tw_ts_end
and if the new event's time stamp is greater, then you know that event will
be dropped ...

Hope that helps..
Chris



On Mon, Jul 24, 2017 at 12:40 AM, Jian Peng <jpeng10 at hawk.iit.edu> wrote:

> Hi,
>
>     Could anybody give some general idea of debugging a ROSS event tree?
>
>     I'm currently having a problem like node A have sent 2048 events to B,
> but before B receives all events, the simulation ends normally. And no
> leftover messages in any queue on routers or terminals.
>
>     It seems all PE have finished processing all events in their own event
> tree. If I want to see where those "un-handled" events go, is there a
> better debugging way other than adding printfs manually?
>
>     Thanks!
>
> _______________________________________________
> codes-ross-users mailing list
> codes-ross-users at lists.mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/codes-ross-users
>
>


-- 
----------------------------------------------------------------------------------------------
Christopher D. Carothers

Director, Center for Computational Innovations
Professor, Department of Computer Science
Rensselaer Polytechnic Institute
110 8th Street
Troy, New York 12180-3590

e-mail: chris.carothers at gmail.com
web page: www.cs.rpi.edu/~chrisc <http://www.cs.rpi.edu/%7Echrisc>
phone: (518) 276-2930
fax: (518) 276-4033
----------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/codes-ross-users/attachments/20170724/ab0a21a4/attachment.html>