You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/open-software-week/big-imaging-data.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,13 +17,13 @@ This course is designed for imaging facility staff, image analysts, and imaging
17
17
18
18
## Course overview
19
19
20
-
__Tuesday morning:__
20
+
__Thursday morning:__
21
21
The technical side of the track will start with an introduction to chunked file formats for big imaging data, such as `OME-zarr`.
22
22
We will then proceed to work on hands-on tutorials to
23
23
- Read and write big imaging data using `zarr`
24
24
- Process big imaging data lazily and in-parallel with `dask`
25
25
26
-
__Tuesday afternoon:__
26
+
__Thursday afternoon:__
27
27
The community side of the track will start with a very short introduction to existing community efforts in both software engineering [^1]_, imaging[^2]_ and image analysis[^3]_.
28
28
The participants will then join small discussion groups of their choice circling around the wider question: Where next for careers and community in Big Imaging Data?
29
29
The discussions will then be fed back to the wider group, and result in the publication of a blog after the course.
@@ -52,6 +52,13 @@ We will email you at least a week before the event with instructions on installi
52
52
If you're new to Python, we recommend attending our __Intro to Python__ workshop on Monday, or completing an equivalent course beforehand.
53
53
This hands-on session will cover the basics, including data types, control flow, functions, and core libraries—a great way to get up to speed before this event.
54
54
55
+
### Data
56
+
Bringing your own data is encouraged but not required.
57
+
It's a great chance to get feedback on your data and learn from others.
58
+
If you don't have your own data, we will provide example datasets for you to work with.
59
+
60
+
We expect that participant-led ideas emerging from this track may inspire collaborative projects during the __Hackday__ on Friday.
61
+
55
62
### Related
56
63
57
64
If you're interested analysis tools for whole-organ imaging (particularly brains), you might also benefit from attending the preceding two-day [BrainGlobe main track](brainglobe.md).
@@ -62,4 +69,4 @@ Fill in [this Google form](https://forms.gle/2UAAzikhSgYArZpX7) to apply. We unf
62
69
63
70
[^1]: community initiatives around e.g. the [Software Sustainability Institute](https://www.software.ac.uk/), the [Society for Research Software Engineering](https://society-rse.org/about/history/), and The Hidden REF.
64
71
[^2]: For example [BioImagingUK](https://www.rms.org.uk/community/networks-affiliates/bioimaginguk-network.html), [Euro-BioImaging](https://www.eurobioimaging.eu/), [Global Bioimaging](https://globalbioimaging.org/)
65
-
[^3]: For example [neubias](https://eubias.org/NEUBIAS/), [GloBIAS](https://www.globias.org/)
72
+
[^3]: For example [neubias](https://eubias.org/NEUBIAS/), [GloBIAS](https://www.globias.org/)
0 commit comments