-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension of spatial.distance module #479
Extension of spatial.distance module #479
Conversation
- refactorization to scipy naming - restructuring of distance calculation logic - support for distance calculation of two different tensors with different splits - support for dtypes other than float32
Codecov Report
@@ Coverage Diff @@
## master #479 +/- ##
==========================================
+ Coverage 96.72% 96.76% +0.03%
==========================================
Files 60 60
Lines 12281 12562 +281
==========================================
+ Hits 11879 12155 +276
- Misses 402 407 +5
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks pretty good. needs a few small updates but good job!
heat/spatial/distance.py
Outdated
stat = MPI.Status() | ||
comm.handle.Probe(source=sender, tag=iter, status=stat) | ||
count = int(stat.Get_count(mpi_type) / f) | ||
moving = torch.zeros((count, f), dtype=torch_type) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
device argument
would it be possible to abstract the communications loop that you use in |
I don't know, in principle yes, but what would be the application. The key point here ist the calculation of metrics between chunks from X and Y. While this is easily substituted, it can already currently be modified by the function you pass as metric. |
Description
Issue/s resolved:
Addresses #475 amongst other changes
Changes proposed:
Type of change
Due Diligence
Does this change modify the behaviour of other functions? If so, which?
no