imaging

It seems like a slight pain to do this, but it might be useful to have a GitHub action generate HTML GoDoc on PRs / code pushes, so that reviewers can easily preview what the GoDoc will look like.

It looks like the easiest way to do this is with wget sadly (if you want all the nice styles and such applied in the html).

Per SVK's suggestion, it is worth exploring if one can use an autoencoder (regular or variational) instead of PCA for the sliding-window-based image denoising originally written by @ramav87 .

@saimani5 @markpoxley will you be interested in exploring it?

See brainglobe/cellfinder#182

Moving to using dask means that confusingly, if you have a text file of paths, the registration will work, but the cell detection wont.

Add a PolyDataIO based on the VTK::IOPDALmodule:

https://github.com/Kitware/VTK/tree/master/IO/PDAL

Steps (a complete example can be found here):

0. Verify that the test suite runs and passes

The spinning indicators give the impression that data is loading but that is not correct. An alternative that is not moving would be better.

Currently, we are having readthedocs.org build the documentation for each PR and, if there are any warnings, the build fails immediately. This is a good thing, because it ensures that every PR is generating good documentation, including running the examples.

As discussed in #271, it would be nice to be able to see all of the warnings for the doc build instead of failing on the first one. B