GithubHelp home page GithubHelp logo

jni / lma-2021-bioimage-analysis-python Goto Github PK

View Code? Open in Web Editor NEW
9.0 4.0 4.0 114.86 MB

"Bioimage analysis in Python" workshop at LMA2021

License: BSD 3-Clause "New" or "Revised" License

Makefile 0.01% Jupyter Notebook 100.00%

lma-2021-bioimage-analysis-python's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

lma-2021-bioimage-analysis-python's Issues

chunks too big, chunks too small... Buckets full of rocks.

During the workshop, Genevieve used the foreman analogy for the dask scheduler to explain why using tiny chunks are not optimal when trying to decide on chunk size. Chunks too big will crash our memory, but chunks too small will incur lots of overhead.

Feedback was great on the analogy so we should add it to the notebook! ๐Ÿ˜Š

Feedback based on workshop

This workshop was the first time the "images are numpy arrays" content was presentaed. Next time it runs, we should rearrange it so the exercises are interspersed through the content, rather than all at the end. I think that would be more engaging for participants.

Reword possibly misleading statement about dask

The dask tutorial includes this statement in the first couple of cells. I don't think this is strictly accurate, and it might be good to reword it.

A first life hack: in general, avoid using bare dask, and instead create a dask.distributed Client as in the cell below. What this buys you:

  • memory management: the distributed scheduler that is automatically created with the default client will launch processes with maximum memory limits. If they exceed those limits, the scheduler will stop sending tasks to them and eventually kill them. In contrast, without distributed, you are subject to the same issues as bare Python. It is very easy to freeze your machine.

Dask documentation reference; https://docs.dask.org/en/latest/setup/single-distributed.html

Add more resources links based on participant suggestions

Workshop participants put a whole bunch of great resources into the chat when we asked them about their favourite places to learn more about image analysis.

We should add that information here too (most likely to the last section in the README, which currently contains a link to forum.image.sc and the napari zulip channel).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.