Difference: RICHUpgradeDatabase (1 vs. 39)

Revision 392019-08-27 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 95 to 95
 
Import QA data
Changed:
<
<
Convert the xlsx file to the csv format, comma delimited.
>
>
Convert the xlsx file to the csv format, comma delimited. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Create Devices". Select the file and press import.
 
Changed:
<
<
Create new devices and open table of preliminary tests
>
>
Create new devices and open table of preliminary tests (OBSOLETE)
  Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Create Devices". A table with the fields required by the quality assurance procedure is opened. Fill the fields as required. If the date of the tests is different from the date of writing, change it accordingly. The hour/minute/second fields are indicative and required if you want to retrieve the table with the same serial numbers (to distinguish it from another table created in the same day). Press import to create the new devices in the database. A search within the already existing serial numbers will be performed. If any device with the same serial number has been already inserted in the database, the import will be aborted (i.e. none of the devices will be inserted).
Changed:
<
<
Update an existing device with the complete preliminary tests
>
>
Update an existing device with the complete preliminary tests (OBSOLETE)
  If the table described above it's not complete, for instance the information on the HV is missing, you can integrate this information later on. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties". Click "Retrieve test table by test date", and select the date/time you need. Fill the missing fields in the table and press update.
Changed:
<
<
Update an existing device with the data from anodes and dynodes continuity tests
>
>
Update an existing device with the data from anodes and dynodes continuity tests (OBSOLETE)
  Important: the files produced with Windows PowerShell must be converted from dos to unix format.
1) Move to the folder containing the files and open them with vi *. Type esc and :setautowriteall. Type ::bufdo %s/\r//ge. Keep pressing enter until all files are modified. Type :wq. Convert them using the dos2unix command.

Revision 362019-05-27 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 104 to 104
 
Update an existing device with the data from anodes and dynodes continuity tests
Changed:
<
<
Important: the files produced with Windows PowerShell must be converted from dos to unix format. Move to the folder containing the files and open them with vi (vi -o *), and type :%s/\r/ . Copy the files on your home to pclbrich02 and convert them using the dos2unix command.
>
>
Important: the files produced with Windows PowerShell must be converted from dos to unix format.
1) Move to the folder containing the files and open them with vi *. Type esc and :setautowriteall. Type ::bufdo %s/\r//ge. Keep pressing enter until all files are modified. Type :wq. Convert them using the dos2unix command.
  Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties". Click "Import anodes/dynodes data". Select the folder containing the files and press

Revision 342019-03-06 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 100 to 100
 
Update an existing device with the complete preliminary tests
Changed:
<
<
If the table described above it's not complete, for instance the information on the HV is missing, you can integrate this information later on. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties".
>
>
If the table described above it's not complete, for instance the information on the HV is missing, you can integrate this information later on. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties". Click "Retrieve test table by test date", and select the date/time you need. Fill the missing fields in the table and press update.

Update an existing device with the data from anodes and dynodes continuity tests
  Important: the files produced with Windows PowerShell must be converted from dos to unix format. Move to the folder containing the files and open them with vi (vi -o *), and type :%s/\r/ . Copy the files on your home to pclbrich02 and convert them using the dos2unix command.
Added:
>
>
Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties". Click "Import anodes/dynodes data". Select the folder containing the files and press
 

EC

PDM

Revision 332019-03-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 96 to 96
 
Create new devices and open table of preliminary tests

Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Create Devices". A table with the fields required by the quality assurance procedure is opened. Fill the fields as required. If the date of the

Changed:
<
<
tests is different from the date of writing, change it accordingly. Press import to create the new devices in the database. A search within the already existing serial numbers will be performed. If any device with the same serial number has been already inserted in the database, the import will be aborted (i.e. none of the devices will be inserted).
>
>
tests is different from the date of writing, change it accordingly. The hour/minute/second fields are indicative and required if you want to retrieve the table with the same serial numbers (to distinguish it from another table created in the same day). Press import to create the new devices in the database. A search within the already existing serial numbers will be performed. If any device with the same serial number has been already inserted in the database, the import will be aborted (i.e. none of the devices will be inserted).
 
Update an existing device with the complete preliminary tests

Revision 322019-03-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 102 to 102
  If the table described above it's not complete, for instance the information on the HV is missing, you can integrate this information later on. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties".
Changed:
<
<
Important: the files produced with Windows PowerShell must be converted from dos to unix format. Open the files with vi (vi -o *), and type :%s/\r/ . Copy the files to pclbrich02 and convert them using the dos2unix command.
>
>
Important: the files produced with Windows PowerShell must be converted from dos to unix format. Move to the folder containing the files and open them with vi (vi -o *), and type :%s/\r/ . Copy the files on your home to pclbrich02 and convert them using the dos2unix command.
 

EC

Revision 312019-03-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 6 to 6
 

Inventory, Bookkeeping and Connectivity Database project

Changed:
<
<
The large number of units, their test, qualification and calibration and their connectivity in Elementary Cells (EC), Photo-Detector Modules (PDM), columns and photo-detector assemblies motivated the development of an inventory and bookkeeping system to store and retrieve data.
The RICH Inventory, Bookkeeping and Connectivity Database (IBCDB) is an under development WinCC-OA project working as a user friendly DB for the RICH upgrade. The choice of WinCC-OA is mainly motivated by the scattered tools already provided by the JCOP framework. Moreover, this choice will make easier the integration of the DB with the upgraded LHCb ECS and the information exchange with the standard LHCb databases.
The DB will provide the full detector inventory and bookkeeping, accounting for the hierarchical structure of all the sub-assemblies and for the changes in time of the composition of the assemblies and their calibration data. The DB will allow to take a snapshot of all detector data, retrieving all and only the data valid at a certain date-time. The main aim of the DB is to track the full history of every devices that will be used in the RICH detectors.
The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDMDB, PDM.
>
>
A note describing the functionalities of the database (DB) is available at https://edms.cern.ch/ui/#!master/navigator/document?P:1414255486:100275478:subDocs. The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, EC, PDMDB, PDM.
 

How to connect to the database from outside the CERN network

Line: 93 to 93
 

BaseBoard

Changed:
<
<
The files produced with Windows PowerShell must be converted from dos to unix format. Open the files with vi (vi -o *), and type :%s/\r/ . Copy the files to pclbrich02 and convert them using the dos2unix command.
>
>
Create new devices and open table of preliminary tests

Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Create Devices". A table with the fields required by the quality assurance procedure is opened. Fill the fields as required. If the date of the tests is different from the date of writing, change it accordingly. Press import to create the new devices in the database. A search within the already existing serial numbers will be performed. If any device with the same serial number has been already inserted in the database, the import will be aborted (i.e. none of the devices will be inserted).

Update an existing device with the complete preliminary tests

If the table described above it's not complete, for instance the information on the HV is missing, you can integrate this information later on. Select BaseBoard as the default device type. Click on "Start Hardware View". Click on "Insert/Update Device properties".

Important: the files produced with Windows PowerShell must be converted from dos to unix format. Open the files with vi (vi -o *), and type :%s/\r/ . Copy the files to pclbrich02 and convert them using the dos2unix command.

 

EC

Revision 282018-06-06 - LhcbTestbeamSupportService

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 8 to 8
  The large number of units, their test, qualification and calibration and their connectivity in Elementary Cells (EC), Photo-Detector Modules (PDM), columns and photo-detector assemblies motivated the development of an inventory and bookkeeping system to store and retrieve data.
The RICH Inventory, Bookkeeping and Connectivity Database (IBCDB) is an under development WinCC-OA project working as a user friendly DB for the RICH upgrade. The choice of WinCC-OA is mainly motivated by the scattered tools already provided by the JCOP framework. Moreover, this choice will make easier the integration of the DB with the upgraded LHCb ECS and the information exchange with the standard LHCb databases.
The DB will provide the full detector inventory and bookkeeping, accounting for the hierarchical structure of all the sub-assemblies and for the changes in time of the composition of the assemblies and their calibration data. The DB will allow to take a snapshot of all detector data, retrieving all and only the data valid at a certain date-time. The main aim of the DB is to track the full history of every devices that will be used in the RICH detectors.
The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDMDB, PDM.
Changed:
<
<

How to connect to the database

>
>

How to connect to the database from outside the CERN network

FROM LINUX

FROM WINDOWS

  • Remote Desktop to cernts.cern.ch and from there Remote Desktop to a WINDOWS PC inside the CERN network.
  • OR, use the CERN remote desktop gateway service (https://remotedesktop.web.cern.ch/remotedesktop/) to connect directly to a WINDOWS PC inside the CERN network.
  • OR, use ssh from windows, for instance with PuTTY or sons and do the same sequence of commands explained for linux.

 
Deleted:
<
<
Linux:
1) ssh -Y username@lxplusNOSPAMPLEASE.cern.ch (if you are not in the CERN gateway you can also tunnel via lxplus)
2) ssh -Y pclbrich02
3) source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh (from your home directory to avoid problems related to write permissions)
 

DB operations

Revision 272018-06-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

Deleted:
<
<

Inventory, Bookkeeping and Connectivity Database project

The large number of units, their test, qualification and calibration and their connectivity in Elementary Cells (EC), Photo-Detector Modules (PDM), columns and photo-detector assemblies motivated the development of an inventory and bookkeeping system to store and retrieve data.

The RICH Inventory, Bookkeeping and Connectivity Database (IBCDB) is an under development WinCC-OA project working as a user friendly DB for the RICH upgrade. The choice of WinCC-OA is mainly motivated by the scattered tools already provided by the JCOP framework. Moreover, this choice will make easier the integration of the DB with the upgraded LHCb ECS and the information exchange with the CondDB and the ConfDB.

