KomaMRI.jl: An open-source framework for general MRI simulations with GPU acceleration

KomaMRI v0.9.1

Diff since v0.9.0

Motion-Related Features and Bug fixes These updates primarily affect KomaMRIBase. Key changes include:

• Bug fixes related to phantom definition, motion lists, and flow experiments (PR #499, #511, #516, #520, #536).
• Improved motion definition, allowing for easier specification of single motion instances and flexible time spans (PR #517, #531).
• Introduction of the TimeCurve structure, enabling arbitrary temporal motion patterns that were previously challenging to replicate (PR #531).
• Added tests for motion-related functions to improve code coverage (PR #523). Other Minor Changes
• Updated and expanded documentation for contributors to Koma, providing clearer guidelines and resources (PR #509, #510, #514, #518, #543).
• KomaMRIPlots: Standardized colormaps using QMRIColors.jl for T1 and T2 maps (PR #528).
• KomaMRICore: Removed "hack" of using cos + i sin as oneAPI.jl didn't defined cis(x) . Now we use sincos for GPU kernel code (PR #496).

Merged pull requests:

• Update README.md with v0.9 news (#493) (@calberolalopez)
• Update to use cis instead of cos + i sin (#496) (@cncastillo)
• CompatHelper: bump compat for PlutoPlotly in [weakdeps] to 0.6 for package KomaMRIPlots, (keep existing compat) (#497) (@github-actions[bot])
• Fix Phantom-related bugs (#498 and more) (#499) (@pvillacorta)
• Avoid GPU runners for CPU jobs, and fix hanging CPU tests (#502) (@cncastillo)
• CompatHelper: bump compat for Functors to 0.5 for package KomaMRICore, (keep existing compat) (#507) (@github-actions[bot])
• How to contribute to Koma docs (#509) (@Stockless)
• Fixing text some details in dev documentation (#510) (@Stockless)
• Adjust reset flag interpolation to trigger at jump (#511) (@pvillacorta)
• Bump codecov/codecov-action from 4 to 5 (#513) (@dependabot[bot])
• Fix asset paths for "5-contribute-to-koma.md" (#514) (@Stockless)
• Fixed incorrect assets path (#515) (@Stockless)
• Fix flow-related functions (#516) (@pvillacorta)
• Ease motion definition when only one motion is needed (#517) (@pvillacorta)
• Limited size of large assets in light mode (#518) (@Stockless)
• Solve bug in SpinRanges when indexing a phantom with a BitVector (#520) (@pvillacorta)
• Test motion-related functions (#523) (@pvillacorta)
• Limit 'NadcsPerImage' to be at least 1 (#527) (@Stockless)
• Adding standard T1 and T2 colormaps from QMRIColors.jl (#528) (@Stockless)
• Flexibilize the definition of motion time spans (#531) (@pvillacorta)
• Fix motion bugs and add colorscale keyword in plot_image (#536) (@pvillacorta)
• Resize contributors (#541) (@Stockless)
• Contributing guidelines update (#543) (@Stockless)
• replace all "cmin" and "cmax" with "zmin" and "zmax" respectibly (#546) (@Stockless)
• bump v0.9.0 to v0.9.1 (#547) (@Stockless)

Closed issues:

• Add Contributing Guidelines (#209)
• Include steps for contributing using VSCode (#233)
• An error of 'DivideError: integer division' occurs in the internal functions of simulate when using a sequence with spiral acquisition (#409)
• Test setting fields from a Phantom @view (#412)
• Future: use sincos once available in oneAPI.jl (#463)
• Use color-map recommendations for MR relaxometry maps by Quantitative MR Study Group (#473)
• Easily define Phantom motion field composed by only one Motion instance (#481)
• Troubles defining Float32 or empty phantoms with KomaMRI 0.9 (#498)
• Don't run CPU benchmarks on GPU workers (#501)
• Test Motion constructors (#512)
• Test motion-related functions (#522)
• Resize collaborators (#525)