-
Notifications
You must be signed in to change notification settings - Fork 4
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
fs paramater specification causing problem in load_physio #10
Comments
@smoia wdyt ? |
I didn't have a look at the code yet, is it possible that passing arguments more carefully will solve the problem? Also, yes, fs should be in a 'phys' file, but they should also be in the json file in BIDS format, and I don't remember us supporting anything else than that? Worth adding a check in the affected function rather than duplicating code, but maybe you have another solution in mind I'm not 100% understanding. |
Should we then constrain the possible file extension here to only |
Ah I see. Then yes, please separate the
You can also use reading functions form phys2bids on top of that! |
Thank you for that block of code, will integrate that ! |
Expected Behavior
In the
generate_physio
function, whenload_physio
is called, it uses thefs
specified in the parameters ofgenerate_physio
. However, for '.phys' files, this causes problem since thefs
information can be retrieved from the file directly. So havingfs=None
(default value) lead to afs
value ofNOTHING
(enum type) after loading the file...See also discussion here.
Actual Behavior
Steps to Reproduce the Problem
Specifications
Possible solution
Since the
fs
parameters should still be specified if loading any file format that is not.phys
, I would propose to create another mode to separate those different format rather than grouping everything undermode="physio"
The text was updated successfully, but these errors were encountered: