Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by johnhagood

  1. I want to set a timer that represents "time of failure" where if the entity is not processed within this time, it will be deemed a failure and be destroyed. This time needs to be dependent on a random draw (one for entity type, and one for a distribution based on entity type). I also need to be able to change this time due to interventions that happen. Is it possible to do this?
  2. The main problem I see with task sequences is I don't see a way to reschedule tasks for later. I used the "Token Wait Action: No Wait" setting on an execute step, then executed the Seize->delay->release process in that step. This does what I wanted. Thanks for taking the time to help.
  3. Yes, it has the same issues, I need to make the task sequences more dynamic. I can't use task sequences as they are implemented to get the functionality I need. It looks like I need to write my own steps.
  4. I want to be able to schedule events for the future without having to define a separate timer for each possible time this will happen. Ideally i'd like to be able to index into a vector of timers to start one, so it can be dependent on a state variable. One use of these would be recurring tasks, for instance, while a patient is in post-surgery, they will be administered medicine every r hours. This is dependent on them exiting surgery (it doesn't begin at a specific time), so a rate table doesn't really work, and that would run into a similar problem of having to define different rate tables for each patient type and recurring tasks (potentially hundreds). Any ideas?
  5. Yeah, I figured that part out. I need more control than task sequences allow me, is there a way to simulate task sequences in processes so I can add more machinery? I can probably make something work with just the sequences, but it will take a lot and I'm trying to avoid getting too complicated at the moment, it's just a prototype.
  6. After looking more into task sequences, it may work, but not without major rework, the primary issues are that the seizing is not the only thing that happens, and work will be done in phases, without moving from the server, and different patients may not have the same phases. I see how it could be done with a second model, but i'd like to avoid getting too complicated if I can Is it not possible to do what I asked in my original question?
  7. In the final model, we could potentially have ~1000 different task sequences for all of the different patient types and severities, is there a way to store task sequences in the data (or otherwise in a way that can be held in a database and imported?) That would be much more manageable.
  8. I am working on a model of an emergency room, and I'm having trouble figuring out how to model multiple personnel working on a patient at once. For instance, when a patient enters, the patient will attempt to seize a nurse, a PA, and a Doctor to do a number of tasks that can be done simultaneously (but are not required to be done simultaneously). If the doctor is busy, the nurse and PA should be able to finish their tasks and move on while the patient still waits for the doctor. I need a way to seize-delay-release the nurse and PA and move on with other processes before the doctor arrives. Effectively, I want to schedule the release at a later time, instead of stopping the process with a delay step.
  • Create New...