Set different label value to patients by percentage in proximity system.

Question

question

Tom asked Oct 14 2022 at 3:09 AM Tom commented Oct 14 2022 at 9:13 AM

Set different label value to patients by percentage in proximity system.

Hi.

According to patient's label, I want to set different label value to patients by percentage.

Specifically, Floor spot1 give 'get' label's value - 0 or 1' to patient using set label function of proximity system.

Patients who have 'type a' label have 70% to acquire 'get' label's value - 0 and 30% to acquire value - 1 by Floor spot1.

Patients who have 'type b' label is the opposite.

I tried to solve this problem in patient flow but I couldn't find the way.

So I think I should to use code in set label page of proximity system.

Could you help me to solve this problem?

Thank you.

Q_set different label value by percentage.fsm

Software Version:

FlexSim 22.2.2

proximity agent system set label by percentage

q-set-different-label-value-by-percentage.fsm (107.4 KiB)

______

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 · 2022-10-14T06:46:20Z

Felix Möhlmann answered Oct 14 2022 at 6:46 AM Tom commented Oct 14 2022 at 9:13 AM

You could probably also solve this with a Decide activity in the patient flow, but using the proximity trigger is likely quicker.

Check which of the two "type" values are present on the patient, then use the "bernoulli" distribution to assign one of two values by percentage.

Object patient = agent.object;
if(patient.type == "a")
{
    patient.get = bernoulli(70, 0, 1, getstream(patient));
}
if(patient.type == "b")
{
    patient.get = bernoulli(70, 1, 0, getstream(patient));
}

1665729957907.png (5.7 KiB)

· 3

Tom commented · Oct 14 2022 at 7:28 AM

Thank you for your replying!

I add code snippet in proximity trigger and it seems to be working properly.

Doesn't it matter to enter any value to 'tag value'?

Q_set different label value by percentage1.fsm

0 ·

q-code-snippet.png (28.6 KiB)

q-set-different-label-value-by-percentage1.fsm (46.8 KiB)

Felix Möhlmann Tom commented · Oct 14 2022 at 9:06 AM

I'm not sure what you mean by "tag value". The default code of the "Set Label" option uses different, older syntax when creating/setting the label.

patient.get = ... essentially does the same as patient.labels.assert("get").value = ...

The default code first assigns the object, label name and value to distinct variables in order to enable entering those in the option's GUI.

At this point you can actually delete the "Set Label" option from the trigger. The code snippet alone is enough to create and set the label.

0 ·

Tom Felix Möhlmann commented · Oct 14 2022 at 9:13 AM

Ahhhh, Ok!

Thank you so much!

0 ·

question