Shinya O avatar image
Shinya O asked Jeanette F commented

OptQuest Error - A variable name has been duplicated


OptQuest Error occures in the following model, OptQuestError-A_variable_name_has_been_duplicated.fsm in the FlexSim Cloud.

The error message said it's a variable name problem, but I don't think so.

What does this error mean?

Thanks in advance



FlexSim 22.0.4
optquestoptimizeroptquest error
1659670192075.png (199.7 KiB)
1659670332133.png (206.3 KiB)
· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jeanette F avatar image Jeanette F ♦♦ commented ·

Hi @Shinya O, 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 unaccept and comment back to reopen your question.

0 Likes 0 ·

1 Answer

Jordan Johnson avatar image
Jordan Johnson answered Jeanette F commented

This is a bug. I will add it to the dev list to get it fixed. It happens because OptQuest sees a sequence as many variables instead of one. So FlexSim generates a name for each of the sequence values. Right now, it generates those names by concatenating an index with the parameter name. So for Sequence14, it generates:

  • Sequence141
  • Sequence142
  • ...
  • Sequence1410
  • Sequence1411
  • ...

And for Sequence141, it generates:

  • Sequence1411 (which duplicates the 11th value from the previous sequence)
  • Sequence1412
  • ...

Until this bug is fixed, you'll have to avoid this bug by ensuring that if you have multiple sequence parameters, that their names don't end in a digit (1-9).

· 8
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jordan Johnson avatar image Jordan Johnson ♦♦ commented ·

Or you could use leading zeros in your parameter names: Sequence041, Sequence141. Again, that's just a workaround until the bug is fixed.

0 Likes 0 ·
Shinya O avatar image Shinya O Jordan Johnson ♦♦ commented ·
Is this bug fixed?
0 Likes 0 ·
Jeanette F avatar image Jeanette F ♦♦ Shinya O commented ·
Hello @Shinya O,

This was fixed in 22.0.7

1 Like 1 ·
Show more comments