Skip to content

Commit 72cef80

Browse files
committed
add links to people
1 parent a37a95f commit 72cef80

File tree

1 file changed

+15
-13
lines changed

1 file changed

+15
-13
lines changed

_posts/2019-05-02-zarr-2.3-release.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,9 @@ tutorial](https://zarr.readthedocs.io/en/stable/tutorial.html#distributed-cloud-
6464
The attraction of cloud storage is that total I/O bandwidth scales
6565
linearly with the size of a computing cluster, so there are no
6666
technical limits to the size of the data or computation you can scale
67-
up to. Here's a slide from a recent presentation by Ryan Abernathey
68-
showing how I/O scales when using Zarr over Google Cloud Storage:
67+
up to. Here's a slide from a recent presentation by [Ryan
68+
Abernathey](https://github.com/rabernat) showing how I/O scales when
69+
using Zarr over Google Cloud Storage:
6970

7071
<script async class="speakerdeck-embed" data-slide="22" data-id="1621118c5987411fb55fdcf503cb331d" data-ratio="1.77777777777778" src="//speakerdeck.com/assets/embed.js"></script>
7172

@@ -122,14 +123,14 @@ entry](https://github.com/pangeo-data/pangeo-datastore/blob/aa3f12bcc3be9584c1a9
122123
## Compatibility with N5
123124

124125
Around the same time that development on Zarr was getting started, a
125-
separate team led by [Stephan
126-
Saafeld](https://www.janelia.org/lab/saalfeld-lab) at the Janelia
127-
research campus was experiencing similar challenges storing and
128-
computing with large amounts of neural imaging data, and developed a
129-
software library called [N5](https://github.com/saalfeldlab/n5). N5 is
130-
implemented in Java but is very similar to Zarr in the approach it
131-
takes to storing both metadata and data chunks, and to decoupling the
132-
storage backend to enable efficient use of cloud storage.
126+
separate team led by [Stephan Saafeld](https://github.com/axtimwalde)
127+
at the Janelia research campus was experiencing similar challenges
128+
storing and computing with large amounts of neural imaging data, and
129+
developed a software library called
130+
[N5](https://github.com/saalfeldlab/n5). N5 is implemented in Java but
131+
is very similar to Zarr in the approach it takes to storing both
132+
metadata and data chunks, and to decoupling the storage backend to
133+
enable efficient use of cloud storage.
133134

134135
There is a lot of commonality between Zarr and N5 and we are working
135136
jointly to bring the two approaches together. As a first experimental
@@ -175,9 +176,10 @@ handling different Python versions.
175176

176177
There is a growing community of interest around new approaches to
177178
storage of array-like data, particularly in the cloud. For example,
178-
Theo McCaie from the UK Met Office Informatics Lab recently wrote a
179-
series of blog posts about the challenges involved in [storing 200TB
180-
of "high momentum" weather model data every
179+
[Theo McCaie](https://github.com/tam203) from the UK Met Office
180+
Informatics Lab recently wrote a series of blog posts about the
181+
challenges involved in [storing 200TB of "high momentum" weather model
182+
data every
181183
day](https://medium.com/informatics-lab/creating-a-data-format-for-high-momentum-datasets-a394fa48b671). This
182184
is an exciting space to be working in and we'd like to do what we can
183185
to build connections and share knowledge and ideas between

0 commit comments

Comments
 (0)