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

Correctly validating that AER and IBMQ support the methods and field types for every device and simulator #996

Closed
5 of 10 tasks
jaygambetta opened this issue Oct 1, 2018 · 1 comment
Assignees
Labels
type: enhancement It's working, but needs polishing
Milestone

Comments

@jaygambetta
Copy link
Member

jaygambetta commented Oct 1, 2018

What is the expected behavior?

This is related to #1047 but the difference is I want to have a way that I can easily see that the provider is a valid provider for terra.

The idea is that it should return data that passes the schemas

Then I think terra needs to have some way to be sure that it is making a qobj that passes the schema

  • qobj_schema.json

Then inside the IBMQ provider, we should have something that confirms that qobj from terra will work

  • ibmq_device_qobj_schema.json
  • ibmq_simulator_qobj_schema.json

Then we need something in the AER that does the same

  • Aer_qobj_schema.json
@delapuente delapuente added the type: enhancement It's working, but needs polishing label Oct 2, 2018
@jaygambetta jaygambetta changed the title Update all the backends for using the QObj and Result classes and schemas (every device) Correctly validating that AER and IBMQ support the methods and field types for every device and simulator Oct 16, 2018
@diego-plan9 diego-plan9 added this to the 0.7 milestone Oct 31, 2018
@ajavadia
Copy link
Member

ajavadia commented Dec 4, 2018

Closing, only Qobj models left and let's track in a separate issue. @diego-plan9

@ajavadia ajavadia closed this as completed Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement It's working, but needs polishing
Projects
None yet
Development

No branches or pull requests

4 participants