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

Now we use Cirq backend #77

Open
nakatamaho opened this issue Feb 12, 2022 · 0 comments · May be fixed by #83
Open

Now we use Cirq backend #77

nakatamaho opened this issue Feb 12, 2022 · 0 comments · May be fixed by #83
Labels
enhancement New feature or request

Comments

@nakatamaho
Copy link
Collaborator

We should better use the Cirq as the backend. Consequently, some files are renamed and classes may be modified.

There are at least two advantages to using it instead of direct use of libcustatevec: (i) better programmability since the Cirq is a high level of quantum circuit language and libcustatevec is low level library. (ii) CPU optimization, as well as GPU optimization using libcustatevec, is available for the Cirq.

The following files may be renamed to cirq_bridge or something else.
$ find . -name "cu_q"
./apps/www/lib/cu_quantum.rb
./apps/www/app/controllers/cu_quantum_controller.rb
./apps/www/app/views/cu_quantum
./apps/www/test/controllers/cu_quantum_controller_test.rb

especially, there is a class named CuQuantum in ./apps/www/lib/cu_quantum.rb,
class CuQuantum
and this should also be renamed.

Direct use of libcustatevec will be done in the future when we find very serious problems using Cirq.
Best,
Nakata Maho

@yasuhito yasuhito added the enhancement New feature or request label Feb 12, 2022
@yasuhito yasuhito self-assigned this Feb 12, 2022
yasuhito added a commit that referenced this issue Feb 12, 2022
@yasuhito yasuhito linked a pull request Feb 14, 2022 that will close this issue
@yasuhito yasuhito removed their assignment Apr 25, 2022
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

Successfully merging a pull request may close this issue.

2 participants