Multiple event in the same wait for event activity: bug or missing feature?

Question

question

Alessio Merlo asked Jun 07 2017 at 8:14 AM Matthew Gillespie answered Jun 19 2017 at 6:48 PM

Multiple event in the same wait for event activity: bug or missing feature?

Hi,

today I tried to model a monitor on the object state change, but I encountered some troubles.

I used the activity Wait for Event, I sampled the object and I chose the event "state change" twice. Why twice? Because I want to listen the transition from any state to blocked or breakdown state. But when I ran the model an exception occured. I isolated the issue in a simple model (waitforevent-1.fsm).

I don't know if it is a bug or a missing feature. I tried to reproduce a double event listener in another model (waitforevent-2.fsm), but the issue occurs again.

Then I believe that it is a missing feature. Will be possible to implement this feature in the next release?

Software Version:

FlexSim 17.1.2

bug wait for event feature request

waitforevent-1.fsm (18.8 KiB)

waitforevent-2.fsm (20.5 KiB)

· 2

Matthew Gillespie ♦♦ commented · Jun 07 2017 at 8:28 PM

Is there a reason you don't want to use two different Wait for Event activities for this?

0 ·

Alessio Merlo Matthew Gillespie ♦♦ commented · Jun 08 2017 at 9:14 AM

Yes, because with only one activity I want to simulate an "or" condition: the first event catched releases the token. With two different activities I would manage the "abort" of the activity which doesn't trigger the correct event. Is the idea clear?

Your proposal is valid workaround, even if I must use at least 3 activities (with only one I would obtain the same result). I found another workaround using decision condition at the end of activity which implements a switch case on the state saved into a label. My solution isn't so "elegant" because a self loop to the same activity I need, but use only one activity and no "abort" condition.

As for you, is a bug or a missing feature? I believe that the feature is implemented correctly, but there is an issue in the cycle which calls back the listener. I suppose this situation: the trigger has two listeners related the same activity, when the first one is called back releases the token of the activity which destroys the second one while exiting. Then the cycle to call back the monitor want to do two iterations, the first one is performed correctly, the second one fails because the call back function doesn't exist more. I don't know how the call back system is implemented, then it is only a hypothesis.

Any futher details are appreciated.

0 ·

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2017-06-19T18:48:30Z

Matthew Gillespie answered Jun 19 2017 at 6:48 PM

We've added this to the list of bugs to fix for the next 17.0 bug fix release. Thanks for pointing it out!

question