Closed apchytr closed 2 months ago
Attention: Patch coverage is 99.14530%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 89.60%. Comparing base (
06c000b
) to head (adff94a
). Report is 1 commits behind head on develop.
Files with missing lines | Patch % | Lines |
---|---|---|
mrmustard/physics/ansatze.py | 98.95% | 1 Missing :warning: |
looks good! I'm asking this more for personal clarification than anything else: what value do we gain from this separation of representations and ansatze? Is it in anticipation for future things? I'm wondering this because I see that this separation is the reason you lowered the _original
data to the ansatz itself.
looks good! I'm asking this more for personal clarification than anything else: what value do we gain from this separation of representations and ansatze? Is it in anticipation for future things? I'm wondering this because I see that this separation is the reason you lowered the
_original
data to the ansatz itself.
So I think the original design was that we would have different types of ansatz but I believe as we continue to develop lab_dev its becoming more and more evident that this separation is unnecessary. The only thing I could think of is that maybe codefactor will give us issues if we merge the two.
Context: currently on develop
to_bargmann
is not checking if original bargmann data exists leading to issues such asrunning out of memory.
Description of the Change:
to_bargmann
now checks for original bargmann data. Removed a single line that hasoriginal_fock_data
as that is not used anywhere. Moved some things to ansatz.__truediv__
and__mul__
can update the original bargmann data as long as other is a scalar._original_bargmann_data
is renamed to_original_abc_data
. SomeRepresentation
cleanup removing duplicate code.