ViniciusF

What you could do is add a different configuration to your Excel Importer for each scenario. Then they appear on the experiments tab. I don't know if there is a more simple way of doing it.

Hi, What you could do is set up another column with the weights (likelihood) of creating each entity type... so you can set up probabilities any way you want it. Look SelectEntityTypeFromTable - SimBit to learn how to do it.

I used rate tables once, these events per hour does not guarantee that you'll have that amount of entities on the time interval. It varies from replication to replication. Sometimes you'll generate less, sometimes more.

My bad, the correct expression is Worker.RideStation.CurrentCapacity.

Hello, Worker has a state variable to set ride capacity on run time (Worker.RideStation.Capacity). What you could do is save the number created on a modelentity variable, and set up a addon process trigger on Entered of the node MemberOuput@Separator to first verify if it is a worker (Decide Step with Is.Worker), and if true, you would use a Search step to search through QueueState -> Separator1.MemberOutputBuffer.Contents and assign the Worker.RideStation.Capacity to the value of the modelentity variable found.

Is it fair to say that the longest waiting time in the parent queue is the first entity at the queue? If so, you could use something like: Candidate.Node.AssociatedObject.Combiner.ParentInputBuffer.Contents.TimeWaiting(Candidate.Node.AssociatedObject.Combiner.ParentInputBuffer.Contents.FirstItem) to access the combiner which has the largest value of the time waiting of the firstItem in the queue. It seems to work

You need to put the search, release and transfer steps into the Add-on Process Triggers "Parent Entered" of the Combiners. For example, for the "Juntar_secos" combiner, at the "Parent Entered" Addon process, you would search for Slots.Processing.Contents, matching "Candidate.ModelEntity.Id_Del_Pedido == ModelEntity.Id_del_pedido". After that you should use a release step, to release Server "Slots", and a transfer step to transfer what have been found to Output@Slots.

Well, first thing, you don't need your entities to be bouncing between the output and the input of your server like that. If you want to use it as sort of storage, set both the processing time and the capacity to infinity. After that, at the moment that the parent entity enters the combiner "Parent Entered" you could search the queue of your storage using a search step with something like "Server1.Processing.Contents", with the condition of "Candidate.ModelEntity.State == ModelEntity.State", release the server and transfer what have been found to the output. You need to take some care on some situations, like what if the parent entity arrives first at the combiner then the member at the storage? And some care with batching quantities aswell. But I think you can handle it.