Lars Kasper

Dear Emily, Thank you for using the PhysIO Toolbox. In order to see the heart rate outputs, you would have to specify HRV as a model to include in your...

Dear @poeplau, Thank you for your contribution. In order to understand it better, would you be willing to share an example dataset and the script/SPM job you used to process...

Dear Stepan, Thank you for trying out PhysIO. Unfortunately, we have never tested compatibility with Octave explicitly. I presume there might be some missing functions from Matlab Toolboxes (signal processing...

Dear Stepan, which version of PhysIO are you using (`tapas_physio_version`)? In the latest commit of `master`, `development` and `physio` branch here in the repository, it seems that the previous function...

Thank you for pointing this out, @alexisganesh ! We are aware of this issue and will fix it in the next release (coming up within a month!). It slipped through...

Dear Liz, Thank you for trying out PhysIO. Could you try to see what happens if you set the number of slices back to 84 (i.e., disregard the MB factor)?...

Dear Liz, My apologies for the delayed reply, please see my thoughts inline below: > Thanks for your quick response! When I set the slices to 84, the code works...

Dear Evelyne, My apologies for the delay in responding, conference season and now summer is upon us... I presume this is BrainProducts data? We are relying on Fieldtrip `ft_*` functions...

And I just realized that the BrainProducts reader might not be functional at the moment, please see this issue: https://github.com/translationalneuromodeling/tapas/issues/225 As I stated there, it would be great to have...

Dear Ru, This is weird, it seems as if the `sync.grad_direction` is not properly defined. Would you be able to go into `tapas_physio_create_scan_timing_from_gradients_philips.m`, set a breakpoint at line 164 and...