-
Notifications
You must be signed in to change notification settings - Fork 21
Add Parser #14
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
Add Parser #14
Conversation
|
Wait, we have to get rid of Travis. I'll open an issue. |
tsalo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I may be misunderstanding the required inputs for the workflow. I was under the impression that the workflow should be designed around BIDS-format data. If not, then only some of these comments will apply.
phys2denoise/cli/run.py
Outdated
| optional.add_argument('-os', '--oversampling', | ||
| dest='oversampling', | ||
| type=int, | ||
| help='Temporal oversampling factor in seconds. ' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the oversampling factor has a unit. It's just a scalar for the actual sample rate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just took that from the input descriptions in PR #4 but I have no idea
phys2denoise/cli/run.py
Outdated
| optional.add_argument('-tl', '--time-length', | ||
| dest='time_length', | ||
| type=int, | ||
| help='RRF Kernel length in seconds.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this apply to the CRF kernel as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, but as I said I based these inputs in PR #4
smoia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, a couple of changes here and there but there's no gain without pain, right?
phys2denoise/cli/run.py
Outdated
| help='Sampling rate for the output time series ' | ||
| 'in seconds. Corresponds to TR in fMRI data.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could rename the variable in the metrics that use this one
phys2denoise/cli/run.py
Outdated
| optional.add_argument('-slt', '--slice-timings', | ||
| dest='slice_timings', | ||
| type=str, | ||
| help='Filename with the slice timings.', | ||
| default=None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but atm either we import the fMRI file, or we need to get the information in another way - let's do the other way to begin with.
Co-authored-by: Stefano Moia <s.moia@bcbl.eu>
|
Hey, I made all the changes mentioned in your comments except the one regarding the nscans because l'm not sure what it is exactly. |
smoia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some suggested changes to take care of, but I think it's fine. @tsalo @CesarCaballeroGaudes does it make sense to you?
First draft of the parser.
I'm particularly not sure about slice_timing and n_harmonies.
Also pardon me for some poor descriptions in help.
I'm waiting for your comments!