Skip to content

Afni verbosity #2345

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

Merged
merged 4 commits into from
Jan 5, 2018
Merged

Afni verbosity #2345

merged 4 commits into from
Jan 5, 2018

Conversation

salma1601
Copy link
Contributor

add AFNI verbosity options when available

Copy link
Member

@effigies effigies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. A couple stylistic comments that you're welcome to reject if you disagree.

@@ -438,6 +438,12 @@ class AllineateInputSpec(AFNICommandInputSpec):
traits.Enum(*_dirs),
argstr='-nwarp_fixdep%s',
desc='To fix non-linear warp dependency along directions.')
verb = traits.Bool(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to say no, but would this make more sense as "verbose" instead of "verb"? I think that'll make interfaces a little friendlier to new users, while experienced AFNI users would know "verb" means "verbose", so it shouldn't cause confusion.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes I agree, I was hesitating on this one. Is that OK if I change all the AFNI verb (even introduced before my changes) to verbose ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. No, that would require deprecating, because somebody depends on this behavior. If it's consistent with existing interfaces, verb seems fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok

desc='Print out verbose progress reports.')
quiet = traits.Bool(
argstr='-quiet',
desc='Don\'t print out verbose progress reports.')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Preference: Use double-quotes instead of escaping apostrophes within single quotes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok

@@ -1377,6 +1380,9 @@ class MaskToolInputSpec(AFNICommandInputSpec):
'or using the labels in {R,L,A,P,I,S}.',
argstr='-fill_dirs %s',
requires=['fill_holes'])
verbose = traits.Int(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that you have verbose in Copy. If it's okay to mix-and-match (i.e., there are some interfaces that already have verbose), I'd prefer that you use verbose for all new additions. If this would be the first interface with verbose, I'd say switch it to verb for consistency.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I am not sure to follow. I added verbose to Allineate, Copy, MaskTool andTcat. These interfaces had no verbosity parameter before. I didn't touch the other ones which had already a verb or a verbose parameter as you told me.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I think I wrote this just as you made those changes. I wasn't sure if you were going to keep it at verb, but the changes you made look good. You can safely ignore that last message. (Also this one.)

@effigies
Copy link
Member

Looks good. Happy to merge when tests pass.

@mgxd mgxd merged commit 775e21b into nipy:master Jan 5, 2018
@mgxd mgxd added this to the 1.0 milestone Jan 21, 2018
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.

3 participants