Dundee: Will, Petr, Kenny, Dominik, Jean-Marie, Mark, Roger, Simon, Riad,
Remote: Josh, Liza, David, Chris, Melissa, Wilma, Jason (phone), Emil, Andreas
Start: 2:00 pm
(2-3 minutes each)
plan is to release on Thursday
After no more code PR review - focus on Users Meeting
(in no particular order)
East (infra/IDR 0.5.0)
Populate metadata PR (Emil)
IDR core 0.5.0 stable (Memoizer issues)
1 PR not backported. Discuss: fix IDR to use latest BF?
Regenerating memoizers can kill server
Few ongoing misc. deliverables: apex, render plugin
Largely focusing on workshop deliverables
microservice</u>](https://gitlab.com/openmicroscopy/incubator/mapr-microservice) offering mapr-related queries of materialized view via HTTP endpoint.
More examples & docs to come - Managed repo, microservices etc.
5.9 Reader - PR open
5.9 Writer - Not started yet
5.8 Reader: data assumptions lead to silent failure (worst
version bump), require upgrade, etc
Can’t release files publicly until resolved
are clear about status
workflow in the morning
Other sessions in afternoon.
60-seater room on 2nd floor. Plenty big enough.
Image Training hackathon in Cambridge - Mon/Tues (Petr).
(5 min. max; tech. Discussion should be highlighted to relevant people and rescheduled)
(20-25 minutes plus 15 minutes questions max)
OMERO 5.4.6 changelog text suggestion for read-only:
This introduces a significant new subsystem for read-only operation with which servers can be configured not to make changes to the database, the filesystem, or both. The goal is to permit horizontal scaling of OMERO by running multiple servers in parallel to increase the throughput of data and metadata for large-scale analysis or publishing. Additionally, a read-only copy of an existing OMERO can be opened safely to the public for experimentation. For example, this infrastructure supports the public OMERO web and Jupyter environment of the Image Data Resource, https://idr.openmicroscopy.org/.