Hi

1. You don't need to repeat-schedule a steppable to tick-tock every second
until the package makes it to the other end. If it takes 3.25 time units
for the package to get there, schedule it (the package ?) once for 3.25d
from the current time.

2. You can take a look at my now-open source traffic simulation
(http://cs.gmu.edu/~eclab/projects/mason/projects/traffic/)
Cars do show up at the other end of a road after a time proportional to
the length (weight) of the road. The queueing mechanism might be
different, e.g. if you want your nodes to service packages based on
some priorities.

G


On Tue, 11 Jan 2011, MASON-INTEREST-L automatic digest system wrote:

> There is 1 message totalling 29 lines in this issue.
>
> Topics of the day:
>
>   1. ADVICE - modeling flow in a network
>
> ----------------------------------------------------------------------
>
> Date:    Mon, 10 Jan 2011 12:37:54 -0800
> From:    Stephen Beitzel <[log in to unmask]>
> Subject: ADVICE - modeling flow in a network
>
> I've just discovered the MASON framework and have started writing my
> first simulation. I have constructed a grid of nodes (held in a
> SparseGrid2D) and connected them in a Network. Now what I'd like to do
> is allow nodes to send packages to each other along the edges in the
> network, and I'm thinking about how best to accomplish this.
>
> I want the time it takes for a package to traverse an edge to be
> proportional to the edge's weight (held as the Edge's info Object). So
> far what I've come up with is a class to represent the package and a
> Steppable that counts down time for the package. When the package
> figures it has arrived, it stops the corresponding Stoppable and then
> delivers itself to the receiving node. This requires that the sending
> node have access to the SimState (so it can schedule the Steppable and
> hand the Stoppable to the package). All this entangled knowledge of
> the sim feels inelegant, though. Is there a cleaner way to do this?
>
> I'd kind of like to be able to have the originating node construct the
> package and hand it off to the edge, which would deal with keeping
> track of packages en route and delivering the packages to the node at
> the other end.
>
> ------------------------------
>
> End of MASON-INTEREST-L Digest - 8 Jan 2011 to 10 Jan 2011 (#2011-7)
> ********************************************************************
>