Jump to content
Simio Forum

jdoran

Members
  • Content Count

    670
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jdoran

  1. Nope, the 64bit version still will not open the model with a massive data table (at least not within the 5mins I was willing to wait for it). I left the model opening over night (via the 32bit client), and came in this morning to it opened. I have removed the datatable, and will have to explore using a database, etc.
  2. Nice pick-up. I had completely forgotten about that. Let's see if that works.
  3. Has anyone else experienced significant performance hits when dealing with large tables in their models? One of my tables has a bit over 230k rows. Since adding the table the model can take up to 30seconds to save (on a SSD), and since closing the model, it no longer seems to load. I can see that tables are added directly into the model xml data which does not seem to make much sense.
  4. So each wait step would require a state/property, a timer and two assign blocks. It's simpler than making the re-usable process with passed tokens, and probably more durable. Thanks. I'll have to go back and update my models, and keep it in mind in the future.
  5. This fixed the outstanding bug where writing in an experiment would dump all csv files in the simulation root directory, ignoring the relative directories you specify in the file path in the file element. The fix was trivial, and I am sure I have raised it several times both on this forum. I made the fix a few months ago, and have kept meaning to post it here (if indeed I have not already). The problem with unofficial fixes is that it is another moving part to update, keep track of, and adds to installation complexity. I have lost previous fixes twice (due to fresh re-installs). Essential
  6. I dont recall making a variable timer being an easy thing to do. I believe they required their own state variable. It will make the code harder to read and debug too. I currently execute side processes with delays that fire events. This is even worse in some ways as it makes multiple tokens that then need to be handled.
  7. Is it possible to implement a wait step that either waits for a specified time, or for an event to be fired (which ever comes first). I hacked together a model where I execute a process before the wait step, that delays for the time and fires an event. I then simply listen for either event at the wait step. I don't think this is very neat. Is there a better way? I can see there are timer elements, but I don't see how you would invoke one simply to act as a countdown.
  8. Some SimBits that may be relevant. Pick Up Drop Off Flow <- flow related, i.e. liquids Appointment Arrivals Moveable Operator Using A Storage Queue Seizing Vehicle Vehicle Finishes And Parks When Off Shift The two most relevant SimBit sections will probably be: Vehicles Schedules / Changeovers
  9. Just a tip from briefly reading your description: You will want to look at some of the SimBits around entities getting transported by transporters. In general I advise just looking at each SimBit as regardless of name, there are some interesting concepts/techniques that will apply regardless of the scenario you are trying to simulate. I will dig out the SimBit names when my model stops running. =P
  10. I think the more pertinent question is what backup files are actually meant to do. I have found that when ever my model corrupts, the backup is _usually_ useless too. Why would you want to disable them anyway?
  11. Thanks for the offer, but the routing has to be decided by entities in my case.
  12. I was using entities to seize transporters as they entered servers, I then abstracted these chains of servers into sub-models, and then sub-models of these sub-models such that I could re-arrange and order these chains easily, and so I could have 12 or so of these long chains encapsulated in single objects that sit in the top level model where the transporters and entities start. When the entity enters one of these servers, it is added into the allocation queue for the transporter (I might be referring to the token... but for all intents and purpose it is the entity as these tokens are cr
  13. I don't think I solved this one. I think I worked around it by making better logic to ensure that sure I didn't get into dead-locks in the first place. It is kind of awkward to do a looping find and remove on the AllocationQueue over many transporters before every seize in the model just to try and keep synchronicity between different levels of nested models that can't directly see each other. The downside with messing with the allocation queue (by either removing or only seizing when conditions are ideal), is that you can't generate any kind of Gantt chart to see what is SPECIFICAL
  14. See the navigation panel? Click on the project root folder: Then ctrl + C & ctrl + V into the new project. The recommended approach though is to load models as libraries into new project files... but if you are not careful... it is very easy to get duplicate project id errors, etc.
  15. Have a look at the "Interruptible Operator" simbit.
  16. http://www.simio.com/forums/viewforum.php?f=4 Insiders get access to the latest sprints ahead of everyone else. If you are posting here, I assume that you an insider that will have access to that sub-forum.
  17. Those are just the default schedules, modified to be a straight 30minute interval. As for that expression: StandardWeek.TimeUntilNextValue(TimeNow) * 60 <= 0.6 In the latest sprint, we can now tap into the schedules to look at how long until the next scheduled change. Schedule || SIMIO FUNCTION || REFERENCE POINT TIME || 60 (to convert from hours to minutes) || 0.6 seconds (because we are using delays, we need to make sure we have a big enough window that we are likely to check within) Make sure you are running the latest copy of Simio.
  18. Using the dummy server to trigger a process for onshift, offshift that would drive your model smarter than delays. The model I provided was an example of using the schedule. The easiest solution completely depends on the complexity of the scenario you are modelling.
  19. Attached is a very rough attempt at the concept. It may help you think of a cleaner way to approach this problem. I would recommend using a trigger based approach, which would require a "dummy server" to act as the sift overseer, to trigger the change. time_limit_on_working.spfx
  20. From Simio Support: repeat_group_search_support.spfx
  21. I am not sure this is really possible, without modifying the transporter... but those benefits listed are pretty nice.
  22. In table properties, if you put a reference to the server objects, on that column you can set a property that says something like "auto set row". This will auto set the table row for each entity as it enters the servers. Hope it helps.
×
×
  • Create New...