Home/Tools/chiaha-SLX

chiaha-SLX

A simulation language for models written as code. It runs SLX and GPSS/H style models, and our team can move Plant Simulation and ExtendSim models into it.

What it is

A model you can read

In chiaha-SLX a model is a short text file. Each customer, part or vehicle is an object with its own steps: wait for a resource, take it, hold it for a while, let it go. The example here is a barber shop.

Models compile to native code, so a long run or a few hundred replications finish quickly.

module barber
{
  control boolean barber_busy = FALSE;
  int             served = 0;

  class Customer
  {
    actions
    {
      wait until (!barber_busy);
      barber_busy = TRUE;
      advance rv_expo(1, 16.0);
      barber_busy = FALSE;
      served++;
      terminate;
    }
  }
  ...
}
Part of a barber shop model. Each customer waits in line, gets a haircut of about 16 minutes and leaves.
What it runs

Bring the model you already have

If your team wrote models in SLX or GPSS/H, many will run as they are. Send one and we’ll tell you what runs today and what needs changing.

Plant Simulation and ExtendSim models don’t open directly. Our team rebuilds them in chiaha-SLX and checks the new model against the old one’s results before anything is retired.

Learn more about running SLX models, GPSS/H style models and the example models with their code.

ModelHow it gets inStatus
SLXRuns as written, or with small changesEarly access
GPSS/H styleRuns on a GPSS layer written in the languageEarly access
Plant Simulation, ExtendSimRebuilt by our team, checked against the originalAvailable
Item and rate flow in one modelDiscrete event and discrete rate togetherEarly access
Verification and validation

Two different checks

Verification asks whether the language computes what it should. chiaha-SLX is checked against queueing theory, including single and multi-server queues, breakdowns and customers who give up waiting, and against the answers printed in the SLX and GPSS textbooks. The checks run every time the language changes.

Validation asks whether a model matches the real system, so it’s done one model at a time. When we move a model into chiaha-SLX, the new model has to reproduce the original’s results first, then the system’s measured history where it exists, before anyone relies on it.

Two ways to use it

Write it yourself, or hand it to us

License chiaha-SLX

For teams that build their own models. You get the language and its model library, and we help with the first models. Early access is free: 25 runs a day, runs of up to 10 seconds and up to 5 replications at a time. Paid plans for teams are coming; talk to us if you need more now.

We move your model into it

Send us an SLX, GPSS/H, Plant Simulation or ExtendSim model. We move it into chiaha-SLX, show that it gives the same answers, and hand it back with notes your next modeler can follow.

FAQ

chiaha-SLX,
plainly answered.

Will my SLX model run unchanged?

Many do. Send us the model and we run it, then tell you what runs as is and what needs changing.

Can you move a Plant Simulation or ExtendSim model?

Yes. Our team rebuilds the model in chiaha-SLX and checks that it gives the same answers as the original before you retire the old one.

Do I have to write code?

Not if we move or build the model for you. If your team writes models, the language reads like the SLX and GPSS they may already know.

Is there a free version?

Yes. Early access is free and instant: 25 runs a day, runs of up to 10 seconds, up to 5 replications at a time, in your browser on ChiAha Cloud. Try it free.

Where does my model go?

Your model stays yours. Each run happens in a temporary folder on our server that’s deleted as soon as the run ends. We don’t keep your model or its results; your draft is saved only in your browser.

SLX and GPSS/H are trademarks of their respective owners. ChiAha is not affiliated with or endorsed by them.

Early access

Try it free

The free plan runs in your browser on ChiAha Cloud, with nothing to install. Moving a model you already have starts with a conversation: tell us what it’s written in and what it answers.