How To Develop Software For Cms Tracker Sub Structure Tests

Transcription

1 Proposal for steps to be taken in the software development for CMS tracker sub structure tests W. Beaumont (Antwerpen) V.Zhukov (Karlsruhe)

2 software is important The software has a big influence on the procedure of assembly, long term test and solving problems. Up to now the procedures are not defined in detail. This presentation assumes a vague idea of a procedure, so the software development can start with the possibility to detail the software.

3 module identification Module (= module + opto -hybrid) is identified by its position in the sub structure. This determines an electrical address: CCU address, I2C channel ( I2C addresses of the chip are fixed). (1 FEC) This has to be related to the bar code(s) and can be related to the DCU ID. Output fibers are identified by a bar code ( related to the bar code of the opto-hybrid, related to the module) Information between bar codes (and object properties) has to retrieve from /exchanges with the production data base

4 software packages assembly program (new) Connectivity test Long term substructure test Diagnostic test slow control /interlock online monitor (optional)

5 Assembly program Gives a XML petal configuration (module location) output that is used as input for the other programs as also for the registration of the assembled petal to the production data base. Can be seen as a independent development task implementation : (XML) text editor or as someone takes care of it:

6 Register program

7 the petal configuration file petal configuration file LongTerm Assembly program Connectivity fixed configuration files

8 Connectivity test demands To check if the mounted module is correctly connected and working. Check location of the module with DCU id? Unique identification of modules. The software should be user friendly easy to operate without long learning period minimize the possibilities of mistakes stable also when errors appears Entering the complete assembled substructure to the production data base

9 connectivity test development As the long term test software is modular built and well understood by the current developers this will be used as base for further developments. Assistants is needed here. Can be a relative independent project.

10 long term structure test purpose To monitor the substructure during a long time in an environment in which the temperature is changed. To make sure that all components are functioning during the test. To check if properties of modules don t change (to much) It is not to determine the properties of modules etc. This is already done during the deep module test.

11 Long term test development module test on substructure based on the current Lt module test. data is stored as modules not as substructure. extra's like timing adjustments are provided by predefined (XML) configuration files Full? automatized test. (difficult if manual switching is needed)

12 Connectivity <--> Long Term Connectivity Long Term GUI Libs Parser and setup libs Run and analyzing tools

13 Slow control /interlock Group who will take care about this already formed can be independently developed only interfaces has to be agreed. It is very helpful if in parallel a proto- type setup ( petal production frame, interlock and other hw) could be built up in one of the institutes.

14 diagnostic software a software package that give access to all para meters. Proposal: No extra development. Available packages (XDAQ, standalone or LongTerm) give enough flexibility Has to be operated by a real expert (with knowledge on HW, software operations, can handle a oscilloscope) Developing expert systems is not realistic. Report all problems and solutions to a mailing list / web side that becomes a knowledge data base.

15 actions To be more modular source code has to be split in several libraries Now the data base registration interface is extracted from the two main programs (Long Term, Connectivity test) can be better controlled. The data data base registration interface and assembly programs can be developed separately. Still a lot of work to do for configuration files (XML) and GUI parts has to be done.