Idea

@Jörg Vogel, the solution works but it isn't user friendly. Our team use to have a lot of scenarios those they want to avaliated but they need more than 1 replication to present the variability of that. As the model takes long, it is interesing that they can following the results for each scenario during run time.

This can help them to change the strats based in partial results or check if they have a configuration error or making sure about the results before all run time.

The solution puting just 1 replication works, but in case to have 20 replications, you need to put 2 models for running, and for avoiding the duplicates, you need to abort the 1st replication of the second model... What is possible, but is not user friendly .

So, we believe if we had an option for choose "How do you want to run your model by experimenter" could be a good approach.

If you have a computer with 40 threads available and you have a configuration error in scenario 5, using the standard option you will check the problem just in the third cycle of running,what can take long .In the second option, you are able to see in the first cycle, because of that could be helpful.

What is the problem to set the number of replications to "1".