ATTENDEES:
Till, Debbie, Diane, Kukhee, Sheng, Stephanie, Tom, Patrick, Ron, Antonio, Ernest, Terri
REVIEW NOTES:
This review covers both the design of the FCOM software, and the API. It does not cover how the Fast Feedback application software (controllers, actuators, detectors) will use FCOM. The design review for each subsystem application will cover how it uses FCOM.
- The fcom_icd document details the API for FCOM, and some design information, but the slides include more design detail that should be included in the document.
- Till explained the use of the version number to track changes to the FCOM API and module, so that applications can know they are communicating with compatible versions of FCOM.
- Till described several network functions that are NOT supported by FCOM, such as jumbo frames. These is not required for the Fast Feedback, and the limitations are documented in the ICD. Other projects considering FCOM must be aware of these limitations.
- There is a synchronous, or blocking call for fcomGetBlob. This functionality can be set up with the subscription call, and used subsequently with a timeout on the fcomGetBlob function.
- Stephanie asked about diagnostics - these are documented in the fcom_icd, Till can add more if requested.
At slide 21 several attendees had to leave. The remaining slides reviewed our latency analysis that we completed in August, where we concluded that this multicast network will meet our requirements. It also covered Till's progress and results of his testing this week. Till has remained on schedule throughout - and is ahead of the rest of the Fast Feedback team 
We discussed Till test results - see slide 24. The switches introduced more delay than expected.
ACTION ITEMS:
Till, Terri, Antonio - further testing to understand Till's current results.
Till - may continue to use test stand IOCs fb01 and mg01 in multiple configurations for test.
Terri & Ernest - please support Till in moving test stand cables for Till's various test configurations