...
- There was some discussion on DMS-REQ-0131. This requirement tries to constrain calibration products production by stating that it should take no more than 20 minutes to process 25 calibration exposures.
- AP team is digging in on middleware now – should they use same Slack channel?
- Recommend: start using same channel; endeavor to thread responses
- MG: empty directories? Leave them around?
- Tim: if random incoming "puts", probably easiest?
- How much will this happen? (Should be rare.) Will job scratch repos make this less of an issue?
- MG: raw IDs the same no matter who does ingest?
- Jim: can do if it helps DBB sync etc.? What was the motivating use case?
- There was some discussion of Gen 3 OODS and ingestion. Firstly it was suggested that the "group ID" generated during observing could be treated as an exposure parameter and not a "visit" identifier. This would prevent confusion over the term "visit" and allow OODS to ingest each exposure incrementally without having to know how many exposures are in the "visit". Secondly there was an issue over whether OODS is required to ingest all 189 CCD files in one ingest or if it can do that ingest incrementally as files are picked up. It probably makes sense to ingest in one go given that an "ingest complete" event is requirerequired on completion.