# Agenda 2022-12-15

###### tags: `meeting` `update`
- Attendees
- [ ] Adam
- [x] Alan
- [x] Eric
- [x] Micah
- [x] Nathan
- [x] Nenad
- [ ] Joshua
- [ ] Tamie
- Previous Action Items
- [ ] Need to revisit language in CRA re: data sharing (esp. w/ hosting on BioHub)
- [x] Zarr MVP
- [ ] Nathan : add parameters around pixel size

- Topics
- Camera issue [#88](https://github.com/calliphlox/cpx/issues/88)
- OME metadata requirements
- What parts should be supported?
- Issue [#86](https://github.com/calliphlox/cpx/issues/86)

- Meeting Minutes
- Camera issue cpx#88
- Was data good before the failure?
- Suspecting a memory leak on camera driver; dcam known to leak resources
- Solution is likely to shut down entire driver and restart (monitor potential resource leaks over time)
- [ ] Nathan : investigate memory leak and back pressure (file system filled up)
- [ ] Micah : help monitor resourcing over acquisition time
- OME metadata requirements cpx#86
- https://ngff.openmicroscopy.org/latest/#metadata
- What should be supported?
- Enables Allen Institute to tie in contextual info for experiments (Saskia's file, Config.toml, OMERO)
- Instrument ID / Who collected
- Date collected/acquired
- Difficulty of selecting OME is finding users
- This is true, but after 20 yrs, this stanard still exists
- [ ] Nathan : need to follow up w/ Saskia on relevancy of OME (is this important downstream for the LIMS?)
- Coordinate transformation
- Having coord. transformation metadata would enable relational context when dropping different Zarr files into big data viewer

- Action Items
- Camera issue cpx#88
- [ ] Nathan : investigate memory leak and back pressure (file system filled up)
- [ ] Micah : help monitor resourcing over acquisition time
- OME metadata requirements cpx#86
- [ ] Nathan : need to follow up w/ Saskia on relevancy of OME (is this important downstream for the LIMS?)
- What does her metadata requirement/spec look like?