1 / 5

One year after FESA1, we have now:

One year after FESA1, we have now:. A framework design and a Front End code fully supported by AB/CO/FC . Deployment procedures entirely in AB/CO/FC’s hands . Design and deployment data stored in ORACLE DB supported by AB/CO/DM . A complete set of solid, efficient and coherent tools .

keefer
Download Presentation

One year after FESA1, we have now:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. One year after FESA1, we have now: • A framework design and a Front End code fully supported by AB/CO/FC. • Deployment procedures entirely in AB/CO/FC’s hands. • Design and deployment data stored in ORACLE DB supported by AB/CO/DM. • A complete set of solid, efficient and coherent tools. • Documentation

  2. BUT: • We cannot start like foreseen our developments on LEIR [basic timing facilities (~PTIM) not available] • Even with timing, it is not yet possible to do the BTVI for LEIR with the current functionality [Priority levels per action not supported, RT actions in parallel not possible]

  3. BUT: • We cannot migrate BISCoTO/FESA1 SPS instruments toward FESA2 [work to support SPS legacy timing has not even started yet] • We cannot start PS consolidation (GM-Body eradication) with FESA 2 [basic timing facilities (~PTIM) not available, no GM Adaptor for FESA 2] • We cannot implement the ISOLDE Wire Scanners [No ‘User Command’ event sourceto send commands like ‘Make 20 consecutive scans’ to the RT Task]

  4. BUT: • We could do it with FESA 1 but: • FESA 1 is not supported by CO (apart from well defined CMW issues) • Backward compatibility with FESA 1 user code has been neglected [different data structures, file names, method signatures, object names…]

  5. Conclusions: • We still support and enjoy the framework, the team and the tools …But we are now stuck and waiting. • BDI invested and still invests a lot in FESA1 & FESA2. Don’t let us down. • Solve PS&SPS Timing and RT Tasks issues in the coming days [Ask for report next week]. • Port GM Adaptor to FESA 2 before Christmas now that it is working and fresh in our minds. • Fully support FESA 2 deployment, consolidation and adaptive maintenance.

More Related