Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move express and representation types to QuantumInterface #92

Open
apkille opened this issue Dec 22, 2024 · 1 comment
Open

Move express and representation types to QuantumInterface #92

apkille opened this issue Dec 22, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@apkille
Copy link
Member

apkille commented Dec 22, 2024

Right now, I'm working on translating phase space representations of Gaussian quantum objects in Gabs.jl to Fock space representations in QuantumOptics.jl. Should we limit express to one way symbolic-to-numerical translations, or could we use it as a general function that translates between any two packages that depend on QuantumInterface.jl? To me, it seems pretty clean to implement something like express(::GaussianState, QuantumOpticsRepr(cutoff = 10)) and return a QuantumOptics Ket object with FockBasis(10).

@apkille apkille added the enhancement New feature or request label Dec 22, 2024
@Krastanov
Copy link
Member

I am in favor of this.

QuantumClifford already has an extension that converts some objects to QuantumOptics objects, but those are unambiguous and do not need configuration like cutoff=10. For the more general objects you are describing, this seems like the appropriate way to proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants