Skip to content

Conversation

@SouthEndMusic
Copy link
Contributor

See corresponding PR at DataInterpolations here. I added a comment there about whether the information that SparseConnectivityTracer needs for the different interpolation types should live in DataInterpolations

@SouthEndMusic SouthEndMusic marked this pull request as draft July 10, 2025 14:48
@codecov-commenter
Copy link

codecov-commenter commented Jul 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.57%. Comparing base (577de61) to head (a7618fc).

❗ There is a different number of reports uploaded between BASE (577de61) and HEAD (a7618fc). Click for more details.

HEAD has 10 uploads less than BASE
Flag BASE (577de61) HEAD (a7618fc)
12 2
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #252       +/-   ##
===========================================
- Coverage   92.53%   58.57%   -33.96%     
===========================================
  Files          30       30               
  Lines        1246     1183       -63     
===========================================
- Hits         1153      693      -460     
- Misses         93      490      +397     

☔ 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.

@adrhill
Copy link
Owner

adrhill commented Jul 11, 2025

If you don't mind, it would be better for the DI extension to live in DI at this point.
SCT v0.7.0 is coming up in #254 and would be a nice occasion for the move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants