Detailed development conventions are descrived at!master/navigator/document?P:1414255486:100275477:subDocs, summarised in the following. A git repository containing everything required to install a project from scratch is available

Instructions to use the git repository

  • If not done before, clone the repository:

git clone ssh://

  • if you cloned the repository some time ago, pull the latest changes with:

git checkout master
git pull origin master

  • create your development branch with:

git checkout -b userName_partition

where userName is your username and partition is the partition you are working on (HV, DAQ, DCS, ecc)

* add the files you want to push on the remote repository with

git add fileToAdd

where fileToAdd is the name of the file you want to add, for every file.

  • commit the changes

git commit -m "commit message describing what you are pushing"

  • push the changes

git push origin userName_partition

  • open a merge request following the link appearing on the terminal with a web browser:

- Source branch: userName_partition ; Target branch: master

- Press "Compare branches and continue".

- If you still have things to finish before the request can be merged, put the prefix WIP in the title.

- Write a summary of your changes in the description textfield.

General development conventions

When developing panels, the system name must always be used before each call to datapoint elements.

The top domain CU will use the RICH1 or RICH2 prefix, and an underscore will separate the prefix from the domain name (e.g. RICH1_DCS). The nodes below will have the prefix R1U_domainName, R1D_domainName, R2A_domainName, R2C_domainName for RICH1 Up, RICH1 Down, RICH2 A-side and RICH2 C-side, respectively. domainName is either HV, DCS, DAQ, ECS. All the CU and LU names must be upper-case.

The hardware devices need first to be appended to the logical view, by using the same tree structure that will be used in the FSM. The device units are appended to the FSM from the logical view. For each partition, a configurator panel allows to define the aliases, to append devices to the FSM, and to access the recipe configurator.

When sending messages to the logviewer, the DebugTN function will be used, in orde to have the corresponding timestamp. The format of this timestamp (YYYY.MM.DD HH:MM:SS.mmm) will be used everywhere.

Installation at the pit

When installing or moving projects to the pit, the rich_oper account will be used. The installation folder will be /localdisk/wincc. The JCOP components will be installed in /group/rich/pvss/fwComponents_projectName, where project will be R2HV1 for instance.

All projects will belong to the rich group and have group permission read/write.

-- GiovanniCavallero - 2020-05-14

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2020-05-19 - GiovanniCavallero
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback