-
Notifications
You must be signed in to change notification settings - Fork 530
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
Better documentation and educational components #1357
Comments
Hi @satra and all. Congratulation on the Nipype grant, that's amazing news!!! |
@miykael - what i would like to see is a set of jupyter notebooks that are fully executable and also turn into reasonable slideshows. this will take some effort to implement, but i would like to see small chunks build through different components of nipype. as a related example see: http://mbakker7.github.io/exploratory_computing_with_python/ |
Feel free to fork https://github.com/mwaskom/nipype_concepts :) |
@mwaskom - indeed. we really need to start putting all these pieces together. what i like about mark's work are study examples that he created which makes people implement things. and i think his intro to python also can be re-formulated for biomedical scientists. ideally we will create a set of documents and tools that will work as a complete teaching package that we can use in our workshops as well. i better finish the engine rewrite soon, so that we don't have to perform too many modifications! :) |
@satra In Udacity they are doing a course on tensorflow, check out the materials: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/udacity/README.md I find particularly convenient the docker image, that you run and launches a jupyter server with the assignments. It takes around 2 minutes to get it started if you manage to install docker. |
I'd be happy to work on educational notebooks as well. |
@fliem - that's a great start. here are some thoughts:
most people can setup nipype workflows quite easily following some basic instructions, the harder part is to debug execution errors, so if we can guide people through errors and how to fix them that would be very helpful. we should also have sections on how to build your own interface and contribute code to nipype. |
@fliem - i will be at brainhack in lausanne and this would be a good project there. |
@satra can we close this issue and open a new one if needed? I think missing part is at least partially covered in the issue from nipype_tutorial miykael/nipype_tutorial#37 |
The text was updated successfully, but these errors were encountered: