-
Notifications
You must be signed in to change notification settings - Fork 26
jBaci
- ACS: ALMA Common Software
- BACI: BAsic Control Interface
The objective of this project is to review the current implementation of the BACI properties done in Java, and complete the missing parts of it as needed.
ACS provides a software infrastructure common to all partners and consists of a documented collection of common patterns in and of components, which implement those patterns. The heart of ACS is based on a distributed component model, with ACS components implemented as CORBA objects in any of the supported programming languages. The teams responsible for the control system's development use ACS Components as the basis for control high level entities and for the implementation of devices such as an antenna mount control. ACS provides common CORBA-based services such as logging, error and alarm management, configuration database and lifecycle management.
One of the part of ACS is BACI, which defines a framework that forms a base for the IDL definition of the interfaces for the controlled objects. BACI itself does not define any specific control system (for instance a control system designed to manage a synchrotron light source or a network of gas pumps). It does, however, restrict the set of all definable objects with the IDL to a specific set that conforms to BACI design guidelines and uses BACI interfaces in a predefined way.
Currently the BACI specification has an implementation in C++, this was done in the collaboration framework of ALMA, which uses this implementation in its Control system software. Nowadays, there has been huge interest from the ACS users community, to start to use a BACI implementation based on Java programming language, there is an outdated implementation which might not work completely. Hence, it needs to be reviewed.
- Review the BACI specification requirements, considering monitoring and alarm as well
- Check ACS and ALMA documentation, this includes manual and twiki pages
- Review the current jBACI code available as part of the ACS community repository (open source software)
- Prepare a machine to install ACS community build. ACS community requires RHEL 6 64-bit
- Understand and prepare the development environment in the prepared machine.
- Implement in Java the missing parts of jBACI
- Add unit tests and instructions to automatize the build.
- Developed code must be according to the ACS community standards, therefore the results may result in a contribution to the ACS community.
| # | Milestone/Deliverable | Planned Completion Date | Status |
|---|---|---|---|
| 1 | Documentation of the requirements for this project and preparation of the environment/machine | End of week 2 | PENDING |
| 2 | Documentation of the proposed solution | End of week 3 | PENDING |
| 3 | Implementation and testing | End of week 6 | PENDING |
| 4 | Presentation for ADC Software Group and documentation on twiki page | End of week 8 | PENDING |
- Ubuntu & VirtualBox installed.
- CentOS 6.7 installed on virtual
- ACS required packages downloaded and installed.
- Additional ACS pre-installation procedures.
- ACS version 2015.2 successfully installed and started.
- Bugs found on ACS version 2015.2.
- Unable to run more than one ACS Instance at the same time.
- Unable to start more than one container.
- After invoking 'acsStop' the lock file is not deleted.
- ACS version 2014.6 installed.
- Eclipse installed.
- jBaci project configured.
- Read jBaci & Baci code.
- Read documentation (BACI supported types, BACI properties).
- Printed Baci UML.
- Read jBaci & Baci code.
- Printed jBaci UML.
- Ran jBaci old tests.