46 allow data partitioning for parallel processing by antenna or antenna#48
Conversation
…node_task_data_mapping. Also added an example ipynb.
|
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Pull request overview
This pull request adds support for string coordinate mapping in the node_task_data_mapping functionality, enabling parallel processing by antenna names or similar string-based dimensions. The key change implements exact string matching for coordinates with string data types (like antenna names), while maintaining numeric interpolation for traditional numeric coordinates.
Key Changes:
- Added string coordinate handling in
interpolate_data_coords_onto_parallel_coordswith exact matching logic - Added tutorial notebook
sd_tutorial.ipynbdemonstrating antenna-based partitioning - Updated version reference in
graph_building_tutorial_image.ipynb
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
src/graphviper/graph_tools/coordinate_utils.py |
Added string coordinate detection and exact matching interpolator alongside existing numeric interpolation |
docs/sd_tutorial.ipynb |
New tutorial demonstrating parallel processing partitioned by antenna names |
docs/graph_building_tutorial_image.ipynb |
Version bump and timestamp updates from re-execution |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Thanks @Jan-Willem for the fix. I have tested with my dataset and confirmed that partitioning by antenna name works. It produced a dictionary consistent with manually created one. I have approved the change. |
@tnakazato I have added support to node_task_data_mapping so that string mapping can be done. Only exact matching is performed. I have also added an example docs/sd_tutorial.ipynb.