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

Fixed doc of SDT #830

Merged
merged 1 commit into from Jan 9, 2016

Conversation

Projects
None yet
3 participants
@samuelstjean
Contributor

samuelstjean commented Jan 8, 2016

I stumbled upon what seems some discrepancies with the SDT paper https://www.ncbi.nlm.nih.gov/pubmed/19188114. Anyone can pitch in to say this is not a late friday afternoon mistake?

Fixed doc of SDT
I stumbled upon what seems some discrepancies with the SDT paper https://www.ncbi.nlm.nih.gov/pubmed/19188114. Anyone can pitch in to say this is not a late friday afternoon mistake?
@arokem

This comment has been minimized.

Member

arokem commented Jan 9, 2016

Hey @mdesco - can you confirm that SDT in this context stands for "Sharpening Deconvolution Transform"? Thanks!

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 9, 2016

Max is out of office. I confirm. The correct name is even in the abstract of the paper that Sam posted and in his thesis.

Garyfallidis added a commit that referenced this pull request Jan 9, 2016

@Garyfallidis Garyfallidis merged commit 2975f91 into nipy:master Jan 9, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@samuelstjean

This comment has been minimized.

Contributor

samuelstjean commented Jan 10, 2016

Explains also why I always had the name wrong and mic was laughing about
me. The original typo is also in an old abstract of ours btw.
On Jan 9, 2016 18:02, "Eleftherios Garyfallidis" notifications@github.com
wrote:

Merged #830 #830.


Reply to this email directly or view it on GitHub
#830 (comment).

@samuelstjean samuelstjean deleted the samuelstjean:patch-3 branch Jan 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment