How to get the scenario parameters in optimizer?

[rajankur6494]

[ FlexSim 23.2.0 ]

Hi Team,

I am running optimizer to find the best production schedule but for 1 scenario, the run is not completed and stuck at 65% every time.

I would like to check this scenario in detail while running the model, but I am not able to find the parameters in advance.

The parameter variability is chosen from here:

Is there any way to find the parameters since run is not completed.

Thank you!

[joerg_vogel_HsH]

@Ankur A3, you show two pictures. We haven’t any clue how they are processed in a model, nor we know how you let OptQuest transform this data into values in your model maybe causing problems. OptQuest tests a model by inserting on model run start parameters and analyzing results at run stop to provide solutions meeting conditions best. You can do this manually without OptQuest. You let run your model with exactly same setup of parameters and allowed variations of OptQuest.

[moehlmann_fe]

Does the solution below not work in this case?

https://answers.flexsim.com/questions/155798/getting-scenario-description-before-optimizer-resu.html...

[rajankur6494]

@Felix Möhlmann,

I tried it but it is not able to open the excel file.

[rajankur6494]

@Joerg Vogel,

Yes, I set up the parameters and allowed opt quest to make all the possible variation.

I can do it manually, but it takes little time to design scenario permutation and combination.

Thank you!

[moehlmann_fe]

Are you sure that the file path is correct and is the file located somewhere that doesn't need admin rights to open? Also, is the file open while you run the experiment? That would also cause this error.

In regards to Joerg's comment and your answer:

You can use a range based job to define a job that runs through all possible permutations/combinations in a few seconds.

[JordanLJohnson · Accepted solution]

Try this code:

treenode expr = Model.find("Tools/Experimenter");
function_s(expr, "setModelToScenario", 1, 1);

The setModelToScenario function_s accepts two parameters: a Scenario ID and a replication number. As long as the scenario ID is present in the database, this function should succeed. The first scenario the optimizer submitted will have ID 1, the second will have ID 2, etc. (assuming the optimization job is the only job that has run using the current database file).

[Jeanette_Fullmer]

Hi @Ankur A3, was Jordan Johnson's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.