Skip to content
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

Display 3D trajectories, with a grid interface #193

Merged
merged 94 commits into from
Feb 24, 2025

Conversation

chaithyagr
Copy link
Member

No description provided.

chaithyagr and others added 30 commits April 26, 2024 14:45
This add "get_interpolators_from_fieldmap", supporting both real (B0 map only) and complex (Zmap = R2* + 1j * B0map) fields
in arbitrary dimension (2D and 3D). The routine supports both numpy / cupy arrays and torch tensors on CPU and GPU,
the latter requiring cupy due to limitations in torch.histogram / torch.histogramdd (pytorch/pytorch#69519).

Calculation uses time segmentation with uniform time samples and LS coefficients (using histogram).

Based on MIRT (https://github.com/JeffFessler/mirt/blob/main/mri/mri_exp_approx.m)
and its Python porting from MIRTORCH (https://github.com/guanhuaw/MIRTorch/blob/master/mirtorch/linear/mri.py)
and SigPy (https://github.com/mikgroup/sigpy/blob/main/sigpy/mri/util.py).
Avoid torch cuda test case if cupy is not available.
remove deprecated get_grad

Co-authored-by: Chaithya G R <[email protected]>
@chaithyagr
Copy link
Member Author

test

1 similar comment
@chaithyagr
Copy link
Member Author

test

@chaithyagr
Copy link
Member Author

test

@chaithyagr
Copy link
Member Author

@Daval-G I think we can merge if you are happy... I seemed to have tagged a random person in my commit :P

Copy link
Collaborator

@Daval-G Daval-G left a comment

Choose a reason for hiding this comment

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

Approved with still a few small comments to take into account, I trust that you can handle them without further review.

A few quick questions:

  • The documentation wasn't generated in the latest commits, is it normal ?
  • Is it a common practice to use commit messages as regular messages/comments and ping people in them ? (particularly strangers xD) Maybe let's stick to github comments

Also please read also the previous comments that are still open

Comment on lines 2 to 4
======================
3D Trajectory display
======================
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please don't mark general comments as resolved as an assignee, it's difficult for reviewers if they have to look into each solved comment just to be sure it was really solved or simply to read the assignee's answer

[docs] final updates

Co-authored-by: Guillaume Daval-Frérot <[email protected]>
@chaithyagr
Copy link
Member Author

The documentation wasn't generated in the latest commits, is it normal ?

Yes, docs is built only if we add [docs] in the commit header.

Is it a common practice to use commit messages as regular messages/comments and ping people in them ? (particularly strangers xD) Maybe let's stick to github comments

Its not common, I tried it, but it seems like its a bad idea

@chaithyagr chaithyagr merged commit b91a706 into mind-inria:master Feb 24, 2025
12 checks passed
@chaithyagr chaithyagr deleted the display_dens branch February 24, 2025 07:52
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.

Add trajectory plotting functions from SPARKLING
4 participants