OptQuest Error - A variable name has been duplicated

OptQuest Error - A variable name has been duplicated

ozawa_shinya
Advocate Advocate
471 Views
10 Replies
Message 1 of 11

OptQuest Error - A variable name has been duplicated

ozawa_shinya
Advocate
Advocate

[ FlexSim 22.0.4 ]

Hi,

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


1659670192075.png


1659670332133.png


0 Likes
Accepted solutions (1)
472 Views
10 Replies
Replies (10)
Message 2 of 11

JordanLJohnson
Autodesk
Autodesk
Accepted solution

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).

.


Jordan Johnson
Principal Software Engineer
>

0 Likes
Message 3 of 11

JordanLJohnson
Autodesk
Autodesk

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

.


Jordan Johnson
Principal Software Engineer
>

0 Likes
Message 4 of 11

Jeanette_Fullmer
Community Manager
Community Manager

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
Message 5 of 11

ozawa_shinya
Advocate
Advocate
Is this bug fixed?
0 Likes
Message 6 of 11

Jeanette_Fullmer
Community Manager
Community Manager
Hello @Shinya O,

This was fixed in 22.0.7

Message 7 of 11

ozawa_shinya
Advocate
Advocate
Thank you for your information.
0 Likes
Message 8 of 11

maryamh11
Collaborator
Collaborator

Hi @Jeanette F

I'm using version 24.1.0 and also got this error (A variable name has been duplicated). my variables had 1-9 at the end, i changed them to something alphabetical and the error is gone.

0 Likes
Message 9 of 11

Jeanette_Fullmer
Community Manager
Community Manager
Hello @Maryam H2,

We were not able to replicate this issue in 24.1.0. Could you provide a sample model that demonstrates this issue?

0 Likes
Message 10 of 11

maryamh11
Collaborator
Collaborator
@Jeanette F i don't know if i can create a sample modle for this. Can we meet instead?
0 Likes
Message 11 of 11

Jeanette_Fullmer
Community Manager
Community Manager
Hello @Maryam H2,

Yes, I emailed you times that I could meet to go over your model. We can discus this at that time as well.

0 Likes