Skip to content

Conversation

@egouden
Copy link
Contributor

@egouden egouden commented Oct 1, 2025

No description provided.

@codecov
Copy link

codecov bot commented Oct 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.54%. Comparing base (c843798) to head (d53c73b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #306      +/-   ##
==========================================
+ Coverage   93.50%   93.54%   +0.04%     
==========================================
  Files          27       27              
  Lines        5555     5580      +25     
==========================================
+ Hits         5194     5220      +26     
+ Misses        361      360       -1     
Flag Coverage Δ
notebooktests 0.00% <0.00%> (ø)
unittests 93.54% <100.00%> (+0.04%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@kmuehlbauer kmuehlbauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good to me. Would be great, if we also can work with simple Dataset objects instead of DataTree.

Sweeps are sorted by their start time to ensure temporal consistency.
Parameters:
volumes: List of DataTree objects, each representing a radar volume or a single scan.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it make sense to make this work for multiple sweep Dataset objects, too?

Use case would be single sweeps opened by xr.open_dataset.

Should be possible when looking at the code, but nor sure how much involved that would be.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is open_dataset not always returning a DataTree with mandatory global variables?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it opens a Dataset, not a DataTree. If we want to get back a DataTree we would have to use open_datatree, but that's not implemented in the xradar backends AFAICT. We currently only have a dedicated open_"backend"_datatree function.

The issue is that our DataTree implementation was made before DataTree was finally introduced into xarray codebase.

@egouden
Copy link
Contributor Author

egouden commented Oct 2, 2025

It is not clear to me how you can retrieve the global metadata from the sweep datasets. The DataTree seems to be the natural object for implementing FM301.

The approach has been refined in #307 with some extra motivation.

@egouden egouden closed this Oct 2, 2025
@egouden egouden deleted the stack_volumes branch October 4, 2025 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants