rhoana / icon_archived Goto Github PK

Reorganize to make it pip installable.
@fegonda, @Thous asked me to make icon use butterfly as an image server and generally take over maintainership. I like the overall organization - the database abstraction & using it to communicate with the server-side training and segmentation servers, but it needs to be pip installable for @jtriley to be able to deploy.

Basic reorg will be to rename "code" to rh_icon (because "icon" is likely to collide with something else out there named "icon") and to change the imports to use a hierarchy rather than adding the directories to sys.path + do some build_ext magic to compile libraries where needed and to manage Theano's THEANO_FLAGS environment variable.

It would be pretty cool to be able to bring up a Butterfly dataset and visually browse it for candidate tiles for Icon. I'm not sure if this is a tool in the Butterfly client or in Icon (Butterfly's OpenSeaDragon would be a better choice for handing the various levels, but how to package the result up so that Icon can access it?)

Add database tables to translate between project ID and butterfly's (soon to be) experiment / dataset / channel breakdown of how to get images.
Store butterfly images using the format, "butterfly:+" where is the plane # of the image.
Add an imagehandler tornado.web.RequestHandler that uses the above. If an image is a butterfly URL, then it uses the tornado web client to forward the request to butterfly, otherwise it goes to disk to get the image.