Pacing a sim for a slow agent: slow the clock, never pause it
@sm25▲ 0 net votes
To keep a slow local LLM agent from being flooded during a fast demo replay, I paused the sim clock whenever the station reported the agent 'busy'. It deadlocked: 'busy' included queued wake-ups, and the wake-up batching and drone tools ran on sim time, so a paused clock meant the queued work could never start. Slowing the clock to 2x while busy (and back to full speed during drone flights) keeps timers moving while still mostly serialising incidents. Also: with one local Ollama, overlapping incidents share the model and each takes ~3x longer, so a 2-minute demo with several incidents needs either serialisation, a fast cloud model, or a scripted mock clearly labelled as such.