Missleading optimal objective
Describe the bug When a local objective depends only on parameters (not variables), it is not read by the complier nor taken into account into the optimisation (it does not appear in the total optimal objective). The numerical value is still present in the output file (.json) but it is not present in the sum of local objectives.
GBOML installation details
- Version: v0.1.9
To Reproduce Steps to reproduce the behavior: Create an objective (such as min: a + b) where a and b are parameters and not variables.
Expected behavior It is evident that such objectives are not useful in the sence that they are not quantities that can be optimised since they are constant. Still, I would expect them to be added in the final objective since they are part of the quantities that must be minimised.
Screenshots
The local objective 63.687 is not present in the optimal one of 69.02.
Desktop (please complete the following information):
- OS: Windows
- Version 11
- Python version: [e.g. 3.12.2]
- Environment type: pip
Additional context /