The DB will provide the full detector inventory and bookkeeping, accounting for the hierarchical structure of all the sub-assemblies and for the changes in time of the composition of the assemblies and their calibration data. The DB will allow to take a snapshot of all detector data, retrieving all and only the data valid at a certain date-time. The main aim of the DB is to track the full history of every devices that will be used in the RICH detectors.

The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.

The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDMDB, PDM and Lens.

IBCDB setup instructions

The IBCDB project is running as an autostart service on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB

You can connect to the machine via ssh (first connect to lxplus if you are not based at CERN using the -Y option). To operate the database type (from your afs home directory to avoid writing permission problems)

source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh

 
Changed:
<
<
To stop the service connect on pclbrich02 with the lbrich account name and type: sudo systemctl stop lbRichUpgradeIBCDB

The service has been created using the following steps:
- the .lbRichUpgradeConf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:

[Unit]
Description=lbRichUpgradeIBCDB WinCC OA project

>
>

Inventory, Bookkeeping and Connectivity Database project

 
Changed:
<
<
[Service]
EnvironmentFile=/etc/.lbRichUpgradeIBCDBConf
ExecStart=/opt/WinCC_OA/3.15/bin/WCCILpmon $proj
>
>
The large number of units, their test, qualification and calibration and their connectivity in Elementary Cells (EC), Photo-Detector Modules (PDM), columns and photo-detector assemblies motivated the development of an inventory and bookkeeping system to store and retrieve data.
The RICH Inventory, Bookkeeping and Connectivity Database (IBCDB) is an under development WinCC-OA project working as a user friendly DB for the RICH upgrade. The choice of WinCC-OA is mainly motivated by the scattered tools already provided by the JCOP framework. Moreover, this choice will make easier the integration of the DB with the upgraded LHCb ECS and the information exchange with the standard LHCb databases.
The DB will provide the full detector inventory and bookkeeping, accounting for the hierarchical structure of all the sub-assemblies and for the changes in time of the composition of the assemblies and their calibration data. The DB will allow to take a snapshot of all detector data, retrieving all and only the data valid at a certain date-time. The main aim of the DB is to track the full history of every devices that will be used in the RICH detectors.
The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDMDB, PDM.
 
Changed:
<
<
[Install]
WantedBy=multi-user.target
>
>

How to connect to the database

 
Changed:
<
<
Follow the instruction at this this link to manage the service.
>
>
Linux:
1) ssh -Y username@lxplusNOSPAMPLEASE.cern.ch (if you are not in the CERN gateway you can also tunnel via lxplus)
2) ssh -Y pclbrich02
3) source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh (from your home directory to avoid problems related to write permissions)
 

DB operations

Changed:
<
<
The first thing to do is to select the device type you are interested for. Then you can choose between two modes of operations:

Hardware View: click this button if you want to insert new devices in the DB and/or to insert/update/retrieve test, calibration and setting data.

>
>
First select the device type. Then choose between two modes of operations:
Hardware View: click this button if you want to insert new devices in the DB and/or to insert/update/retrieve test, calibration and setting data.
Logical View: click this button if you want to insert/update/retrieve device locations.
 
Changed:
<
<
Logical View: click this button if you want to insert/update/retrieve device locations.

DBoperations.png

>
>
DBoperations.png
 

Hardware View

Changed:
<
<
You can change the selected device type clicking on the button at the top of the panel shown below. The panel could be slightly different with respect to the one shown in the attached image, since the functionality depend on the selected device type.

In the following sections you can get instructions to operate the different device types. To date, the MaPMT sector of the DB is the most advanced one, since we have to cope with the MaPMT production series and the quality assurance facilities already started to provide data.

>
>
You can change the selected device type clicking on the button at the top of the panel shown below. The panel could be slightly different with respect to the one shown in the attached image, since the functionality depend on the selected device type.
In the following sections you can get instructions to operate the different device types.
 
Changed:
<
<
HWview.png
>
>
hwView.png
 

MAPMT

Summary
Changed:
<
<
The Summary button opens a tree containing the serial numbers and the status of the MaPMTs inserted in the DB. There are three available status: NOT_READY (the MaPMT is not validated yet), READY (the MaPMT has been tested and validated) and BROKEN. Type a pattern in the Serial number filter text field at the top to make easier the search. Then click the green tick. Select the corresponding serial number and click on the Show selected button in order to retrieve MaPMT data.

SUMMARY.png

>
>
The Summary button opens a tree containing the serial numbers and the status of the MaPMTs inserted in the DB. There are three available status: NOT_READY (the MaPMT is not validated yet), READY (the MaPMT has been tested and validated) and BROKEN. Type a pattern in the Serial number filter text field at the top to make the search easier. Then click the green tick. Select the corresponding serial number and click on the Show selected button in order to retrieve MaPMT data.
 
Changed:
<
<
If no calibration data have been inserted yet, a message will appear.
>
>
summary.png
 
Changed:
<
<
Select the desired start of validity date in order to retrieve calibration data. The skeleton of the user interface that will be used to show MaPMT data is shown in the image below.
>
>
If no calibration data have been inserted yet, a message will appear. Select the desired start of validity date in order to retrieve calibration data. An example of the user interface showing the data for a MaPMT is shown in the image below.
 
Changed:
<
<
MaPMTdata.png
>
>
MaPMTdata.png
  The pixel data are accessible via the 64 buttons to the right of the panel. Clicking on one of these buttons it will appear a panel like the one shown below
Changed:
<
<
pixelData.png
>
>
pixelData.png
  It is also possible to access Datasheet, Test Infos and Quantum Efficiency data. The datasheet panel has a color code based on quality assurance facilities requirements to Hamamatsu.
Changed:
<
<
datasheet.png
>
>
datasheet.png
 
Create Devices
Line: 109 to 78
  export.png
Changed:
<
<

Lens

>
>

BaseBoard

 
Changed:
<
<
  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.
>
>

EC

 
Changed:
<
<
  • Create a Device : no datasheet informations are required.

  • Change Status : a table will be opened. Right click on the corresponding serial number and select the new device status.
>
>

PDM

 

Other devices

Line: 168 to 134
  A table with all allocated devices will appear. Select the devices you want to remove and click on Remove selected devices from their locations. A validation panel will appear. Insert all the informations and click Ok.
Added:
>
>

IBCDB technicalities

 
Changed:
<
<
-- GiovanniCavallero - 2015-11-19
>
>
The IBCDB project is running as an autostart service on the pclbrich02 CentOS 7 machine.
The WinCC 3.15 project name is lbRichUpgradeIBCDB and the project path is /localdisk/WinCC/lbRichUpgradeIBCDB.
The local git repository can be found in /home/Packages/git/ECS. The remote repository is at https://gitlab.cern.ch/LHCbRICHUpgrade/ECS.

To stop the service connect on pclbrich02 with the lbrich account name and type: sudo systemctl stop lbRichUpgradeIBCDB

The service has been created using the following steps:
- the .lbRichUpgradeConf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:

 
Added:
>
>
[Unit]
Description=lbRichUpgradeIBCDB WinCC OA project

[Service]
EnvironmentFile=/etc/.lbRichUpgradeIBCDBConf
ExecStart=/opt/WinCC_OA/3.15/bin/WCCILpmon $proj

[Install]
WantedBy=multi-user.target

Follow the instruction at this this link to manage the service.

-- GiovanniCavallero - 2015-11-19

 
META FILEATTACHMENT attachment="StartPanel.png" attr="" comment="" date="1447968937" name="StartPanel.png" path="StartPanel.png" size="44377" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMT.png" attr="" comment="" date="1447969161" name="MaPMT.png" path="MaPMT.png" size="30575" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMTval.png" attr="" comment="" date="1447969162" name="MaPMTval.png" path="MaPMTval.png" size="50055" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Logic.png" attr="" comment="" date="1447969162" name="Logic.png" path="Logic.png" size="30532" user="gcavalle" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="datasheet.png" attr="" comment="" date="1478796708" name="datasheet.png" path="datasheet.png" size="38183" user="gcavalle" version="2"
 
META FILEATTACHMENT attachment="logical.png" attr="" comment="" date="1466355455" name="logical.png" path="logical.png" size="46248" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBoperations.png" attr="" comment="" date="1478794779" name="DBoperations.png" path="DBoperations.png" size="47758" user="gcavalle" version="1"
META FILEATTACHMENT attachment="HWview.png" attr="" comment="" date="1478795532" name="HWview.png" path="HWview.png" size="22338" user="gcavalle" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="SUMMARY.png" attr="" comment="" date="1478795983" name="SUMMARY.png" path="SUMMARY.png" size="32692" user="gcavalle" version="1"
 
META FILEATTACHMENT attachment="MaPMTdata.png" attr="" comment="" date="1478796357" name="MaPMTdata.png" path="MaPMTdata.png" size="49602" user="gcavalle" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="pixelData.png" attr="" comment="" date="1478796465" name="pixelData.png" path="pixelData.png" size="31368" user="gcavalle" version="1"
 
