Feature Description
Default problem template initialization should be with a named trajectory object. The construction of this object can be accomplished using overloaded problem template constructors, but the documented default should use trajectories.
Error handling---reporting improperly configured named trajectories---should be the responsibility of the problem template.
This issue should move us closer to being able to dispatch based on trajectory type (e.g. smooth pulse without the Unitary or Trajectory lead). A separate issue should be created for "dressed" named trajectories which attach to integrator type, similar to how LinearAlgebra can call specialized methods on Upper Triangular and Hermitian matrices.
Importance
1 (lowest)
What does this feature affect?
Other information
No response
Feature Description
Default problem template initialization should be with a named trajectory object. The construction of this object can be accomplished using overloaded problem template constructors, but the documented default should use trajectories.
Error handling---reporting improperly configured named trajectories---should be the responsibility of the problem template.
This issue should move us closer to being able to dispatch based on trajectory type (e.g. smooth pulse without the Unitary or Trajectory lead). A separate issue should be created for "dressed" named trajectories which attach to integrator type, similar to how LinearAlgebra can call specialized methods on Upper Triangular and Hermitian matrices.
Importance
1 (lowest)
What does this feature affect?
Other information
No response