-
Notifications
You must be signed in to change notification settings - Fork 70
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
examples from nipype #98
Comments
@djarecka - I'm all for moving the examples to the tutorial, but I have two concerns:
I think a better place to put those examples (and to let them be improved by the community) is niflows. What do you think? I also think that we could eventually improve the "Workflow Example" section on nipype tutorial. At the moment it's just a two different pipelines ("Example" and "Hands-on") that I like to show. But I think we can improve the content there, as well as the layout. |
@djarecka - About the beginner's guide... While I'm very attached to it (it was my first own homepage - and it also looks that way), I would be happy to let it slowly disappear. There's no point of having the beginner's guide and the tutorial together, and I currently have not much time to focus on the beginner's guide. The problem is that the beginner's guide is still more popular than the tutorial: Site Overview over the last 13 months for the Beginner's Guide Site Overview over the last 13 months for the Nipype Tutorial This all might change over the next few months, but for the moment the beginner's guide seems to be useful. |
@miykael - of course, I don't want you to remove something that is useful, but I have to admit it's not clear to me who should be pointed to the Beginner's Guide and and who to the Nipype Tutorial. It seems to me that links to these website are included a bit randomly on Nipype website, but I could be wrong. If you think that this website is dedicated to different people, that's fine, but maybe we can at least clarify it somewhere. Do we test any examples from the beginner website with the current Nipype? And about the examples: I'm sure that many of them are out of shape and that's why I started thinking that they should be tested somewhere. Not saying that Nipype Tutorial is the best place, just wanted have discussion where they fit best and how they should be updated/tested. |
I'm happy to "hide" the beginner's guide. How could I best do that? I already have an Important banner on the beginner's guide, directing people to the tutorial (http://miykael.github.io/nipype-beginner-s-guide/). Hmm... I just saw that this banner is outdated. I think I will rewrite the text and state very clearly that the beginner's guide content hasn't been updated since April 2016. That should hopefully move people to the tutorial. What do you think @djarecka? The beginner's example are not tested. And in comparison to the tutorial, I think the only real additional content is the FAQ and Glossary section. And anyhow, their content is to 95% from http://mindhive.mit.edu/node/46 and http://mindhive.mit.edu/node/71. @djarecka and @satra, should I include those two sections in the tutorial as well? Does it make more sense to update the mindhive homepage (many links and references are broken) or should I leave this aside anyhow? |
@miykael - yes, I think it's a good idea to be clear that the examples from the website are not tested (so people don't expect that everything is working), and that the tutorial is tested. I'm checking now FAQ and Glossary, and you're absolutely right that this can be very useful for the beginners, so we shouldn't hide them. My main concern was really regarding the nipype code, since there are many sources that people take examples, and they expect that everything should work... And it looks like many examples haven't been really tested for long time (e.g. the pipelines from |
a few notes:
|
@satra , @miykael - should we move these examples to the nipype tutorial?
Should we still point to the "Beginner's Guide"?
You might have already write about it, but can't find it right now.
The text was updated successfully, but these errors were encountered: