[DEFECT] Genetic Algorithm Constraint (implicit) is ignored for 'logistic' fitness

[alfoa]

Thank you for the defect report

• I am using the latest version of RAVEN.
• I have read the Wiki.
• I have created a minimum, reproducible example
  that demonstrates the defect.

Defect Description

• Genetic Algorithm Constraint (implicit) is ignored for 'logistic' fitness
• In addition, the manual is not very clear on the Constraint formulation...there is some info in the fitness section but in the constraint section the constraint is still reported as "boolean" (see previous issue [DEFECT] A lot of tests that uses constraint return Floats as return arg of function. #2053)

Steps to Reproduce

N/A

Expected Behavior

usage of constraint or error at the initialization stage if constraint (implicit) is used with logistic fitness

Screenshots and Input Files

No response

OS

Linux

OS Version

No response

Dependency Manager

PIP

For Change Control Board: Issue Review

• Is it tagged with a type: defect or task?
• Is it tagged with a priority: critical, normal or minor?
• If it will impact requirements or requirements tests, is it tagged with requirements?
• If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

• If the issue is a defect, is the defect fixed?
• If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

[sprapp-inl]

I also have this issue, but I don't think it is related to the specific use of logistic fitness. It seems that in all cases the initialization (sampling for first generation) ignores the constraints, as a sampler outside of the optimizer is required for initialization. I've opened a TASK to see if samplers could be given constraints as well.