ATTENTION

This FlexSim Community Forum is read-only. Please post any new questions, ideas, or discussions to our new community (we call it Answers) at https://answers.flexsim.com/. Our new Question & Answer site brings a modern, mobile-friendly interface and more focus on getting answers quickly. There are a few differences between how our new Q&A community works vs. a classic, threaded-conversation-style forum like the one below, so be sure to read our Answers Best Practices.


flexsim.com

Go Back   FlexSim Community Forum > FlexSim Software > Q&A
Downloads

Q&A Using Flexsim and building models

  #1  
Old 05-05-2009
Markus Bans Markus Bans is offline
Flexsim User
 
Join Date: Aug 2007
Location: D-41199 Moenchengladbach, Germany
Posts: 8
Downloads: 28
Uploads: 1
Thanks: 2
Thanked 15 Times in 4 Posts
Rep Power: 0
Markus Bans will become famous soon enough
Default Scheduled_down and Waiting_for_operator states

Hi there,

in the attached model, the source, Operator1 and both Processor1 and Processor2 belong to a 7 days and 8 hours timetable.

So I expect 66.7 % for the state 'Scheduled_down'.

This is the case for Processor2 and for Operator1, but not for Processor1.

Processor1 shows a lower percentage for 'Scheduled_down' than 66.7 % and also a high percentage for 'Waiting_for_Operator'.

But how can an object wait for an operator, when it's scheduled down?

So why is the percentage of Processor1 for 'Scheduled_down' lower than 66.7 %?

Please run the model fast until time = 604800 s, what is exactly 7 days.

Kind regards,

Markus Bans
Attached Files
File Type: zip Operator_and_processor_states.zip (42.2 KB, 280 views)
  #2  
Old 05-05-2009
Phil BoBo's Avatar
Phil BoBo Phil BoBo is offline
Flexsim Development
 
Join Date: Jan 2008
Posts: 756
Downloads: 109
Uploads: 18
Thanks: 385
Thanked 1,483 Times in 525 Posts
Rep Power: 1174
Phil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond repute
Default

It is because of the order of the stopobject() calls.

When you call stopobject() on an operator who is being utilized by a processor, that operator then in turn calls stopobject() on the processor to make it waiting_for_operator.

So what is happening is that you are stopping the processor, then stopping the operator, which in turn stops the processor again, so the processor is in waiting_for_operator state during its down time.

To fix this you could reorder the members of the time table, but this isn't really a good solution.

The better solution is to increase the priority on the stop request for the time table. In the time table's Down Function, change the priority value from 0 to 1. This way, when the operator calls stopobject() on the processor, that stop request's priority is 0, but the scheduled_down stop that it is currently in has a priority of 1 so it stays in the scheduled_down state.
The Following 7 Users Say Thank You to Phil BoBo For This Useful Post:
Tom David (05-05-2009)

Tags
scheduled_down, states, timetable


Thread Thread Starter Forum Replies Last Post
Creating a stacked bar chart for the states of multiple objects Kris Geisberger Tips and Tricks 6 08-11-2011 09:40 PM
Multiprocessor states and MTBF Markus Bans Q&A 1 03-30-2009 01:34 AM
Flow items with states AlanZhang Q&A 16 11-30-2007 10:32 AM


All times are GMT -6.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 1993-2018 FlexSim Software Products, Inc.