JaamSim2015-01 released

69 views
Skip to first unread message

Harvey Harrison

unread,
Jan 8, 2015, 7:16:57 PM1/8/15
to jaamsi...@googlegroups.com
Another year, another release.

- The deadlock issue reported earlier has been fixed, please report if you see any others.
- saved config files now save the unit types before other dependent keywords avoiding errors on reload
- additional validation has been added to some keywords where only a certain range of values is allowed
- there is additional functionality for controlling queuing behavior, which I will let Harry expand on.

Cheers,

Harvey

Harry King

unread,
Jan 8, 2015, 8:15:28 PM1/8/15
to jaamsi...@googlegroups.com
Most of the feature requests and bug reports that I received over the last few weeks are implemented/fixed in release 2015-01.

- EntityGenerator can create multiple entities per arrival time

- Queues can be shared between multiple Servers, Seize blocks, etc.

- Entities can be sent directly to a Queue instead of via a Server, Seize block, etc. The queue notifies the all its Servers, etc. whenever an entity is added to the queue.

- Queues can use a priority input to sort the entities (see attached example)

- Seize blocks now send all entities to its queue before processing

- Seize blocks now implement the OperatingThresholdList keyword

- keywords that accept a probability distribution or a time series now test on start-up that the minimum and maximum values for these sources are valid for the input. For example, the input for ServiceTime keyword for Server must be >= 0 s. A NormalDistribution will generate a validation error on start-up unless the input for its MinValue keyword is >= 0 s.

Enjoy,
Harry

Example 2 - Server and Queue with Priority.cfg

Jerry L

unread,
Jan 8, 2015, 9:17:45 PM1/8/15
to jaamsi...@googlegroups.com
Wow, you guys have been busy!

I can't wait to try out the new build!

Jerry L

unread,
Jan 8, 2015, 9:22:35 PM1/8/15
to jaamsi...@googlegroups.com
 A NormalDistribution will generate a validation error on start-up unless the input for its MinValue keyword is >= 0 s.

If it generates a value below the minimum, does it set it to the minimum or does it resample? 

For example, if I call the normal distribution and set MinValue to 0, and the distribution returns -0.5, does it return a value of 0, or will it re-sample until it gets a value >= 0?

Harry King

unread,
Jan 8, 2015, 9:30:46 PM1/8/15
to jaamsi...@googlegroups.com
Jerry,

Samples that are outside of the MinValue/MaxValue range are rejected and re-sampled. The pop-ups for the two keywords make a note of this.

If you just cap the sampled values, you get weird looking spikes at the two boundaries.

Harry


Jerry L

unread,
Jan 9, 2015, 9:05:26 AM1/9/15
to jaamsi...@googlegroups.com

- Entities can be sent directly to a Queue instead of via a Server, Seize block, etc. The queue notifies the all its Servers, etc. whenever an entity is added to the queue.


I just made a small model where I sent the entities directly to a queue.  At least for these small models, it was more intuitive and easier than the previous way. 
Reply all
Reply to author
Forward
0 new messages