Mathias Winkel
Mathias Winkel
Hi @ricklamers, This PR is definitely nothing you would want to merge right away and is not intended as such. I would rather like to make you aware about further...
With this change, we are storing the relevant parts of the full conversation history (instead of only keeping the user prompts). This makes full use of the chat-API and back-reference...
This is a follow/up of #73. I originally planned to re-open that one, but this seems impossible. The change addresses https://github.com/ricklamers/gpt-code-ui/discussions/6 and https://github.com/ricklamers/gpt-code-ui/issues/62 - at least partially. The idea is...
Currently, parameters/targets only contain a name and some specific properties like bounds or possible values. However, it would be desirable, to allow for conveniently adding some metadata like description, unit,...
The current interface for constraints is a bit inconvenient. E.g., looking at ```python ContinuousLinearConstraint(parameters=["T1", "T2", "t1"], coefficients=[1.0, -1.0, max_temp_ramp_rate], operator=">=", rhs=0.0) ``` Why are parameters and coefficients given in separate...
At https://emdgroup.github.io/baybe/stable/_autosummary/baybe.parameters.numerical.NumericalContinuousParameter.html#baybe.parameters.numerical.NumericalContinuousParameter.metadata, the link to the `MeasurableMetadata` class is not clickable: This also applies to other spots in the parameter-related documentation but seems to work e.g. for targets: https://emdgroup.github.io/baybe/stable/_autosummary/baybe.targets.numerical.NumericalTarget.html#baybe.targets.numerical.NumericalTarget.metadata