META FILEATTACHMENT attachment="insertPMT.png" attr="" comment="" date="1478798409" name="insertPMT.png" path="insertPMT.png" size="15722" user="gcavalle" version="1"
META FILEATTACHMENT attachment="export.png" attr="" comment="" date="1478798938" name="export.png" path="export.png" size="20760" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBlogic.png" attr="" comment="" date="1478799312" name="DBlogic.png" path="DBlogic.png" size="21791" user="gcavalle" version="1"
META FILEATTACHMENT attachment="logicalHistory.png" attr="" comment="" date="1478799487" name="logicalHistory.png" path="logicalHistory.png" size="47003" user="gcavalle" version="1"
META FILEATTACHMENT attachment="deviceHistory.png" attr="" comment="" date="1478799669" name="deviceHistory.png" path="deviceHistory.png" size="40787" user="gcavalle" version="1"
META FILEATTACHMENT attachment="insertDev.png" attr="" comment="" date="1478799953" name="insertDev.png" path="insertDev.png" size="46821" user="gcavalle" version="1"
Added:
>
>
META FILEATTACHMENT attachment="startDB.png" attr="" comment="" date="1528185046" name="startDB.png" path="startDB.png" size="30870" user="gcavalle" version="1"
META FILEATTACHMENT attachment="hwView.png" attr="" comment="" date="1528185600" name="hwView.png" path="hwView.png" size="31393" user="gcavalle" version="1"
META FILEATTACHMENT attachment="summary.png" attr="" comment="" date="1528185669" name="summary.png" path="summary.png" size="87811" user="gcavalle" version="1"
META FILEATTACHMENT attachment="data.png" attr="" comment="" date="1528185767" name="data.png" path="data.png" size="95011" user="gcavalle" version="1"
META FILEATTACHMENT attachment="pixelData.png" attr="" comment="" date="1528186771" name="pixelData.png" path="pixelData.png" size="33405" user="gcavalle" version="1"
META FILEATTACHMENT attachment="datasheet.png" attr="" comment="" date="1528186771" name="datasheet.png" path="datasheet.png" size="70215" user="gcavalle" version="1"
META FILEATTACHMENT attachment="EC.png" attr="" comment="" date="1528186771" name="EC.png" path="EC.png" size="37262" user="gcavalle" version="1"
META FILEATTACHMENT attachment="exportData.png" attr="" comment="" date="1528186771" name="exportData.png" path="exportData.png" size="44282" user="gcavalle" version="1"
META FILEATTACHMENT attachment="moveDevices.png" attr="" comment="" date="1528186771" name="moveDevices.png" path="moveDevices.png" size="37945" user="gcavalle" version="1"

Revision 252018-01-18 - LhcbTestbeamSupportService

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 25 to 25
  To stop the service connect on pclbrich02 with the lbrich account name and type: sudo systemctl stop lbRichUpgradeIBCDB
Changed:
<
<
The service has been created using the following steps:
- the .lbRichUpgrade.Conf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:
>
>
The service has been created using the following steps:
- the .lbRichUpgradeConf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:
  [Unit]
Description=lbRichUpgradeIBCDB WinCC OA project

Revision 242017-12-28 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 19 to 19
  The IBCDB project is running as an autostart service on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
Changed:
<
<
You can connect to the machine via ssh (first connect to lxplus from outside of CERN using -Y option). To operate the database type (from your afs home directory to avoid possible writing permission problems)
>
>
You can connect to the machine via ssh (first connect to lxplus if you are not based at CERN using the -Y option). To operate the database type (from your afs home directory to avoid writing permission problems)
  source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh
Changed:
<
<
To stop the service connect on pclbrich02 and type: sudo systemctl stop lbRichUpgradeIBCDB
>
>
To stop the service connect on pclbrich02 with the lbrich account name and type: sudo systemctl stop lbRichUpgradeIBCDB
 
Changed:
<
<
To service has been created using the following steps:
- the .lbRichUpgrade.Conf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:
>
>
The service has been created using the following steps:
- the .lbRichUpgrade.Conf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:
  [Unit]
Description=lbRichUpgradeIBCDB WinCC OA project

Revision 232017-12-20 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 17 to 17
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
>
>
The IBCDB project is running as an autostart service on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
  You can connect to the machine via ssh (first connect to lxplus from outside of CERN using -Y option). To operate the database type (from your afs home directory to avoid possible writing permission problems)

source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh

Added:
>
>
To stop the service connect on pclbrich02 and type: sudo systemctl stop lbRichUpgradeIBCDB

To service has been created using the following steps:
- the .lbRichUpgrade.Conf file has been created in /etc containing: proj=-PROJ lbRichUpgradeIBCDB
- the .lbRichUpgradeIBCDB.service file has been created in /etc/systemd/system/ containing:

[Unit]
Description=lbRichUpgradeIBCDB WinCC OA project

[Service]
EnvironmentFile=/etc/.lbRichUpgradeConf
ExecStart=/opt/WinCC_OA/3.15/bin/WCCILpmon $proj

[Install]
WantedBy=multi-user.target

Follow the instruction at this this link to manage the service.

 

DB operations

The first thing to do is to select the device type you are interested for. Then you can choose between two modes of operations:

Revision 222017-09-12 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 19 to 19
  The IBCDB project is running on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
Changed:
<
<
You can connect to the machine via ssh (first connect to lxplus from outside of CERN). To operate the database type (from your afs home directory to avoid possible writing permission problems)
>
>
You can connect to the machine via ssh (first connect to lxplus from outside of CERN using -Y option). To operate the database type (from your afs home directory to avoid possible writing permission problems)
  source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh

Revision 212017-08-11 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 17 to 17
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
>
>
The IBCDB project is running on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
 
Changed:
<
<
You can connect to the machine via ssh. To operate the database type (from your afs home directory to avoid possible writing permission problems)
>
>
You can connect to the machine via ssh (first connect to lxplus from outside of CERN). To operate the database type (from your afs home directory to avoid possible writing permission problems)
  source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh

Revision 202017-08-01 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 17 to 17
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running on the pclbrich02 CentOS 7 machine. You can connect to the machine via ssh.
>
>
The IBCDB project is running on the pclbrich02 CentOS 7 machine. The WinCC 3.15 project name is lbRichUpgradeIBCDB. The project path is /home/WinCC/lbRichUpgradeIBCDB. The local git repository can be found in /home/Packages/git/lbRichUpgradeIBCDB. The remote repository is at https://gitlab.cern.ch/gcavalle/lbRichUpgradeIBCDB
 
Changed:
<
<
To operate the database type
>
>
You can connect to the machine via ssh. To operate the database type (from your afs home directory to avoid possible writing permission problems)
  source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh
