How does one get started? about tutorials HOT 4 CLOSED

Much better. It would be useful to add instructions on how to start Binder (and warn the user for expected long time the initial steps take). I think that the errors I show were caused by the first cell not finishing execution yet.

I'll open a new issue for an error I encountered using the Python kernel.

from tutorials.

@nicost There are several different notebooks covering different topics. As the second bullet point of the "ImageJ Tutorials and Demo" notebook says: "To dive in to the tutorials, click the links below." Hopefully you see a table of contents that looks like this?

Start with the "Using ImageJ" tutorials, and if you want more detail, you can read the "Advanced usage" tutorials as well. The notebooks are all using the Groovy BeakerX kernel, except for "ImageJ with Python Kernel" which uses Python 3 and shows how to use pyimagej to work with ImageJ from Python.

Edit: Just saw this part of your comment:

When clicking on those I see lines of code and comments, but nothing that I can interact with, change and no way to make this run myself (I discovered a button on the top right that says "Execute on Binder", but that leads to a long wait and then lots of errors).

Regarding Binder: I did not have time to test the latest master branch on Binder yet. I am sorry to hear that it no longer works. I will try to fix that ASAP, although I have some other urgent deadlines right now.

Regarding getting started with Jupyter: here is a quick start guide. I personally think the easiest way to get started with it on your local computer is to:

1. Install conda
2. Clone this imagej/tutorials repo
3. Open a terminal and cd to the local clone
4. Run conda env create -f environment.yml
5. source activate scijava to activate the environment
6. jupyter notebook to launch Jupyter Notebook.
7. Open the notebooks and enjoy running the cells live.

from tutorials.

I added a version of the above instructions to the README with c2e454b. I hope it helps.

from tutorials.

I just tested on Binder, and it works for me. The first time a particular commit from GitHub is launched, it takes a while to build, on the order of minutes. Then, the first time you open a notebook and execute the ImageJ initialization cell for a particular Binder instance, it takes again on the order of minutes to execute, because it downloads and caches the ImageJ libraries. I don't have an easy idea how to make this faster on the cloud side, other than to reduce the footprint of net.imagej:imagej. If you got error messages, it would be helpful to copy/paste them as an issue here, so that we can troubleshoot.

I'm closing this issue, since there are instructions in place now, but feel free to reopen if you feel the documentation is still insufficient!

from tutorials.