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

QuantumImplementation and ClassicImplementation empty #197

Open
salmma opened this issue Aug 17, 2021 · 2 comments
Open

QuantumImplementation and ClassicImplementation empty #197

salmma opened this issue Aug 17, 2021 · 2 comments
Labels
ask S1 This requires discussion with StoneOne invalid This doesn't seem right question Further information is requested

Comments

@salmma
Copy link
Contributor

salmma commented Aug 17, 2021

when adding an implementation (classical or quantum) it is only stored in the implementation table neither in the quantum_implementation nor in the classic_implementation table.

Should the specific tables be removed?

@salmma salmma added the question Further information is requested label Aug 17, 2021
@salmma
Copy link
Contributor Author

salmma commented Aug 18, 2021

How should be decided whether an implementation is quantum (, hybrid) or classic?
I assume based on the computationModel of the implementedAlgortihm

@salmma salmma added the invalid This doesn't seem right label Aug 18, 2021
@salmma
Copy link
Contributor Author

salmma commented Aug 18, 2021

** Should be discussed with StoneOne!**

@salmma salmma added the ask S1 This requires discussion with StoneOne label Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ask S1 This requires discussion with StoneOne invalid This doesn't seem right question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant