The scientific programing takes part from Monday till Friday.
It is envisioned to start from 9am till dinner at 7pm, and often even
afterwards to accommodate time-zone difference between EU and US.
Monday
- Arrivals shortly after lunch time
- Afternoon session: Fiji GUI options, esp. towards the Drag-and-drop capability
Tuesday
- Arrivals during the day
- Morning session: Fiji GUI coding
- Afternoon session: Zarr specs analysis, planning
- After dinner: Online meeting about N5 Viewer GUI dialog
Wednesday
- Arrivals during the day
- Heads-up local meeting, analysis, planning
- All day: Coding session
- After dinner: Discussions and experiences exchange during Online meeting
Thursday
- Heads-up local meeting, analysis, planning
- All day: Coding session
- After dinner: Discussions and experiences exchange during Online meeting
Friday
- Morning session: Coding session
- Afternoon session: "Putting it all together"
- After dinner: Discussions and experiences exchange during Online meeting
Saturday
- Breakfast together, check-out
-
OME-NGFF Session
We use the term next-generation file formats (NGFFs) to denote file formats that can be hosted natively in an object (or cloud) storage for direct access by a large number of users. Our current work, which we refer to as OME-NGFF, is built upon the Zarr format5 but heavily informed and connected to both TIFF and HDF5.
We assert that together low-latency, cloud-capable NGFF, TIFF and HDF5 can provide a balanced set of options that the community can converge upon and slow the development of ever more file formats. To this end, OME is committed to building an interoperable metadata representation across all three file formats to ensure ease of adoption and data exchange
OME-NGFF: a next-generation file format for expanding bioimaging data-access strategies
-
DataStore Session
The DataStore is shortest described as BigDataServer that can also accept images besides serving them. In other words, it is a REST HTTP-based client-server for downloading/uploading chunks from images from/to a remote dataset. The server is storing image data using the N5 on disk in a BigDataViewer unique XML/N5 dialect. The server communicates with its clients using our own simple protocol.
Motivation as well some reasoning, application examples and more details in general can be found here.
