You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @pjmark-
I was using the nipet.lm.get_time_offset to get the time offset due to injection delay, but when I then incorporate that value in nipet.lm.dynamic_timings per the documentation, the frame timings remain unchanged. When I had a bit of a dig into the code, it also seems that the resulting frame timings are dependent if you pass it a 1-D list versus the 2-D 'def' list approach. Since this function is pretty straightfoward and doesn't require any of the actual PET data to run, I've produced a toy example below.
Also, with the 1-D list approach, would you expect there to be a first frame containing the data before the injection?
Hi @pjmark-
I was using the nipet.lm.get_time_offset to get the time offset due to injection delay, but when I then incorporate that value in nipet.lm.dynamic_timings per the documentation, the frame timings remain unchanged. When I had a bit of a dig into the code, it also seems that the resulting frame timings are dependent if you pass it a 1-D list versus the 2-D 'def' list approach. Since this function is pretty straightfoward and doesn't require any of the actual PET data to run, I've produced a toy example below.
Also, with the 1-D list approach, would you expect there to be a first frame containing the data before the injection?
The text was updated successfully, but these errors were encountered: