Stable 0.4.12 #394
Merged
Stable 0.4.12 #394
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Support for non-string identifiers
I spent too much time trying this:
qp.create_quantum_registers([{"quantum_registers":
[ {"name": "qr", "size": 4} ]
}])
unify format of the docstrings and general format
fixes Qiskit#290
create_program_with_specsnonames
create_anonymous_classical_register
create_anonymous_quantum_register
create_classical_registers_noname
create_quantum_registers_noname
create_circuit_noname
get_register_and_circuit_names_nonames
get_qasm
get_qasms
reasonable defaults
get_qasms_noname
get_execution_list_noname
change_circuit_qobj_after_compile_noname
add_circuit_noname
old QPS_SPECS gone
convert the names to openqasm names when thats needed
names can be ints
tuples as id are also supported
lint and style
debugging appveyor
Hash randomization causes the iteration order of dicts and sets to be unpredictable and differ across Python runs
typ0!!!
I forgot how to math
checks about 0 and emtpy strings as identifiers
better using id instead of hash
lenght of the output considers short ids
cleaning up
self.oq_name -> self._openqasm_name
get_single_name
quantumcircuit name is set at new-time, not after
test adjusted
name arg
counter to track automatic identifiers
docstring and format
openqasm_name as a property
assertEqual -> assertCountEqual
* Fixes for support of non-string identifiers
* Tweak docstrings and exception messages when using non-string
identifiers, for clarity towards the end user and for correctly
indicating that the functions can use hashables.
* Revise `get_single_name()`, renaming it and documenting in a more
general way and making it privat-ish.
* Revise `create_id()`, using strings directly as parameter rather than
format strings, to avoid a potential source of errors.
* Explicitly check that `add_circuit()` receives a valid
`quantum_circuit`, preserving the previous behaviour. Note that this
implies that the attribute is not really optional (even if declared
optional by the signature).
* Added reference to unroll package from qasm. * Added code example to DAGBackend.
* Bump `IBMQuantumExperience` dependency to 1.8.29, as it fixes a bug and will be required by the next sdk release. * Fix the `_check_ibmqe_version()`, as after Qiskit#286 there where cases where the `requirement.txt` file was not present, resulting in the wrong warning. Now uses a simple approach: the check is only performed if installed via pip, assuming in the rest of the cases the user is responsible for updating the dependencies (ie. `pip install -U`). * Revise `_AssertNoLogsContext` in order to produce more informative failure messages.
* Do Python version check in init This does the Python version check in a similar manner as NumPy and SciPy equivilent checks. * Fix pylint issues * Pylint 10/10
* no name in the registers means no name :-/ * _create_id: returns infix if available as a name * kinda rolling back * missing-raises-doc * missing-raises-doc
Adding myself as author.
* get_qubits return in order * added test to reproduce emoticon mapping issue * test mapping of already-conforming circuits * test gate after measure in quantumprogram
* sympy added & tested * learn backedn added * sympy backend 1 * fix the counts * pdate * two backends added: _sympy_qasmsimulator.py and _sympy_unitarysimulator.py * two backends added: _sympy_qasmsimulator.py and _sympy_unitarysimulator.py * one more initializer test case * updating version requirement for IBMQuantumExperience * fixing per diego's comments * measure disabled * measure disabled * header notes added * test cases added to examples/ * pylint errors partially fixed * pylint errors partially fixed * pylint errors partially fixed * pylint errors partially fixed * lint errors fixed * style errors fixed * fix style/lint errors in use_sympy_backends * minor style problem fixed * import u * import u error * fix comments in PR * deleted new line in _quantumprogram.py * clean up docstrings, imports. * lint * fix github url * fix magic * document for each method added * doc fixed * fix error * minimal test added * lint for tests fixed * lint fixed * Fix linting and styling, tests * sympy.sympify * update * Refactor regulate() for sympy simulators Move `regulate()` and `compute_ugate_matrix()` from the individual sympy simulators to `_simulatortools.py`, in order to avoid duplication. Refactor `regulate()` in order to always return a single item with the same type, reducing the complexity of `compute_ugate_matrix` as a result. * remove print * info msg should not start with warning * both tests covered exactly the same amount of lines. So, removing one
Bump API version, fix check, _AssertNoLogsContext
* fix style error in qiskit init file * update test_util.py
* removed relative import warning from examples * Cleaner examples
* Fix the travis stage that performs the linting, making it fail if the `make style` target fails instead of ignoring it silently. * Fix the execution of the deploy stages for the jobs that are the result of a PR against stable. Now the stages are only executed in the job associated to the push.
Revise the cmake QA-related targets, making them optional by default and emitting warnings instead of errors if the dependencies are not present.
Travis and cmake improvements
* Reorganize the contributors information Revise the authors section in the README and in the main document for the Sphinx documentation, moving the full list of contributors to a separate document. * small typo
* Resolves Qiskit#262: add qiskit.backend methods... for getting parameter, calibration, and status. * linting quantumprogram * Update _backendutils.py * Update _backendutils.py * Update _basebackend.py * Update _qeremote.py * Update _basebackend.py * Update _quantumprogram.py * Update _qeremote.py * Warning, updates to test, and backencs 1. Added to the quantum program warnings — may of done this incorrect 2. Removed old versions 3. In the configuration we lost the rewrite of the mapping. I agree we want to update the API but first we need the backend configuration to work 4. Made the test use quantum program Still to be done — check why failing some test — add some test to backend that test the test_basebackends that test new methods * Fixing some spelling and linting * Spelling fixes * Lint and spelling * Linter fixes and some spelling in backendutils * Cleaning up the coupling_map @ewinston we decided that all new code should use the new map and all old code the older one. I have remove the complicated identity map we inserted :-) * Renaming configuration as config to fix scope error * Linting in test * Linting more * Fixing the vqe * More linting * Update test_quantumprogram.py * lint errors I found trying to debug the error * Removing backend from quantum_program test * Making the backend object based * Adding tests for the backend object * Linting tests * Spelling and linting * Removing some set_api that are not needed * set log level to debug * Removing the api from the tests and needed by the program * Cleaning up and adding a discover * correct travis.yml env variable specification * Removing more old code * Updated lengths with rename of q_name and c_name * Lint errors found from travis fixed * Moving import order to help travis linter * Revise DeprecationWarnings, add note to docstrings Add a context manager for ensuring the DeprecationWarnings are shown regardless of the user configuration, as by default they are hidden for end users (ie. when not on an interpreter). Revise the strings for the warnings and add entries to the docstrings for visually showing them on the online docs. * Enable deprecation warnings during __init__ Enable the display of deprecation warnings during qiskit.__init__ instead of via a context manager, for simplifying the deprecated calls and help providing visual aids for the editors. * fix cyclic import and scope of configuration These were pylint warnings. The configuration one was due to having a function of of the same name as a parameter in _backendutils.py. * fix linter * remove converting coupling_map to dict * minor lint fix * Small fix to the backends. * Fix LookupErrors, style, comments Fix several backendutils methods raising ConnectionError instead of LookupError when the entities were not found. Update the structure of those methods for simplicity and consistency. Fix commented out code on tests.
Remove intermediate QASM transforms: * New DagUnrolled created for dealing with unrolling from a DagCircuit instead of a QASM AST * JSON functionallity added to DagUnroller * expand_gates() method added to DagUnroller * Created a new static method for constructring a DagCircuit from a QuantumCircuit * default initializer name to init * updating initializer example to use default name * update qiskit_simulator extension. * Removed deepcopy() in two places to greatly improve performance. * Switched asserts to exceptions * Removed superfluous prints * Some minor refactoring to improve readability * Created tests for the DagUnroller * Removing some random behavior by switching normal dictionaries to OrderedDicts. * Fixing tests, linter and style. Some tests needed to be disabled for Python 3.5 due to inconsistencies with the use of dictionaries as ordered dictionaries.
Temporarily disable the osx build on Travis, as they are having a backlog that might take some time to recover: https://www.traviscistatus.com/incidents/qkqy13yk55q9
* Fix for the quantum program with new backends * Fixing the tests * Small changes * Linting * Update tests using coupling_map as list, add test Update the test in order to specify the coupling_maps as lists, due to recent changes. Add a `test_compile_coupling_map_as_dict` that still uses the dict format, for backwards compatibility during the deprecation. * Update coupling_map as list related docstrings Along with other fixes to docstrings and tests. * Disable travis osx build temporarily (Qiskit#374) Temporarily disable the osx build on Travis, as they are having a backlog that might take some time to recover: https://www.traviscistatus.com/incidents/qkqy13yk55q9 * adding a missing coupling in test_quantumprogram
* improved circuit visualization, testing, & consistent gate definitions * default method args. don't keep tex files around from test.
* fixing projectq test * lint
Fix the `test_api_ibmq.py` tests: * adjust them to the new style for using the API directly instead of going through QuantumProgram. * revise tests that were failing due to assertions no longer valid, and relaxed the assertions in a couple of cases. * remove the test for updating the hub parameters on the fly, as it is rendered deprecated if using the API directly. Add an extra check to `QuantumProgram.set_api()`, as users using a Qconfig where the hub parameters were set, but with the value `None` might have encountered problems.
Updated tests that compare random counts outcomes
* Update example and authors in README translations * Fix QuantumProgram docstrings for sphinx
use assertDictAlmostEqual in test_mapper
* modify circuit addition rules to allow combining circuits with different but unique registers * fixed bug in extend circuit, added unit tests for extend
diego-plan9
approved these changes
Apr 11, 2018
lia-approves
pushed a commit
to edasgupta/qiskit-terra
that referenced
this pull request
Jul 30, 2019
Stable 0.4.12
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.