Deleted:
<
<
from your home directory (/afs/cern.ch/user//).
 

DB operations

The first thing to do is to select the device type you are interested for. Then you can choose between two modes of operations:

Revision 192017-08-01 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 23 to 23
  source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh
Added:
>
>
from your home directory (/afs/cern.ch/user//).
 

DB operations

The first thing to do is to select the device type you are interested for. Then you can choose between two modes of operations:

Line: 74 to 76
  The automatic creation of MaPMTs, together with the insertion of their datasheet in the DB, is possible if you have the .csv datasheets list provided by Hamamatsu. The csv file must be comma separated!
Changed:
<
<
First specify the delivery lab and date. Click on the Select file button. By default the search will start in the C:/Users folder. Click on the Import button to complete MaPMTs insertion in the DB. Wait until the progress bar will close and then check if the MaPMTs are actually imported in the DB as described in the Summary section.
>
>
First specify the delivery batch lab, date and number. Click on the Select file button. By default the search will start in your afs home directory. Click on the Import button to complete MaPMTs insertion in the DB. Wait until the progress bar will close and then check if the MaPMTs are actually imported in the DB as described in the Summary section.
  A message of error will appear if there is at least one MaPMT already inserted in the DB. In that case none of the devices in the list will be imported.
Changed:
<
<
Of course you could also create and import the datasheet of a single MaPMT by hand, clicking on the Import values by hand button.
>
>
You may also create and import the datasheet of a single MaPMT by hand, clicking on the Import values by hand button.
  insertPMT.png
Line: 90 to 91
 
Insert/Update Device Properties
Changed:
<
<
Select MAPMT as the default device type. Click on Start Hardware View and then click the Insert/Update Device properties button. To import data from a file, click Import MaPMTs load measurements, select the file you want to import and click Import. A popup panel will open to show the serial numbers of the MaPMTs you want to import and if some MaPMTs already have the calibration data. If some PMTs are not present in the DB, an error message will appear asking you to create first that MaPMTs. Click the Continue button to confirm the data import, or the Abort button to not import data.
>
>
Select MAPMT as the default device type. Click on Start Hardware View and then click the Insert/Update Device properties button. To import data from a file, click Import MaPMTs load measurements, select the file you want to import and click Import. By default the search will start in your afs home directory. A popup panel will open to show the serial numbers of the MaPMTs you want to import and if some MaPMTs already have the calibration data. If some PMTs are not present in the DB, an error message will appear asking you to create first that MaPMTs. Click the Continue button to confirm the data import, or the Abort button to not import data.
 
Export data

Revision 182017-08-01 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 90 to 90
 
Insert/Update Device Properties
Changed:
<
<
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties button.

A UI similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.

>
>
Select MAPMT as the default device type. Click on Start Hardware View and then click the Insert/Update Device properties button. To import data from a file, click Import MaPMTs load measurements, select the file you want to import and click Import. A popup panel will open to show the serial numbers of the MaPMTs you want to import and if some MaPMTs already have the calibration data. If some PMTs are not present in the DB, an error message will appear asking you to create first that MaPMTs. Click the Continue button to confirm the data import, or the Abort button to not import data.
 
Export data

Revision 172017-08-01 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 13 to 13
  The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.
Changed:
<
<
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDM and Lens.
>
>
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDMDB, PDM and Lens.
 

IBCDB setup instructions

Line: 21 to 21
  To operate the database type
Changed:
<
<
source /home/Packages/lbRichUpgradeIBCDB/start_IBCDB.sh
>
>
source /home/Packages/lbRichUpgradeIBCDB/lbRichUpgradeIBCDB.sh
 

DB operations

Revision 162017-07-31 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 17 to 17
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running as a service on the PCCAZ8007 Windows Server at CERN. You can connect to the machine through a remote desktop connection. You should have the start_IBCDB shortcut on your desktop.
>
>
The IBCDB project is running on the pclbrich02 CentOS 7 machine. You can connect to the machine via ssh.
 
Changed:
<
<
If not, you need to copy the following command in the text field "type the location of the item" during the shortcut creation:
>
>
To operate the database type
 
Changed:
<
<
C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:18998 -data PCCAZ8007:18897 -config D:\WinCC\RICH_UPGRADE-IBCDB-v2\config\config -p lbRichDB/_lbRichDB_operations.pnl

Click next, type the name you want for the shortcut and click finish.

Double-click on the shortcut to start the database operations.

IBCDB remote access instructions

  • Windows flavour
    • start Remote Desktop Connection on your local machine
      • Computer: cernts.cern.ch (Domain: CERN)
      • CERN username and passwords
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

  • Linux flavour: type the following command in the terminal to start the Remote Desktop Connection:
    • rdesktop -u user -d CERN -g 1800x1200 cernts.cern.ch (change "1800x1200" to fit the size of your screen, or replace "-g 1800x1200" with "-f" for the full screen view (ctrl+alt+enter to exit the full screen view). Replace "user" with your CERN username)
    • type your CERN password
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

>
>
source /home/Packages/lbRichUpgradeIBCDB/start_IBCDB.sh
 

DB operations

Revision 152016-11-10 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

Changed:
<
<

What is the Inventory, Bookkeeping and Connectivity Database project?

>
>

Inventory, Bookkeeping and Connectivity Database project

 
Changed:
<
<
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (setting, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes of device data and locations. It will contain the connectivity between RICH sub-assemblies.
>
>
The large number of units, their test, qualification and calibration and their connectivity in Elementary Cells (EC), Photo-Detector Modules (PDM), columns and photo-detector assemblies motivated the development of an inventory and bookkeeping system to store and retrieve data.

The RICH Inventory, Bookkeeping and Connectivity Database (IBCDB) is an under development WinCC-OA project working as a user friendly DB for the RICH upgrade. The choice of WinCC-OA is mainly motivated by the scattered tools already provided by the JCOP framework. Moreover, this choice will make easier the integration of the DB with the upgraded LHCb ECS and the information exchange with the CondDB and the ConfDB.

The DB will provide the full detector inventory and bookkeeping, accounting for the hierarchical structure of all the sub-assemblies and for the changes in time of the composition of the assemblies and their calibration data. The DB will allow to take a snapshot of all detector data, retrieving all and only the data valid at a certain date-time. The main aim of the DB is to track the full history of every devices that will be used in the RICH detectors.

The DB provides the hardware information and location of each device. It is the central database to store and retrieve data provided by the quality assurance facilities. It is the main source of information to select and group devices, in order to cope with the assembly of the EC and PDM. It allows the multi-user access, with access control and logging of date-time and user for any transaction.

The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, EC, PDM and Lens.

 

IBCDB setup instructions

Line: 48 to 56
 

DB operations

Changed:
<
<
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens, HVPS and LVPS. Select the device type you want to work with (you can change it during operations). At this point you can choose between two modes of operations:
>
>
The first thing to do is to select the device type you are interested for. Then you can choose between two modes of operations:
  Hardware View: click this button if you want to insert new devices in the DB and/or to insert/update/retrieve test, calibration and setting data.

Logical View: click this button if you want to insert/update/retrieve device locations.

Changed:
<
<
DBoperations.png
>
>
DBoperations.png
 

Hardware View

Changed:
<
<
You can change the selected device type clicking on the button at the top of the panel. The functionality depend on the device type and so this panel is slightly different from one device type to the other.
>
>
You can change the selected device type clicking on the button at the top of the panel shown below. The panel could be slightly different with respect to the one shown in the attached image, since the functionality depend on the selected device type.
 
Changed:
<
<
In the following sections you can get instructions to operate MAPMTs, Lens and other device types.
>
>
In the following sections you can get instructions to operate the different device types. To date, the MaPMT sector of the DB is the most advanced one, since we have to cope with the MaPMT production series and the quality assurance facilities already started to provide data.
 
Changed:
<
<
HWview.png
>
>
HWview.png
 

MAPMT

Summary
Changed:
<
<
The Summary button opens a tree containing the serial number and the status of the MaPMTs currently in the DB. To make easier the search, type a pattern in the Serial number filter text field at the top, then click the green tick. Select the corresponding serial number and click on the Show selected button in order to retrieve MaPMT data.
>
>
The Summary button opens a tree containing the serial numbers and the status of the MaPMTs inserted in the DB. There are three available status: NOT_READY (the MaPMT is not validated yet), READY (the MaPMT has been tested and validated) and BROKEN. Type a pattern in the Serial number filter text field at the top to make easier the search. Then click the green tick. Select the corresponding serial number and click on the Show selected button in order to retrieve MaPMT data.
 
Changed:
<
<
SUMMARY.png
>
>
SUMMARY.png
 
Changed:
<
<
If no values have been inserted, a message will appear.
>
>
If no calibration data have been inserted yet, a message will appear.
 
Changed:
<
<
Select the desired start of validity date in order to retrieve calibration data. It is also possible to access Datasheet, Test Infos and Quantum Efficiency data.
>
>
Select the desired start of validity date in order to retrieve calibration data. The skeleton of the user interface that will be used to show MaPMT data is shown in the image below.

MaPMTdata.png

The pixel data are accessible via the 64 buttons to the right of the panel. Clicking on one of these buttons it will appear a panel like the one shown below

pixelData.png

 
Changed:
<
<
datasheet.png
>
>
It is also possible to access Datasheet, Test Infos and Quantum Efficiency data. The datasheet panel has a color code based on quality assurance facilities requirements to Hamamatsu.

datasheet.png

 
Create Devices
Changed:
<
<
This button allows to insert MaPMTs in the DB. All you need is the Hamamatsu .csv datasheets copied in a location accessible by PCCAZ8007, i.e. your AFS workspace.
>
>
This button allows to insert MaPMTs in the DB.

The automatic creation of MaPMTs, together with the insertion of their datasheet in the DB, is possible if you have the .csv datasheets list provided by Hamamatsu. The csv file must be comma separated!

 
Changed:
<
<
Select the delivery location and the date. Click on Select file button. By default the search will start in your AFS directory. Click on the Import button to finish device insertions.
>
>
First specify the delivery lab and date. Click on the Select file button. By default the search will start in the C:/Users folder. Click on the Import button to complete MaPMTs insertion in the DB. Wait until the progress bar will close and then check if the MaPMTs are actually imported in the DB as described in the Summary section.
 
Changed:
<
<
A message of error will appear if there is at least one MaPMT already inserted in the DB. In that case no devices will be imported.
>
>
A message of error will appear if there is at least one MaPMT already inserted in the DB. In that case none of the devices in the list will be imported.
 
Changed:
<
<
insertPMT.png
>
>
Of course you could also create and import the datasheet of a single MaPMT by hand, clicking on the Import values by hand button.

insertPMT.png

 
Change Status, Quality Flag
Changed:
<
<
Click this button to change MaPMT properties like status and quality flag. Right-click on the corresponding serial number and select the value you want to change.
>
>
Click this button to change MaPMT properties like status and quality flag. Right-click on the corresponding serial number and select the value you want to change. The available status are described in the Summary section and are NOT_READY, READY and BROKEN. The quality flag is a feature to group and easily identify high and low quality MaPMTs.
 
Insert/Update Device Properties
Line: 108 to 129
  Click to export data to a .txt file. First you have to select the data type to export (so far only Datasheet export is implemented). Transfer the serial numbers to the right table clicking on the button with the arrow. Click Export data. The file will appear in your AFS home directory.
Changed:
<
<
export.png
>
>
export.png
 

Lens

  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.
Changed:
<
<
  • Create a Device : see here. No datasheet informations are required.
>
>
  • Create a Device : no datasheet informations are required.
 
  • Change Status : a table will be opened. Right click on the corresponding serial number and select the new device status.
Line: 132 to 153
 

Logical View

Changed:
<
<
logical.png
>
>
DBlogic.png
 

Search by device type

Changed:
<
<
Click to see current device locations of the selected type. To retrieve the device location history, with interval of validity date, select the corresponding row and click on the See device history button.
>
>
Click to see current device locations of the selected type.

logicalHistory.png

To retrieve the device location history, with interval of validity date, select the corresponding row and click on the See device history button.

deviceHistory.png

 

Search by location

Line: 146 to 173
 
  • TestBeam : First select the testbeam date. Then navigate down through the hardware structure to show devices of the selected device type installed in the corresponding location.
Changed:
<
<
DBlogic.png
>
>

Insert Devices

A table with all devices not yet allocated will appear. If the wanted device does not appear, it means either that the device have not been yet inserted in the DB or it is located somewhere else (see Remove Devices).

 
Deleted:
<
<

Insert a Device into a location

 
Changed:
<
<
A table with all devices not yet allocated will appear. If the wanted device does not appear, it means either that the device have not been yet inserted in the DB or it is located somewhere else (see Remove a Device from a location).
>
>
insertDev.png
 
Changed:
<
<
Select the devices, the location type and click Ok.
>
>
Multiple selections are allowed only for the Lab location type. Select the devices, the location type and click Ok.
 
Changed:
<
<
  • LAB: a validation panel will appear. Insert all the informations and click Ok. You return to the previous panel. Click on the refresh button to the bottom left and check that the device just inserted is not in the table anymore.
>
>
  • LAB: a validation panel will appear. Insert all the informations and click Ok.
 
  • TestBeam : Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status). First select the testbeam date. Then navigate through to the hardware structure and click on the desired location. A validation panel will appear. Insert all the informations and click Ok.
Line: 170 to 198
 
META FILEATTACHMENT attachment="MaPMT.png" attr="" comment="" date="1447969161" name="MaPMT.png" path="MaPMT.png" size="30575" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMTval.png" attr="" comment="" date="1447969162" name="MaPMTval.png" path="MaPMTval.png" size="50055" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Logic.png" attr="" comment="" date="1447969162" name="Logic.png" path="Logic.png" size="30532" user="gcavalle" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="Datasheet.png" attr="" comment="" date="1447969163" name="Datasheet.png" path="Datasheet.png" size="32075" user="gcavalle" version="1"
META FILEATTACHMENT attachment="datasheet.png" attr="" comment="" date="1466351123" name="datasheet.png" path="datasheet.png" size="68755" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBlogic.png" attr="" comment="" date="1466351123" name="DBlogic.png" path="DBlogic.png" size="86051" user="gcavalle" version="1"
META FILEATTACHMENT attachment="SUMMARY.png" attr="" comment="" date="1466351123" name="SUMMARY.png" path="SUMMARY.png" size="64123" user="gcavalle" version="1"
META FILEATTACHMENT attachment="export.png" attr="" comment="" date="1466351123" name="export.png" path="export.png" size="46062" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBoperations.png" attr="" comment="" date="1466351123" name="DBoperations.png" path="DBoperations.png" size="42733" user="gcavalle" version="1"
META FILEATTACHMENT attachment="HWview.png" attr="" comment="" date="1466351123" name="HWview.png" path="HWview.png" size="37134" user="gcavalle" version="1"
META FILEATTACHMENT attachment="insertPMT.png" attr="" comment="" date="1466351123" name="insertPMT.png" path="insertPMT.png" size="42449" user="gcavalle" version="1"
>
>
META FILEATTACHMENT attachment="datasheet.png" attr="" comment="" date="1478796708" name="datasheet.png" path="datasheet.png" size="38183" user="gcavalle" version="2"
 
META FILEATTACHMENT attachment="logical.png" attr="" comment="" date="1466355455" name="logical.png" path="logical.png" size="46248" user="gcavalle" version="1"
Added:
>
>
META FILEATTACHMENT attachment="DBoperations.png" attr="" comment="" date="1478794779" name="DBoperations.png" path="DBoperations.png" size="47758" user="gcavalle" version="1"
META FILEATTACHMENT attachment="HWview.png" attr="" comment="" date="1478795532" name="HWview.png" path="HWview.png" size="22338" user="gcavalle" version="1"
META FILEATTACHMENT attachment="SUMMARY.png" attr="" comment="" date="1478795983" name="SUMMARY.png" path="SUMMARY.png" size="32692" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMTdata.png" attr="" comment="" date="1478796357" name="MaPMTdata.png" path="MaPMTdata.png" size="49602" user="gcavalle" version="1"
META FILEATTACHMENT attachment="pixelData.png" attr="" comment="" date="1478796465" name="pixelData.png" path="pixelData.png" size="31368" user="gcavalle" version="1"
META FILEATTACHMENT attachment="insertPMT.png" attr="" comment="" date="1478798409" name="insertPMT.png" path="insertPMT.png" size="15722" user="gcavalle" version="1"
META FILEATTACHMENT attachment="export.png" attr="" comment="" date="1478798938" name="export.png" path="export.png" size="20760" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBlogic.png" attr="" comment="" date="1478799312" name="DBlogic.png" path="DBlogic.png" size="21791" user="gcavalle" version="1"
META FILEATTACHMENT attachment="logicalHistory.png" attr="" comment="" date="1478799487" name="logicalHistory.png" path="logicalHistory.png" size="47003" user="gcavalle" version="1"
META FILEATTACHMENT attachment="deviceHistory.png" attr="" comment="" date="1478799669" name="deviceHistory.png" path="deviceHistory.png" size="40787" user="gcavalle" version="1"
META FILEATTACHMENT attachment="insertDev.png" attr="" comment="" date="1478799953" name="insertDev.png" path="insertDev.png" size="46821" user="gcavalle" version="1"

Revision 142016-11-10 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

What is the Inventory, Bookkeeping and Connectivity Database project?

Changed:
<
<
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes of device data and locations. It will contain the connectivity between RICH sub-assemblies.
>
>
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (setting, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes of device data and locations. It will contain the connectivity between RICH sub-assemblies.
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running as a service on the PCCAZ8007 machine at CERN. You can connect to the machine through a remote desktop connection. You should have the start_IBCDB shortcut on your desktop.
>
>
The IBCDB project is running as a service on the PCCAZ8007 Windows Server at CERN. You can connect to the machine through a remote desktop connection. You should have the start_IBCDB shortcut on your desktop.
  If not, you need to copy the following command in the text field "type the location of the item" during the shortcut creation:
Line: 19 to 19
  Double-click on the shortcut to start the database operations.
Added:
>
>

IBCDB remote access instructions

  • Windows flavour
    • start Remote Desktop Connection on your local machine
      • Computer: cernts.cern.ch (Domain: CERN)
      • CERN username and passwords
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

  • Linux flavour: type the following command in the terminal to start the Remote Desktop Connection:
    • rdesktop -u user -d CERN -g 1800x1200 cernts.cern.ch (change "1800x1200" to fit the size of your screen, or replace "-g 1800x1200" with "-f" for the full screen view (ctrl+alt+enter to exit the full screen view). Replace "user" with your CERN username)
    • type your CERN password
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

 

DB operations

The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens, HVPS and LVPS. Select the device type you want to work with (you can change it during operations). At this point you can choose between two modes of operations:

Line: 135 to 162
  A table with all allocated devices will appear. Select the devices you want to remove and click on Remove selected devices from their locations. A validation panel will appear. Insert all the informations and click Ok.
Deleted:
<
<

IBCDB remote access instructions

  • Win flavour
    • start Remote Desktop Connection on your local machine
      • Computer: cernts.cern.ch (Domain: CERN)
      • CERN username and passwords
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

  • Linux flavour: type the following commands using the terminal:
    • rdesktop -u -d CERN -g 1800x1200 cernts.cern.ch (change 1800x1200 with the dimension of your screen and with your CERN username)
    • type your CERN password
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

  -- GiovanniCavallero - 2015-11-19

Revision 132016-10-20 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 146 to 146
 
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
Added:
>
>
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

  • Linux flavour: type the following commands using the terminal:
    • rdesktop -u -d CERN -g 1800x1200 cernts.cern.ch (change 1800x1200 with the dimension of your screen and with your CERN username)
    • type your CERN password
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
 
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon

Revision 122016-10-20 - AlessandroBertolin

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 137 to 137
 
Changed:
<
<
-- GiovanniCavallero - 2015-11-19

>
>

IBCDB remote access instructions

 
Added:
>
>
  • Win flavour
    • start Remote Desktop Connection on your local machine
      • Computer: cernts.cern.ch (Domain: CERN)
      • CERN username and passwords
    • once connected to cernts.cern.ch
      • start Remote Desktop Connection
      • Computer: pccaz8007
      • CERN username and passwords (you must ask for access to pccaz8007)
      • start the db using the start_IBCDB icon
 
Added:
>
>
 
Added:
>
>
-- GiovanniCavallero - 2015-11-19
 

META FILEATTACHMENT attachment="StartPanel.png" attr="" comment="" date="1447968937" name="StartPanel.png" path="StartPanel.png" size="44377" user="gcavalle" version="1"

Revision 112016-10-17 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

What is the Inventory, Bookkeeping and Connectivity Database project?

Changed:
<
<
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices measured data and their locations. It will contain the connectivity between RICH sub-assemblies.
>
>
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes of device data and locations. It will contain the connectivity between RICH sub-assemblies.
 

IBCDB setup instructions

The IBCDB project is running as a service on the PCCAZ8007 machine at CERN. You can connect to the machine through a remote desktop connection. You should have the start_IBCDB shortcut on your desktop.

Changed:
<
<
If not need copy the following command in the text field "type the location of the item" when you create the shortcut:
>
>
If not, you need to copy the following command in the text field "type the location of the item" during the shortcut creation:
  C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:18998 -data PCCAZ8007:18897 -config D:\WinCC\RICH_UPGRADE-IBCDB-v2\config\config -p lbRichDB/_lbRichDB_operations.pnl
Line: 32 to 32
 

Hardware View

Changed:
<
<
You can change the selected device type clicking on the top button. Since the functionalities differ depending on the device type, this panel is slightly different from one device type to the other.
>
>
You can change the selected device type clicking on the button at the top of the panel. The functionality depend on the device type and so this panel is slightly different from one device type to the other.
  In the following sections you can get instructions to operate MAPMTs, Lens and other device types.
Line: 43 to 43
 
Summary
Changed:
<
<
The Summary button opens a tree containing the serial number and the status of the MaPMTs currently in the DB. To make easier the search, type a pattern in the Serial number filter text field at the top. To retrieve data of a MaPMT select the corresponding serial number and click on the Show selected button.
>
>
The Summary button opens a tree containing the serial number and the status of the MaPMTs currently in the DB. To make easier the search, type a pattern in the Serial number filter text field at the top, then click the green tick. Select the corresponding serial number and click on the Show selected button in order to retrieve MaPMT data.
  SUMMARY.png
Changed:
<
<
A panel will open with the corresponding MaPMT data. If no values have been inserted, a message will appear.
>
>
If no values have been inserted, a message will appear.
 
Changed:
<
<
To retrieve calibration data select the desired start of validity date. To the left there are Datasheet, Test Infos and Quantum Efficiency buttons. Click to see the corresponding data, i.e.
>
>
Select the desired start of validity date in order to retrieve calibration data. It is also possible to access Datasheet, Test Infos and Quantum Efficiency data.
  datasheet.png

Create Devices
Changed:
<
<
This button allows to insert MaPMTs in the DB. All you need is the Hamamatsu .csv datasheets.
>
>
This button allows to insert MaPMTs in the DB. All you need is the Hamamatsu .csv datasheets copied in a location accessible by PCCAZ8007, i.e. your AFS workspace.
 
Changed:
<
<
Select the delivery location, date and who is writing. Click on Select file button. By default the script will search in your AFS directory. Click on the Import button to finish devices insertion.
>
>
Select the delivery location and the date. Click on Select file button. By default the search will start in your AFS directory. Click on the Import button to finish device insertions.
 
Changed:
<
<
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the DB. In that case devices will not be imported.
>
>
A message of error will appear if there is at least one MaPMT already inserted in the DB. In that case no devices will be imported.
  insertPMT.png

Change Status, Quality Flag
Changed:
<
<
Click this button to change one of these MaPMT properties. Right-click on the corresponding serial number and select the value you want to change.
>
>
Click this button to change MaPMT properties like status and quality flag. Right-click on the corresponding serial number and select the value you want to change.
 
Insert/Update Device Properties

Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties button.

Changed:
<
<
A panel similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.
>
>
A UI similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.
 
Export data
Line: 109 to 109
 

Search by device type

Changed:
<
<
Click to see current locations of devices of the selected type. To retrieve the device location history, with interval of validity date, select the corresponding row and click on the See device history button.
>
>
Click to see current device locations of the selected type. To retrieve the device location history, with interval of validity date, select the corresponding row and click on the See device history button.
 

Search by location

Revision 102016-07-02 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 9 to 9
 

IBCDB setup instructions

Changed:
<
<
The IBCDB project is running as a service on the PCCAZ8007 machine at CERN. You can connect to the machine through a remote desktop connection. You need the IBCDB shortcut on your desktop to start DB operations. Copy the following command in the text field "type the location of the item" when you create the shortcut:
>
>
The IBCDB project is running as a service on the PCCAZ8007 machine at CERN. You can connect to the machine through a remote desktop connection. You should have the start_IBCDB shortcut on your desktop.

If not need copy the following command in the text field "type the location of the item" when you create the shortcut:

  C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:18998 -data PCCAZ8007:18897 -config D:\WinCC\RICH_UPGRADE-IBCDB-v2\config\config -p lbRichDB/_lbRichDB_operations.pnl

Revision 92016-06-19 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

What is the Inventory, Bookkeeping and Connectivity Database project?

Changed:
<
<
The Inventory, Bookkeeping and Connectivity Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices measured data and their locations. It will contain the connectivity between RICH sub-assemblies.
>
>
The Inventory, Bookkeeping and Connectivity DataBase (IBCDB) is an under development WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices measured data and their locations. It will contain the connectivity between RICH sub-assemblies.
 

IBCDB setup instructions

Changed:
<
<
Start a remote desktop connection to the pccaz8007 machine at CERN. Right-click on your desktop, select new->shortcut. Copy the following rows in the text field "type the location of the item":
>
>
The IBCDB project is running as a service on the PCCAZ8007 machine at CERN. You can connect to the machine through a remote desktop connection. You need the IBCDB shortcut on your desktop to start DB operations. Copy the following command in the text field "type the location of the item" when you create the shortcut:
  C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:18998 -data PCCAZ8007:18897 -config D:\WinCC\RICH_UPGRADE-IBCDB-v2\config\config -p lbRichDB/_lbRichDB_operations.pnl
Line: 19 to 19
 

DB operations

Changed:
<
<
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens. The available functionalities depends on the selected device type.
>
>
The DB structure is based on device types. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens, HVPS and LVPS. Select the device type you want to work with (you can change it during operations). At this point you can choose between two modes of operations:
 
Changed:
<
<
Then the following panel will appear:
>
>
Hardware View: click this button if you want to insert new devices in the DB and/or to insert/update/retrieve test, calibration and setting data.
 
Changed:
<
<
StartPanel.png
>
>
Logical View: click this button if you want to insert/update/retrieve device locations.
 
Changed:
<
<
The Hardware View button triggers a series of WinCC-OA panels which aim is to guide you to insert new devices in the DB and to insert/update/retrieve test, calibration and setting data.

The Logical View button triggers a series of WinCC-OA panels that allow you to insert/update/retrieve device locations at any time.

>
>
DBoperations.png
 

Hardware View

Changed:
<
<
You can change the selected device type clicking on the button at the top.
>
>
You can change the selected device type clicking on the top button. Since the functionalities differ depending on the device type, this panel is slightly different from one device type to the other.
 
Changed:
<
<

MAPMT

>
>
In the following sections you can get instructions to operate MAPMTs, Lens and other device types.

HWview.png

 
Changed:
<
<
MaPMT.png
>
>

MAPMT

 
Summary
Changed:
<
<
Click this button to retrieve data. A table with all the MaPMTs inserted in the DB will appear.
>
>
The Summary button opens a tree containing the serial number and the status of the MaPMTs currently in the DB. To make easier the search, type a pattern in the Serial number filter text field at the top. To retrieve data of a MaPMT select the corresponding serial number and click on the Show selected button.
 
Changed:
<
<
For each MAPMT the table contains Serial Number, status, Quality Flag, Gain, k-Factor and Dark Counts columns (gain and dark counts are the values at nominal HV and illumination calibration conditions).
>
>
SUMMARY.png
 
Changed:
<
<
To retrieve data of a MAPMT select the corresponding row and click on the Show selected Device properties button. The following panel will open
>
>
A panel will open with the corresponding MaPMT data. If no values have been inserted, a message will appear.
 
Changed:
<
<
MaPMTval.png
>
>
  To retrieve calibration data select the desired start of validity date. To the left there are Datasheet, Test Infos and Quantum Efficiency buttons. Click to see the corresponding data, i.e.
Changed:
<
<
Datasheet.png
>
>
datasheet.png
 
Create Devices
Changed:
<
<
This button allows to insert multiple MaPMTs at the same time. All you need is the Hamamatsu .csv files containing a series of datasheet.
>
>
This button allows to insert MaPMTs in the DB. All you need is the Hamamatsu .csv datasheets.
 
Changed:
<
<
First you have to browse to search the csv file (you could copy it for example in one of your AFS directory), then select the delivery location and date, click import and you have done!
>
>
Select the delivery location, date and who is writing. Click on Select file button. By default the script will search in your AFS directory. Click on the Import button to finish devices insertion.
 
Changed:
<
<
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the database. In that case the file will not be imported.
>
>
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the DB. In that case devices will not be imported.
 
Changed:
<
<
Change Device Status, k-Factor, Quality Flag
>
>
insertPMT.png

Change Status, Quality Flag
 

Click this button to change one of these MaPMT properties. Right-click on the corresponding serial number and select the value you want to change.

Insert/Update Device Properties
Changed:
<
<
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties.
>
>
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties button.
  A panel similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.
Added:
>
>
Export data

Click to export data to a .txt file. First you have to select the data type to export (so far only Datasheet export is implemented). Transfer the serial numbers to the right table clicking on the button with the arrow. Click Export data. The file will appear in your AFS home directory.

export.png

 

Lens

Added:
>
>
 
  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.
Line: 94 to 103
 

Logical View

Changed:
<
<
Logic.png
>
>
logical.png
 

Search by device type

Line: 108 to 117
 
  • TestBeam : First select the testbeam date. Then navigate down through the hardware structure to show devices of the selected device type installed in the corresponding location.
Added:
>
>
DBlogic.png
 

Insert a Device into a location

A table with all devices not yet allocated will appear. If the wanted device does not appear, it means either that the device have not been yet inserted in the DB or it is located somewhere else (see Remove a Device from a location).

Changed:
<
<
Select the device, the location type and click Ok.
>
>
Select the devices, the location type and click Ok.
 
  • LAB: a validation panel will appear. Insert all the informations and click Ok. You return to the previous panel. Click on the refresh button to the bottom left and check that the device just inserted is not in the table anymore.
Line: 120 to 131
 

Remove a Device from a location

Changed:
<
<
A table with all allocated devices will appear. Select the device you want to remove and click on Remove selected device from its location. A validation panel will appear. Insert all the informations and click Ok.
>
>
A table with all allocated devices will appear. Select the devices you want to remove and click on Remove selected devices from their locations. A validation panel will appear. Insert all the informations and click Ok.
 
Line: 139 to 150
 
META FILEATTACHMENT attachment="MaPMTval.png" attr="" comment="" date="1447969162" name="MaPMTval.png" path="MaPMTval.png" size="50055" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Logic.png" attr="" comment="" date="1447969162" name="Logic.png" path="Logic.png" size="30532" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Datasheet.png" attr="" comment="" date="1447969163" name="Datasheet.png" path="Datasheet.png" size="32075" user="gcavalle" version="1"
Added:
>
>
META FILEATTACHMENT attachment="datasheet.png" attr="" comment="" date="1466351123" name="datasheet.png" path="datasheet.png" size="68755" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBlogic.png" attr="" comment="" date="1466351123" name="DBlogic.png" path="DBlogic.png" size="86051" user="gcavalle" version="1"
META FILEATTACHMENT attachment="SUMMARY.png" attr="" comment="" date="1466351123" name="SUMMARY.png" path="SUMMARY.png" size="64123" user="gcavalle" version="1"
META FILEATTACHMENT attachment="export.png" attr="" comment="" date="1466351123" name="export.png" path="export.png" size="46062" user="gcavalle" version="1"
META FILEATTACHMENT attachment="DBoperations.png" attr="" comment="" date="1466351123" name="DBoperations.png" path="DBoperations.png" size="42733" user="gcavalle" version="1"
META FILEATTACHMENT attachment="HWview.png" attr="" comment="" date="1466351123" name="HWview.png" path="HWview.png" size="37134" user="gcavalle" version="1"
META FILEATTACHMENT attachment="insertPMT.png" attr="" comment="" date="1466351123" name="insertPMT.png" path="insertPMT.png" size="42449" user="gcavalle" version="1"
META FILEATTACHMENT attachment="logical.png" attr="" comment="" date="1466355455" name="logical.png" path="logical.png" size="46248" user="gcavalle" version="1"

Revision 82016-02-29 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 9 to 9
 

IBCDB setup instructions

Changed:
<
<
Start a remote desktop connection to the pccaz8007 machine at CERN. Right-click on your desktop, select new->shortcut. In the text field type the location of the item as
>
>
Start a remote desktop connection to the pccaz8007 machine at CERN. Right-click on your desktop, select new->shortcut. Copy the following rows in the text field "type the location of the item":
 
Changed:
<
<
C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:16998 -data PCCAZ8007:16897 -config D:\WinCC\RICH_UPGRADE-IBCDB\config\config -p lbRichDB/_lbRichDB_operations.pnl
>
>
C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:18998 -data PCCAZ8007:18897 -config D:\WinCC\RICH_UPGRADE-IBCDB-v2\config\config -p lbRichDB/_lbRichDB_operations.pnl
  Click next, type the name you want for the shortcut and click finish.

Revision 72016-02-29 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

What is the Inventory, Bookkeeping and Connectivity Database project?

Changed:
<
<
The Inventory, Bookkeeping and Connectivity Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices data and locations.
>
>
The Inventory, Bookkeeping and Connectivity Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices measured data and their locations. It will contain the connectivity between RICH sub-assemblies.
 

IBCDB setup instructions

Changed:
<
<
Start a remote desktop connection to the pccaz8007 machine at CERN. Right click on your desktop, select new->shortcut. In the text field type the location of the item as
>
>
Start a remote desktop connection to the pccaz8007 machine at CERN. Right-click on your desktop, select new->shortcut. In the text field type the location of the item as
  C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:16998 -data PCCAZ8007:16897 -config D:\WinCC\RICH_UPGRADE-IBCDB\config\config -p lbRichDB/_lbRichDB_operations.pnl
Line: 25 to 25
  StartPanel.png
Changed:
<
<
Click the Hardware View button to start a series of WinCC-OA panels that allow you to insert new devices in the DB and to insert/update/retrieve test, calibration and setting data.
>
>
The Hardware View button triggers a series of WinCC-OA panels which aim is to guide you to insert new devices in the DB and to insert/update/retrieve test, calibration and setting data.
 
Changed:
<
<
Click the Logical View button to start a series of WinCC-OA panels that allow you to insert/update/retrieve device locations at any time.
>
>
The Logical View button triggers a series of WinCC-OA panels that allow you to insert/update/retrieve device locations at any time.
 

Hardware View

Line: 40 to 40
 
Summary
Changed:
<
<
Click this button to retrieve data. A table appears with all the MAPMTs contained in the DB.
>
>
Click this button to retrieve data. A table with all the MaPMTs inserted in the DB will appear.
  For each MAPMT the table contains Serial Number, status, Quality Flag, Gain, k-Factor and Dark Counts columns (gain and dark counts are the values at nominal HV and illumination calibration conditions).
Line: 58 to 58
  This button allows to insert multiple MaPMTs at the same time. All you need is the Hamamatsu .csv files containing a series of datasheet.
Changed:
<
<
First you have to browse to search the csv file, then select the delivery location and date, click import and you have done!
>
>
First you have to browse to search the csv file (you could copy it for example in one of your AFS directory), then select the delivery location and date, click import and you have done!
 
Changed:
<
<
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the database. In this case the file will not be imported.
>
>
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the database. In that case the file will not be imported.
 
Change Device Status, k-Factor, Quality Flag
Line: 69 to 69
 
Insert/Update Device Properties
Changed:
<
<
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties.
>
>
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties.
  A panel similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.

Lens

Changed:
<
<
  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.
>
>
  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.
 
  • Create a Device : see here. No datasheet informations are required.
Line: 106 to 106
 
  • LAB : select the LAB and click on the See location history button. A table with the devices of the device type selected at the beginning will appear.
Changed:
<
<
  • TestBeam : First select the testbeam date. Then navigate down to the hardware level to show devices of the selected device type installed in the corresponding location.
>
>
  • TestBeam : First select the testbeam date. Then navigate down through the hardware structure to show devices of the selected device type installed in the corresponding location.
 

Insert a Device into a location

Line: 116 to 116
 
  • LAB: a validation panel will appear. Insert all the informations and click Ok. You return to the previous panel. Click on the refresh button to the bottom left and check that the device just inserted is not in the table anymore.
Changed:
<
<
  • TestBeam : Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status). First select the testbeam date. Then navigate down to the hardware level and click on the desired location. A validation panel will appear. Insert all the informations and click Ok.
>
>
  • TestBeam : Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status). First select the testbeam date. Then navigate through to the hardware structure and click on the desired location. A validation panel will appear. Insert all the informations and click Ok.
 

Remove a Device from a location

Changed:
<
<
A table with all allocated devices will appear. Select the device to remove and click on Remove selected device from its location. A validation panel will appear. Insert all the informations and click Ok.
>
>
A table with all allocated devices will appear. Select the device you want to remove and click on Remove selected device from its location. A validation panel will appear. Insert all the informations and click Ok.
 

Revision 62016-02-28 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 7 to 7
  The Inventory, Bookkeeping and Connectivity Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices data and locations.
Changed:
<
<

How to start DB operations

>
>

IBCDB setup instructions

 
Changed:
<
<
Start a remote desktop connection to the pccaz8007 computer. Login using the lhcbrich account. Double-click on the RICH_UPGRADE_IBCDB shortcut on the desktop. The following panel will appear
>
>
Start a remote desktop connection to the pccaz8007 machine at CERN. Right click on your desktop, select new->shortcut. In the text field type the location of the item as

C:\Siemens\Automation\WinCC_OA\3.11\bin\WCCOAui.exe -event PCCAZ8007:16998 -data PCCAZ8007:16897 -config D:\WinCC\RICH_UPGRADE-IBCDB\config\config -p lbRichDB/_lbRichDB_operations.pnl

Click next, type the name you want for the shortcut and click finish.

Double-click on the shortcut to start the database operations.

DB operations

First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens. The available functionalities depends on the selected device type.

Then the following panel will appear:

  StartPanel.png
Line: 20 to 32
 

Hardware View

Deleted:
<
<
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens. The available functionalities depends on the selected device type.
 You can change the selected device type clicking on the button at the top.

MAPMT

Line: 43 to 53
  Datasheet.png
Changed:
<
<
Create a Device
>
>
Create Devices
 
Changed:
<
<
Click this button to insert a new device in the DB. Type a unique serial number in the text field and click on the green tick on the right.
>
>
This button allows to insert multiple MaPMTs at the same time. All you need is the Hamamatsu .csv files containing a series of datasheet.
 
Changed:
<
<
The Datasheet button appears: click on it and insert the informations required in the new panel (pass the mouse over the acronyms to see the extended names). These informations can also be inserted later. Click the OK or the Cancel button to return to the previous panel.
>
>
First you have to browse to search the csv file, then select the delivery location and date, click import and you have done!
 
Changed:
<
<
Click the CREATE button to apply the changes and to confirm.
>
>
A message of error will appear if in the file you have selected there is at least one MaPMT already inserted in the database. In this case the file will not be imported.
 
Change Device Status, k-Factor, Quality Flag
Line: 84 to 94
 

Logical View

Deleted:
<
<
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens.
 Logic.png

Search by device type

Revision 42015-11-23 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 20 to 20
 

Hardware View

Changed:
<
<
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB. The available functionalities depends on the selected device type.
>
>
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens. The available functionalities depends on the selected device type.
  You can change the selected device type clicking on the button at the top.
Line: 63 to 63
  A panel similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.
Added:
>
>

Lens

  • Summary : Click to retrieve lens data. A table appear. Select the serial number and click on Show selected Device properties.

  • Create a Device : see here. No datasheet informations are required.

  • Change Status : a table will be opened. Right click on the corresponding serial number and select the new device status.
 

Other devices

  • Summary : open a table with all the devices of the selected type contained in the DB.

  • Create a Device : see here. For the time being no datasheet informations are required.
Changed:
<
<
  • Change Device Status : a table will be opened. Right click on the corresponding serial number and select the new device status.
>
>
  • Change Status : a table will be opened. Right click on the corresponding serial number and select the new device status.

  • Insert/Update Device Properties : a table will be opened. Select the corresponding serial number and click on Insert/update Device properties to insert new lens data.
 

Logical View

Changed:
<
<
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB.
>
>
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB, Lens.
  Logic.png

Revision 32015-11-23 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

Changed:
<
<

What is the Inventory and Bookkeeping Database project?

>
>

What is the Inventory, Bookkeeping and Connectivity Database project?

 
Changed:
<
<
The Inventory and Bookkeeping Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices data and locations.
>
>
The Inventory, Bookkeeping and Connectivity Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices data and locations.
 

How to start DB operations

Line: 32 to 32
  Click this button to retrieve data. A table appears with all the MAPMTs contained in the DB.
Changed:
<
<
For each MAPMT there are Serial Number, status, Quality Flag, Gain, k-Factor and Dark Counts (gain and dark counts are the values at nominal HV and illumination calibration conditions).
>
>
For each MAPMT the table contains Serial Number, status, Quality Flag, Gain, k-Factor and Dark Counts columns (gain and dark counts are the values at nominal HV and illumination calibration conditions).
  To retrieve data of a MAPMT select the corresponding row and click on the Show selected Device properties button. The following panel will open
Added:
>
>
  MaPMTval.png
Line: 43 to 44
 Datasheet.png

Create a Device
Added:
>
>
 
Changed:
<
<
Click this button to insert a new device in the DB. Insert a unique serial number in the text field and click on the green tick on the right.
>
>
Click this button to insert a new device in the DB. Type a unique serial number in the text field and click on the green tick on the right.
  The Datasheet button appears: click on it and insert the informations required in the new panel (pass the mouse over the acronyms to see the extended names). These informations can also be inserted later. Click the OK or the Cancel button to return to the previous panel.
Line: 53 to 55
 
Change Device Status, k-Factor, Quality Flag
Changed:
<
<
The Change Device Status, k-Factor, Quality Flag button allows to change "global" MaPMT properties. Click on it, right-click on the corresponding serial number and select the value you want to change.
>
>
Click this button to change one of these MaPMT properties. Right-click on the corresponding serial number and select the value you want to change.
 
Insert/Update Device Properties
Changed:
<
<
The Insert/Update Device Properties button will open the blue panel shown above, this time to insert calibration data in the DB. Click Apply to confirm.
>
>
Click to insert new MAPMT data in the DB. Select the corresponding row and click the Insert/update Device properties.

A panel similar to the one shown in the Summary subsection will appear, this time to insert calibration data in the DB. Click Apply to confirm.

 

Other devices

Changed:
<
<
Summary : open a table with all the devices of the selected type contained in the DB
>
>
  • Summary : open a table with all the devices of the selected type contained in the DB.

  • Create a Device : see here. For the time being no datasheet informations are required.
 
Changed:
<
<
Change Device Status : a table will be opened. Right click on the corresponding serial number and select the change of the device status.
>
>
  • Change Device Status : a table will be opened. Right click on the corresponding serial number and select the new device status.
 

Logical View

Added:
>
>
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB.
 Logic.png

Search by device type

Changed:
<
<
Click to see current locations of devices of the selected type. To retrieve the device location history, select the corresponding row and click on the Show History button.
>
>
Click to see current locations of devices of the selected type. To retrieve the device location history, with interval of validity date, select the corresponding row and click on the See device history button.
 

Search by location

Changed:
<
<
Click to search the devices installed in a selected location at any time.
>
>
Click to retrieve the devices installed in a selected location at any time. First you have to select the location type. For the time being the available location types are LAB and TestBeam.

  • LAB : select the LAB and click on the See location history button. A table with the devices of the device type selected at the beginning will appear.

  • TestBeam : First select the testbeam date. Then navigate down to the hardware level to show devices of the selected device type installed in the corresponding location.
 

Insert a Device into a location

A table with all devices not yet allocated will appear. If the wanted device does not appear, it means either that the device have not been yet inserted in the DB or it is located somewhere else (see Remove a Device from a location).

Changed:
<
<
Select the device, the location type and click on insert. A validation panel will appear. Insert all the informations and click OK.
>
>
Select the device, the location type and click Ok.

  • LAB: a validation panel will appear. Insert all the informations and click Ok. You return to the previous panel. Click on the refresh button to the bottom left and check that the device just inserted is not in the table anymore.
 
Changed:
<
<
Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status).
>
>
  • TestBeam : Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status). First select the testbeam date. Then navigate down to the hardware level and click on the desired location. A validation panel will appear. Insert all the informations and click Ok.
 

