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.

Sign up for GitHub

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

Jump to bottom

Easily define Phantom motion field composed by only one Motion instance #481

Closed
pvillacorta opened this issue Sep 19, 2024 · 0 comments · Fixed by #517
Closed

Easily define Phantom motion field composed by only one Motion instance #481

pvillacorta opened this issue Sep 19, 2024 · 0 comments · Fixed by #517

Comments

@pvillacorta
Copy link
Collaborator

pvillacorta commented Sep 19, 2024 •
edited
Loading

This will be achieved by:

struct Phantom
   ...
   motion::Union{NoMotion, Motion, MotionList}
   ...
end

and, in the future (#480 ):

struct Phantom
   ...
   motion::Union{NoMotion, Vector{Motion}}
   ...
end
@pvillacorta pvillacorta changed the title Easily define MotionLists composed by only one Motion Easily define Phantom motion field composed by only one Motion instance Dec 5, 2024
@pvillacorta pvillacorta mentioned this issue Dec 5, 2024
Merged
@pvillacorta pvillacorta linked a pull request Dec 8, 2024 that will close this issue
Ease motion definition when only one motion is needed #517
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ease motion definition when only one motion is needed JuliaHealth/KomaMRI.jl
1 participant
@pvillacorta