Closed AlexDo1 closed 2 years ago
Merging #171 (38494b4) into master (3c547d4) will decrease coverage by
0.01%
. The diff coverage is33.33%
.
@@ Coverage Diff @@
## master #171 +/- ##
==========================================
- Coverage 63.58% 63.57% -0.02%
==========================================
Files 67 67
Lines 3095 3105 +10
==========================================
+ Hits 1968 1974 +6
- Misses 1127 1131 +4
Flag | Coverage Δ | |
---|---|---|
e2e | 63.57% <33.33%> (-0.02%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
metacatalog/util/results.py | 80.24% <33.33%> (-1.34%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 3c547d4...38494b4. Read the comment docs.
The latest commit uses the 'old' pd.merge()
function for Composites
and pd.concat
for Split datasets
now.
Composite: Eddy data:
Split dataset: LUBW gauge data:
That looks way better now, thanks a lot! Is there an easy way to add a unit-test for the changed behavior? If yes, that would be cool, if not, never mind and merge.
I think you tested most of the merging behavior of Split datasets
here:
https://github.com/VForWaTer/metacatalog/blob/3c547d4ab06178a41c347bc23afd1cf5dfa17f22/metacatalog/test/test_array_type_data.py#L246-L280
I just copied most of that test for a second test with a Composite dataset
and tested for the shape of the merged data.
I guess we could test for more stuff here, I just focused on the merging behavior.
@mmaelicke From our conversation above, I understand that the tests are not perfect, but we should still be able to merge the PR since the results look good.
It's not so easy to continue a discussion after 10 months :) But I agree, it should be fine to merge.
Always merge Split datasets additionally.
The default parameters of pd.concat() should fit our use case.