Remove a Device from a location

Changed:
<
<
A table with all the allocated devices will appear. Select the device to remove and click on Remove from a location button. A validation panel will appear. Insert all the informations and click OK.
>
>
A table with all allocated devices will appear. Select the device to remove and click on Remove selected device from its location. A validation panel will appear. Insert all the informations and click Ok.
 

Revision 22015-11-21 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Line: 9 to 9
 

How to start DB operations

Changed:
<
<
The following is the start panel
>
>
The start panel is the following
  StartPanel.png
Changed:
<
<
The Hardware View button allows to insert new devices in the DB and to insert/update/retrieve data of inserted devices.
>
>
Click the Hardware View button to start a series of WinCC-OA panels that allow you to insert new devices in the DB and to insert/update/retrieve test, calibration and setting data.
 
Changed:
<
<
The Logical View button allows to insert/retrieve devices locations at any time
>
>
Click the Logical View button to start a series of WinCC-OA panels that allow you to insert/update/retrieve device locations at any time.
 

Hardware View

Changed:
<
<
The hardware, inside the DB, is divided into device types: MaPMT, BaseBoard, FEB, BackBoard, DEB.
>
>
First you have to select the device type that you want to work with. For the time being the device types are: MAPMT, BaseBoard, FEB, BackBoard, DEB. The available functionalities depends on the selected device type.
 
