Setting xl = xu for some parameters to set them #512
Unanswered
MidnightBiscuit
asked this question in
Q&A
Replies: 1 comment
-
I would recommend always defining a new problem where only the free parameters are set (for some algorithms defining a variable with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I have a problem with 15 parameters and want to test different configurations. Sometimes I want to optimise only using two free parameters, sometimes four ou six etcetc. The others have to be set by me. To keep some flexibility I defined the problem with
n_var=15
and change the boundaries to reflect which parameters are free and which are not. For instance a problem with 4 free parameters and 11 parameters set to a given value looks like thisMy question is : is this a valid way of doing it ? Does the algorithm manage this in a nice way or should I arange my program to only include genuine free parameters in the boundaries ? I don't want the program to do something crazy becase I suggest that I have 15 free parameters but then set some of them with a degenerated boundaries.
I tested this and the result seems to be reasonable, no errors, result has a physical meaning and the solution is in the expected range. But maybe it is not optimum or a bit unwise ?
For my problem I use the following algorithm and minimisation routine
Problem is inherited from
ElementwiseProblem
, I have two objectives, zero constraints.Beta Was this translation helpful? Give feedback.
All reactions