Before the release of v0.3, there are a few confusing names and function locations that should be addressed, such as:
[x] Better name for VQHCore.strategy_name, since it has information on the problem, protocol, process and algorithm used. can lead to confusion. Maybe strategy_factory?
[x] We have VQHSourceStrategy, which is an abstract Protocol Class. However, VQHFileStrategy is an implementation, together with VQHProcess. These names are confusing.
[x] On that same note, maybe strategy in VQHSourceStrategy should not be used in this case. Maybe VQHSourceMode is better here?
[x] qubo_algo -> qubo
[x] A long requested change from harp to basis protocol name should be made.
[x] SonificationInterface or VQHMappingStrategy? How about VQHMappingInterface? See #7
[x] The code in abstract_classes.py could be moved to a new file, core/vqh_interfaces.py, containg both QuantumHardwareInterface and SonificationInterface.
[x] On a different direction the subclasses of SonificationInterface could be renamed from FooMapping to FooInterface.
[ ] Again, same problem with the name VQHMapper.strategy, depending on the items above.
[ ] Rename the new AmplituteProtocol to OneHotProtocol, the new BasisProtocol to AmplitudeProtocol (see #13 )
[x] QuboProblem and QUBOProblemRT. Only one survives.
[x] The old CLI flags also have completely different names now.
Before the release of v0.3, there are a few confusing names and function locations that should be addressed, such as:
VQHCore.strategy_name, since it has information on the problem, protocol, process and algorithm used. can lead to confusion. Maybestrategy_factory?VQHSourceStrategy, which is an abstract Protocol Class. However,VQHFileStrategyis an implementation, together withVQHProcess. These names are confusing.VQHSourceStrategyshould not be used in this case. MaybeVQHSourceModeis better here?qubo_algo->quboharptobasisprotocol name should be made.abstract_classes.pycould be moved to a new file,core/vqh_interfaces.py, containg both QuantumHardwareInterface and SonificationInterface.FooMappingtoFooInterface.VQHMapper.strategy, depending on the items above.AmplituteProtocoltoOneHotProtocol, the newBasisProtocoltoAmplitudeProtocol(see #13 )