Changed:
<
<
The Create a Device button allows to insert a new device in the DB. A unique serial number is required to create the device. Click OK to confirm the creation. In the MAPMT case you would insert datasheet informations before the confirmation, but it can also be done later.
>
>
You can change the selected device type clicking on the button at the top.
 
Changed:
<
<
Other functionalities are slightly different depending on the selected device type.

MaPMT

>
>

MAPMT

  MaPMT.png

Summary
Changed:
<
<
The Summary button open a table with all the MaPMTs contained in the DB, with serial number, status, quality flag, kFactor, gain and dark counts (@ nominal HV and illumination calibration conditions).
>
>
Click this button to retrieve data. A table appears with all the MAPMTs contained in the DB.

For each MAPMT there are Serial Number, status, Quality Flag, Gain, k-Factor and Dark Counts (gain and dark counts are the values at nominal HV and illumination calibration conditions).

 
Changed:
<
<
To retrieve data of a MaPMT select the corresponding row and click on the Show Device Properties button. The following panel will open
>
>
To retrieve data of a MAPMT select the corresponding row and click on the Show selected Device properties button. The following panel will open
  MaPMTval.png
Changed:
<
<
To retrieve calibration data select the desired start of validity date. In the left side there are Datasheet, Quantum Efficiency and Test Infos buttons. Click to see the corresponding data, i.e.
>
>
To retrieve calibration data select the desired start of validity date. To the left there are Datasheet, Test Infos and Quantum Efficiency buttons. Click to see the corresponding data, i.e.
  Datasheet.png
