Extend and unify libraries
Is your feature request related to a problem? Please describe
Describe the solution you'd like Chip components should become a library with a more general name, e.g. quantum_elements, physical_elements, physical_components. Tasks should also become two libraries: readout and initialization. Devices can also become a library.
All elements of libraries should follow a single implementation, i.e. all be initialized and declared the same way (see issue #21). All elements of libraries provided should be covered by a very basic test.
Describe alternatives you've considered
Additional context Only elements of general interest should stay in libraries, all elements specific to a single use case should be added in local environment after import.
Only elements of general interest should stay in libraries
I agree there should be local and general libraries.
However, I think the idea of a very large general library, slowly accumulating over time, that is part of the public release, is a positive: Such a library also serves as a collection of examples, which uses can use as a starting point for their unique components.
On Tue, 26 Jan 2021, 17:20 Federico Roy, [email protected] wrote:
Chip components should become a library with a more general name, e.g. quantum_elements, physical_elements, physical_components. Tasks should also become two libraries: readout and initialization. Devices can also become a library.
All elements of libraries should follow a single implementation, i.e. all be initialized and declared the same way (see issue #21 https://github.com/q-optimize/c3/issues/21). All elements of libraries provided should be covered by a very basic test.
Only elements of general interest should stay in libraries, all elements specific to a single use case should be added in local environment after import.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/q-optimize/c3/issues/22, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH3Q4ICS36RDRFXKZ5VGQLS33MUNANCNFSM4WTT4VOQ .
Related: #93 and #99