topic Re: Date Time Source acting as a variable on Experimenter? Process Flow in FlexSim Forum

Date Time Source acting as a variable on Experimenter? Process Flow

daniel_d4 — Wed, 20 May 2020 16:32:33 GMT

[ FlexSim 20.1.2 ]

My model is about bicycle stations and how some of the bicycles stations run out of bycicles so losing potential clients. I want to run experimenter as it follows:

I want to execute 2 scenarios.

Variables on the scenarios(where i have the problem): are the 6 sources of clients (Date Time Source's). I just have one Date Time Table for each source. What i want is that in each of both scenarios, each source use a different Date Time Table for generating the clients which have to pick up the bicycles.

I do not know how to accomplish this, maybe using Global Tables for Data Time Source?

So, I want to use two different tables Data Time for each source (e.g: situations on weekend and another one for working days) and use them as variables for the experimenter. One scenario would be on weekends and the other scenario would be on working days(e.g).

The Perfomance Measures i want to observe are the number of inputs on sink's: Unhappy Clients N1 and Unhappy Client N2. Also the content on lists: "List Bicis Nord 1" and "List Bicis Nord 2", where the bicycles are. (on Dashboard).

I am lost. Any help is much appreciated!

Here i attach my model (Process Flow).

questionExperimenterBicing.fsm

Thank you in advance.

Re: Date Time Source acting as a variable on Experimenter? Process Flow

Matthew_Gillespie — Wed, 20 May 2020 16:50:33 GMT

You should take a look at this other bicycle model for some ideas for simplifying your model.

https://answers.flexsim.com/questions/84894/can-i-release-a-resource-to-another-resource-from.html

Re: Date Time Source acting as a variable on Experimenter? Process Flow

Matthew_Gillespie — Wed, 20 May 2020 21:50:40 GMT

We don't currently have an automatic way of doing this. My suggestion is to use the solution discussed previously here. Basically, make 2 different source activities and put a decide activity after each one. The decide only lets tokens move on if it's the correct scenario, otherwise it sends them to a sink.