Added:
>
>
Create a Device

Click this button to insert a new device in the DB. Insert a unique serial number in the text field and click on the green tick on the right.

The Datasheet button appears: click on it and insert the informations required in the new panel (pass the mouse over the acronyms to see the extended names). These informations can also be inserted later. Click the OK or the Cancel button to return to the previous panel.

Click the CREATE button to apply the changes and to confirm.

 
Change Device Status, k-Factor, Quality Flag

Revision 12015-11-19 - GiovanniCavallero

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="RichUpgrade"

RICH Upgrade Database

What is the Inventory and Bookkeeping Database project?

The Inventory and Bookkeeping Database is a WinCC-OA project working as a user friendly database for the RICH upgrade. The DB contains the informations about all physical devices (settings, calibration and test data) and their location at any time. It allows to save records with interval of validity date/time to track changes on devices data and locations.

How to start DB operations

The following is the start panel

StartPanel.png

The Hardware View button allows to insert new devices in the DB and to insert/update/retrieve data of inserted devices.

The Logical View button allows to insert/retrieve devices locations at any time

Hardware View

The hardware, inside the DB, is divided into device types: MaPMT, BaseBoard, FEB, BackBoard, DEB.

The Create a Device button allows to insert a new device in the DB. A unique serial number is required to create the device. Click OK to confirm the creation. In the MAPMT case you would insert datasheet informations before the confirmation, but it can also be done later.

Other functionalities are slightly different depending on the selected device type.

MaPMT

MaPMT.png

Summary

The Summary button open a table with all the MaPMTs contained in the DB, with serial number, status, quality flag, kFactor, gain and dark counts (@ nominal HV and illumination calibration conditions).

To retrieve data of a MaPMT select the corresponding row and click on the Show Device Properties button. The following panel will open

MaPMTval.png

To retrieve calibration data select the desired start of validity date. In the left side there are Datasheet, Quantum Efficiency and Test Infos buttons. Click to see the corresponding data, i.e.

Datasheet.png

Change Device Status, k-Factor, Quality Flag

The Change Device Status, k-Factor, Quality Flag button allows to change "global" MaPMT properties. Click on it, right-click on the corresponding serial number and select the value you want to change.

Insert/Update Device Properties

The Insert/Update Device Properties button will open the blue panel shown above, this time to insert calibration data in the DB. Click Apply to confirm.

Other devices

Summary : open a table with all the devices of the selected type contained in the DB

Change Device Status : a table will be opened. Right click on the corresponding serial number and select the change of the device status.

Logical View

Logic.png

Search by device type

Click to see current locations of devices of the selected type. To retrieve the device location history, select the corresponding row and click on the Show History button.

Search by location

Click to search the devices installed in a selected location at any time.

Insert a Device into a location

A table with all devices not yet allocated will appear. If the wanted device does not appear, it means either that the device have not been yet inserted in the DB or it is located somewhere else (see Remove a Device from a location).

Select the device, the location type and click on insert. A validation panel will appear. Insert all the informations and click OK.

Only READY devices can be inserted in Testbeam location type (to change the status you need to use the Hardware View. See here to know how to change device status).

Remove a Device from a location

A table with all the allocated devices will appear. Select the device to remove and click on Remove from a location button. A validation panel will appear. Insert all the informations and click OK.

-- GiovanniCavallero - 2015-11-19

META FILEATTACHMENT attachment="StartPanel.png" attr="" comment="" date="1447968937" name="StartPanel.png" path="StartPanel.png" size="44377" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMT.png" attr="" comment="" date="1447969161" name="MaPMT.png" path="MaPMT.png" size="30575" user="gcavalle" version="1"
META FILEATTACHMENT attachment="MaPMTval.png" attr="" comment="" date="1447969162" name="MaPMTval.png" path="MaPMTval.png" size="50055" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Logic.png" attr="" comment="" date="1447969162" name="Logic.png" path="Logic.png" size="30532" user="gcavalle" version="1"
META FILEATTACHMENT attachment="Datasheet.png" attr="" comment="" date="1447969163" name="Datasheet.png" path="Datasheet.png" size="32075" user="gcavalle" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback