-
Notifications
You must be signed in to change notification settings - Fork 21
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
Interpretation of '.seq' files is not matching with sequence designed on PyPulseq #320
Comments
Hi! Thanks for using Koma 😄! This issue is related to #205. While it looks weird, it is more of a plotting bug, as it has no impact on the simulations. The worst thing that it could do is to add a sample with amplitud 0 and duration 0 to the simulation, which has no effect. Having said that, I don't think it is a hard one to solve. Could you provide this pulseq file to do some tests? In the meantime, we have tools to check what is actually being simulated. Take a look at the results of Cheers! |
I believe we found a case where this could affect the simulation, opened #321 to fix it. |
`ERROR: MethodError: no method matching discretize(::Sequence; sim_params::Dict{String, Any}) Closest candidates are: |
Hi @ZemaTimoteo! Can you please update your KomaMRI version? That is why you see |
Hi, to give an update on this. What we were doing differently. We hadn't added the heuristic that Pulseq uses for the first and last samples (more info here #321 (comment)). It is an easy fix and should be solved this week. |
This has been solved in the current dev version of Koma (master). In some cases, the KomaMRI.jl/KomaMRIFiles/test/runtests.jl Lines 53 to 82 in 3d7e92d
Please let us know if you encounter any other issues! |
What happened?
First, thank you for your nice repository, I found it very useful.
However, I am struggling with an issue regarding the interpretation of '.seq' files. Apparently, KomaMRI interpretates each block of gradient built in PyPulseq, with the need to start and finish at 0.
Here are the full concatenated blocks I want to perform in the simulations. However, as you can see they have unexpected behavior of going to zero between each block of gradients design in the Pypulseq.
Here are an example of block 1 and 2 for Gz:
Block 1 - Koma
Block 1 - Pulseq
Block 2 - Koma
Block 1:2 - Koma
Block 1:2 - Pulseq
I feel like this shouldn't be the case, as I need to simulate the '.seq' and don't want to edit it in the Koma environment as it would make it a different sequence from the one I will design for further scanning.
Should I do something different, or is this something that needs to be update?
Best
ZemaTimoteo
Environment
The text was updated successfully, but these errors were encountered: