Skip to content

Conversation

@ineschh
Copy link
Contributor

@ineschh ineschh commented Nov 12, 2020

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!

@eurunuela
Copy link

Wait, we have to get rid of Travis. I'll open an issue.

Copy link
Member

@tsalo tsalo left a 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.

optional.add_argument('-os', '--oversampling',
dest='oversampling',
type=int,
help='Temporal oversampling factor in seconds. '
Copy link
Member

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.

Copy link
Contributor Author

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

optional.add_argument('-tl', '--time-length',
dest='time_length',
type=int,
help='RRF Kernel length in seconds.',
Copy link
Member

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?

Copy link
Contributor Author

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 smoia changed the title add parser Add Parser Nov 12, 2020
Copy link
Member

@smoia smoia left a 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?

Comment on lines 149 to 150
help='Sampling rate for the output time series '
'in seconds. Corresponds to TR in fMRI data.',
Copy link
Member

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

Comment on lines 165 to 169
optional.add_argument('-slt', '--slice-timings',
dest='slice_timings',
type=str,
help='Filename with the slice timings.',
default=None)
Copy link
Member

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.

@ineschh
Copy link
Contributor Author

ineschh commented Nov 13, 2020

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.

Copy link
Member

@smoia smoia left a 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?

@smoia smoia mentioned this pull request Feb 25, 2021
18 tasks
@smoia smoia closed this in #17 Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants