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
There should be utilities that turn any objective into some appropriate constraint. The constraint should take in an objective and a value as arguments, and the output should be a constraint satisfying the desired condition.
For example,
functionObjectiveEqualityConstraint(objective::Objective, value::Float64)
objective - value =0end
functionObjectiveInequalityConstraint(objective::Objective, value::Float64)
objective - value >0end
This functionality has already been implemented in FinalUnitaryFidelityConstraint, which follows the format of UnitaryInfidelityObjective; the point of this issue is to generalize and abstract this concept.
Suggested checklist
Pick a specific objective (e.g. UnitaryInfidelityObjective objective). Write a routine that creates a constraint from this objective. Compare to the existing constraint (e.g. FinalUnitaryFidelityConstraint).
Importance
1 (lowest)
What does this feature affect?
quantum system construction
problem setup
problem solution
problem performance
solution analysis
plotting
documentation
tests
other (please specify below)
Other information
No response
The text was updated successfully, but these errors were encountered:
This would allow for a much simpler implementation of the constraint class of problem templates like minimum time and robustness. Those problems could extract the existing fidelity objective from the problem params, which by default already "pops" from this list. Then, the constraint could be constructed from this objective using the existing gradients.
The code that computes fidelity and sets up the fidelity constraint in these methods could be mostly replaced.
Feature Description
Background
There should be utilities that turn any objective into some appropriate constraint. The constraint should take in an objective and a value as arguments, and the output should be a constraint satisfying the desired condition.
For example,
This functionality has already been implemented in
FinalUnitaryFidelityConstraint
, which follows the format ofUnitaryInfidelityObjective
; the point of this issue is to generalize and abstract this concept.Suggested checklist
UnitaryInfidelityObjective
objective). Write a routine that creates a constraint from this objective. Compare to the existing constraint (e.g.FinalUnitaryFidelityConstraint
).Importance
1 (lowest)
What does this feature affect?
Other information
No response
The text was updated successfully, but these errors were encountered: