FESA3 Release X.x.x - Planning

Goals/Issues/Wishes

• Version of timing Software (, FESL? TBD) in standard Version property
• Persistency better configurable, e.g. at startup? -> implemented @CERN along with other persistency issues
• Exceptions should contain device name wherever possible (core / specific part) - exceptions are thrown per field, device seems not accessible at that moment in the core. See also CERN Jira issue 6337, https://www-acc.gsi.de/bugzilla/show_bug.cgi?id=1543.
• first implementation of transactional settings concept? \\winfilesvg\bel$root\belgroup\CS-Design\CCT-Documents\Concepts\TransactionalConcept FESA3TransactionalSettingsConceptImplementation
  • draft implementation
  • interface design
  • additional integration test (FESA class and deploy-unit, transaction manager 0.0.0)
• Rejecting invalid value-items using exceptions (items which don't exist in the class design; consider subsets!) [perhaps even suitable for FESA3 5.0.2]
• Optional filter-items???
• allow acquisition properties in the global interface (validation rule in plug-in)
• global device name change from cryptic to DUname.FECname (validation, model, migrator adaptions required)
• GSITemplate: Status-Property incl. timer, event, scheduler per default
• Per default: online watching of interface to hardware, more automation possible, useful? Is detailed status / module status insufficient? (-> idea PKain, TBD)
  • Observing timing receiver state in Standard Status (or ModuleStatus??? TBD) property (requires work in SAFTlib/FESL/FWK)
  • Bug 1828 - New project creation: pre-define a timer based Status Update
• Bug 1822 - Inconsistent Validation of struct-item Type
• Update of department short names in ResponsibleType, migrator for migrating CSCO->ACO, ...
• Bug 1839 - Visibility of Property ModuleStatus for Production
• TODO

To be removed

Backlog

• condition compiler: integration of messages with parameters? missing implementation: still no implementation for parameter usage in messages
• MASP integration? Stable API and library required, MASP usage configurable?
• TODO Usage of Eclipse Oxygen??? SVN plug-in/command line version incompatibilities expected, introduction postponed so far
• API for interlock signalling?
• how to proceed with setting data / persistent data problem of function generators? One setting property is not the right solution in this case.
• formalized data acquisition?
• ??? GSI: Alarm system integration -> CSCOSV, derzeit kein Ansprechpartner (07/16)
• ??? GSI: RBAC integration -> CSCOSV, VRapp, Integration possible in FESA in Release 9? (07/16)
• ??? GSI: Post Mortem integration -> CSCOSV, derzeit keine Planung dafuer (07/16)
• ??? GSI: Archiving integration -> CSCOSV, derzeit keine Planung dafuer (07/16) probably nothing to be done in FESA (05/18)

FESA3 6.0.0 Release@CERN (Email, TODO)

Dependencies

• cmw-rda3-cern VX.x.x (CERN: cmw-rda3-cern has been renamed to cmw-fwk)
• Boost 1.69
• cmw-cmx V2.1.5