-
Notifications
You must be signed in to change notification settings - Fork 209
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
General Driver Updates #166
Comments
With #173 nearing its merging and #180 following suite shortly after, two major (and the most important) steps of this issue will be addressed soon. None of the other drivers are technically high priority right now because none of them immediately block other implementations planned in the near future. |
As part of migrating the new drivers to the property framework (#264) I have checked each open driver for an estimated amount of time required to refactor it. I will summarize below:
The migration of the remaining drivers will likely not be part of the |
A quick update on this epic:
The goal will be to refactor all drivers thereby decoupling the need for the legacy driver results from all but the |
I am moving this epic back to product backlog until we have completed the hdf5 and the rest of the drivers updates. |
What is the expected enhancement?
#147 also suggest some general improvements to the drivers. The implementation of these is tracked by this issue:
qiskit_nature.drivers.*
intoqiskit_nature.drivers.second_quantization.*
qiskit_nature.transformers.*
intoqiskit_nature.transformers.second_quantization.*
fcidumpd
hdf5d
pyscfd
pyquanted
psi4d
gaussiand
While performing the checks for general improvments we should also check for the ability of the driver to perform more input validation and update the documentation of all methods.
The text was updated successfully, but these errors were encountered: