Skip to content

Conversation

@andgoldschmidt
Copy link
Member

@andgoldschmidt andgoldschmidt commented Mar 13, 2025

  • Updated all min time and sampling problem templates for kets and unitaries
  • Some bug fixes in fidelity defintions
  • Free time is no longer optional
  • Add final fidelity constraints using KnotPointConstraint from DirectTrajOpt.jl
  • Removed some piccolo options that were not being used (options are not tested well)
  • A handful of objectives are gone (temporarily?), leading to a few removed PTs
  • unrelated, remove density pt bc didn't have a chance to refactor and write its tests

Some potential outstanding issues:

  1. Minimum time problems are only well-behaved with fidelity constraint of 1.0
  2. Minimum time problems currently require the goals to be passed as an argument. This is because the trajectory stores the goal states, but not the subspaces. This should eventually be addressed because there's no reason to need to pass these around as args.
  3. Problem template testing should start taking advantage of shared code.

@andgoldschmidt
Copy link
Member Author

andgoldschmidt commented Mar 13, 2025

Tests pass locally with develop install of harmoniqs/DirectTrajOpt.jl#4

@andgoldschmidt andgoldschmidt requested review from aarontrowbridge and jack-champagne and removed request for aarontrowbridge March 13, 2025 08:12
@jack-champagne
Copy link
Member

Pulling this down this AM to test build

@jack-champagne
Copy link
Member

Everything looks great, I'm going to make a package addition this PM for DirectTrajOpt.jl into general. I am worried though that it will be flagged for similarity since IndirectTrajOpt.jl is also registered. But I believe we should be able to override that with a quick discussion

@andgoldschmidt
Copy link
Member Author

The issue with min time problem templates and the fidelity constraint has been resolved, it was an objective weight and an inequality ordering issue.

@jack-champagne
Copy link
Member

No more dev install, all tests pass (except for one that I marked as broken because it was not consistently passing. Ticket to fix has been made.)

Comment on lines +208 to +209
@test_broken false
# @test final > initial
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the one marked broken for now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll have to check, I didn't do any work on the piccolo options constraints for this refactor, and don't remember adjusting. I'll have to look again when I'm on my laptop not mobile

Copy link
Member

@jack-champagne jack-champagne Mar 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, this has been flaky for a while - don't think this was induced by your work for this since you didn't touch PiccoloOptions and I saw this happening months ago

@jack-champagne jack-champagne merged commit 2210265 into main Mar 16, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants