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

Naming for API calls/interface parts #5

Open
crazy4pi314 opened this issue Jun 3, 2020 · 2 comments
Open

Naming for API calls/interface parts #5

crazy4pi314 opened this issue Jun 3, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@crazy4pi314
Copy link
Contributor

I am starting this because of @glassnotes's comment on #3 that we could call the QRAM type that a user can call to access the ram a 'LooqUpTable / LooqUpBit, or just the general qROM.'

@crazy4pi314
Copy link
Contributor Author

Also moving some notes from the source files here:

 BB has a register of hardware qubits - need to know which of those are
 set to 1; easiest way to do that is to send a string like "0011" to indicate that
 this register is in the state

 |0> ------   (qubit 0, address 00)
 |0> ------   (qubit 1, address 01)
 |1> ------   (qubit 2, address 10)
 |1> ------   (qubit 3, address 11)

 This is a 2-bit address; so QRAM(00) = 0, QRAM(01) = 0, QRAM(10) = 1, QRAM(11) = 1

The black box has to perform this operation ^^ given the inputs, based on the contents
 of the hardware register it starts with

@crazy4pi314
Copy link
Contributor Author

This has come a long way, we will eventually add an explicit API document in the docs for the library to address this.

@crazy4pi314 crazy4pi314 added the documentation Improvements or additions to documentation label Jul 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant