You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would probably suggest that when a solution is implemented, it is done in such a fashion that the user has to specify whether a variable is continuous or discrete, with continuous being the default choice, that gets applied unless you actively do something. It would seem natural to most people to enter min/max values as whole numbers in very many cases, without the implication that they are discrete integers. This is also how this choice is dealt with In classical DOE software, such as Design Expert:
Having looked a bit into the code the proper solution seems to be in line with the suggestion from @dk-teknologisk-mon
We suggest to add an input type to the "Add variable" dialog like in this mock-up
Enterring float range between 0.0 and 1.0 gives wrong performance on "next experiment", only returning integer values:
Enterring float range between 0.1 and 1.1 gives expected performance on "next experiment":
The text was updated successfully, but these errors were encountered: