set the channel description: discussion and Q&A regarding kalasim, a discrete event simulator written in kotlin

Hey there, feel welcome to get in touch regarding https://www.kalasim.org/

The documentation is really nice. Never have time for it

I think that the Flow itself is a very good model for even-based simulations.

Witing the docs was fun here because of mkdocs. In particular with its option to bind code samples directly into the documentation. This allows to refactor code without breaking the docs.

kalasim is also heavily based on coroutines. Its core is really all about suspendable interactions methods to define processes. I nevertheless will start reading about Flow

As an example see the landing page example which is essentially just coroutines (watch the suspend icon) :

Imho this is a truly amazing way to define a DES process definition. I have looked at many engines in the previous months, but the kalasim approach is by far the most pretty one. Clearly I'm strongly biased 🙂

With great pleasure, I have published v0.6 of kalasim today. kalasim is a code-first process-oriented declarative discrete event simulation engine written in Kotlin for everyone. The release ships with amazing new features such as resource selection policies, bidirectional tick-to-wall clock synchronization, and queue batching. Do not miss the greatly extended examples and get started by modeling your business process just today. See https://www.kalasim.org/changes/

Doc sources are sitting under https://github.com/holgerbrandl/kalasim/tree/master/docs/userguide and are automatically built with mkdocs with every push using a github action defined in https://github.com/holgerbrandl/kalasim/blob/master/.github/workflows/manual.yml I'm also amazed by the beauty of this level of integration.

Finally, kalasim v0.7 https://www.linkedin.com/posts/holgerbrandl_kalasim-v07-activity-6870457112590340096-6B0T

I've built a base on the moon with Kotlin, Jupyter, OPENRNDR and Kalasim. Mining robots scan the surface of the moon for depletable water ice deposits. It is a complex business process, and the lives of thirsty astronauts are at stake. https://www.linkedin.com/posts/holgerbrandl_lunar-mining-activity-6886114828251914240-okCY Slack Conversation

Not sure if any of you will join WSC2022 in Singapore starting in a few days, where the global simulation community celebrates its annual summit. I'll bring Kotlin to the stage there, by presenting kalasim, a code first discrete event simulation DSL/engine written in 100% Kotlin. Read more at https://www.linkedin.com/posts/holgerbrandl_wsc22-activity-7002255950950637568--wMw

Not sure if this also a place to share notebooks, but why not: https://github.com/holgerbrandl/kalasim/blob/master/docs/userguide/docs/examples/callcenter.ipynb. See https://www.linkedin.com/posts/holgerbrandl_call-center-activity-7125430811733954560-dYHp for a short overview. Using

nbconvert

this notebook converted to markdown and inlined into the project website built with mkdocs on https://www.kalasim.org/examples/callcenter/. Tanks to the notebook team (@Ilya Muradyan and @roman.belov) for making this build & analysis process possible. Slack Conversation

Hi kalasimers! I am building a knowledge visualization tool, and want to integrate kalasim into it so that it becomes easy to create and view the systems. It's currently in PoC stage: limandoc.com, but feel free to checkout the website. What do you think? Would love to hear your ideas and perhaps we can collaborate on it. I tried to reach Holger, but apparently he is not using slack here.

@holgerbrandl is there a way to get statistics on how long specific component lifetime is? In my case components are computation tasks. And I want to measure how long do they take.