Difference: MainECS (1 vs. 21)

Revision 212008-08-14 - unknown

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 85 to 85
 
  1. You can now Reset the system by selecting "RESET" after clicking on "NOT_READY":
    VeloTop_Reset.JPG

  2. WARNING! The Reset command will bring the state of each subsystem to NOT_READY, but the DAQ hardware will not be touched! To really reset the DAQ, please consult this section.
Changed:
<
<
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:". The files in the directory /daqarea/lhcb/data/2008/ on the online network can be found on Castor at /castor/cern.ch/lhcb/online/point8/2008.
>
>
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:". The files in the directory /daqarea/lhcb/data/2008/ on the online network can be found on Castor at /castor/cern.ch/grid/lhcb/data/2008/ (there is some older data stored at /castor/cern.ch/lhcb/online/point8/2008).
 
  1. Create a symbolic link using the command "ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink" in the directory
    • slice test: /group/velo/slicetest/data/
    • module power up: /group/velo/modulepowerup/data
Line: 96 to 96
 

Releasing the VELO ECS

If you want to release the VELO ECS click on the top padlock and choose release all; if the VELO control has to change its mode from local to global, don't forget to deallocate before to release. Never close the VEECS1_UI_FSM panel whithout releasing it!
Changed:
<
<
-- StefanoDeCapua - 09 Aug 2008
>
>
-- KarolHennessy - 14 Aug 2008
 
META FILEATTACHMENT attachment="VeloTop.JPG" attr="" comment="" date="1218282315" name="VeloTop.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop.JPG" size="107296" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTopNotAllocated.JPG" attr="" comment="" date="1218282331" name="VeloTopNotAllocated.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotAllocated.JPG" size="116559" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotAllocated.JPG" user="Main.StefanoDeCapua" version="1"

Revision 202008-08-09 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 16 to 16
 
  • Log on to a Windows console in the online network (LHCb domain).
  • Open the following directory: G:\online\ecs\Shortcuts\VELO
Changed:
<
<
  • Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG


>
>
  • Double click on VEECS1_UI_FSM. The following panel will pop up:

VeloTopOperate.JPG

 
  • Right-click on VELO. The following panel will pop up:
Changed:
<
<

veloc_released_310.png

>
>

VeloTop.JPG

  • The panel is composed of three parts: on the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data. The VELO User Panel button opens a panel with a collection of useful tools for monitoring (instructions here).

  • Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control. A report panel will pop up, showing which part of the system are not taken: for the time being, the VELO_DCS and VELO_HV should stay excluded for safety reason. Check if the informations displayed are consistent with your expection and then click on dismiss.

VeloActionReport.JPG

  • If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.

  • Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable". You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. turning on LV and HV). Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data.
 
Deleted:
<
<
  • The panel is composed of three parts: on the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data. The VELO User Panel button opens a panel with a collection of useful tools for monitoring (instructions here).
  • Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  • Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. turning on LV and HV). Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data.
 
  • If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:
Added:
>
>

VeloTopNotAllocated.JPG

 
Deleted:
<
<

veloc_deallocated_310.png

 
Changed:
<
<
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:

veloc_allocated_310.png
>
>
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:

VeloTopNotReady.JPG
  This assigns
  • a readout supervisor (ODIN) to the VELO providing clock and fast signals
Line: 37 to 44
 
  • a slice of the storage system to store the data
  • a slice of the monitoring system
Changed:
<
<
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png

>
>
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

Velo_TFC.JPG

You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

Velo_HLT.JPG

 

Farm monitoring

If you want to check the log output of the eventbuilder log in to any online machine (e.g. the plus analysis farm) and execute the following commands:
Line: 50 to 59
 

Taking Data

  1. Make sure that all the components you want to use and which are not included in the FSM are configured.
Changed:
<
<
  1. Select the activity you want from the pull down menu.
>
>
  1. Select the activity you want from the pull down menu (Ex PHYSICSNTP).
 
  1. Select "Run limited to" below "Max Nr. Events:" and enter the number of event you want to acquire. Typically 10000 events are acquired for noise and pedestals runs and 5000 events for the cable test.
  2. Check that "Step Run with" below "Automated Run with Steps:" is NOT selected if you do not want to perform a parameter scan.
Changed:
<
<
  1. Configure the system by selecting "Configure" after clicking on "NOT_READY". This should bring the included subsystems into the state "READY".
  2. Start the system by selecting "START_RUN" after clicking on "READY". This should bring the TFC subsystem into the state "ACTIVE" and the other subsystems into the state "RUNNING".
  3. Start the run by selecting "GO".
  4. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
  5. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
  6. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
>
>
  1. Configure the system by selecting "Configure" after clicking on "NOT_READY":
    VeloTop_Configure.JPG

  2. This should bring the included subsystems into the state "READY":
    VeloTop_Ready.JPG

  3. Start the system by selecting "START_RUN" after clicking on "READY":
    VeloTop_StartRun.JPG

  4. This should bring the TFC subsystem into the state "ACTIVE" and the other subsystems into the state "RUNNING":
    VeloTop_Active.JPG

  5. Start the run by selecting "GO":
    VeloTop_Go.JPG

  6. This should bring the VELO system into the state "RUNNING":
    VeloTop_Running.JPG

  7. The RUN can be aborted at any time by selecting "STOP_RUN" from the VELO system button:
    VeloTop_AbortRun.JPG

  8. Wait until the run is automatically stopped. The system will go in the state "PAUSED":
    VeloTop_Paused.JPG

  9. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED":
    VeloTop_StopRun.JPG

  10. This will bring the system into the state "NOT_READY":
    VeloTop_Stopped.JPG

  11. You can now Reset the system by selecting "RESET" after clicking on "NOT_READY":
    VeloTop_Reset.JPG

  12. WARNING! The Reset command will bring the state of each subsystem to NOT_READY, but the DAQ hardware will not be touched! To really reset the DAQ, please consult this section.
 
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:". The files in the directory /daqarea/lhcb/data/2008/ on the online network can be found on Castor at /castor/cern.ch/lhcb/online/point8/2008.
  2. Create a symbolic link using the command "ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink" in the directory
    • slice test: /group/velo/slicetest/data/
Line: 70 to 96
 

Releasing the VELO ECS

If you want to release the VELO ECS click on the top padlock and choose release all; if the VELO control has to change its mode from local to global, don't forget to deallocate before to release. Never close the VEECS1_UI_FSM panel whithout releasing it!
Changed:
<
<
-- StefanoDeCapua - 06 Mar 2008
>
>
-- StefanoDeCapua - 09 Aug 2008
 
Changed:
<
<
META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_released_310.png" attr="" comment="" date="1214347572" name="veloc_released_310.png" path="veloc_released_310.png" size="44677" stream="veloc_released_310.png" user="Main.OlafBehrendt" version="1"
>
>
META FILEATTACHMENT attachment="VeloTop.JPG" attr="" comment="" date="1218282315" name="VeloTop.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop.JPG" size="107296" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTopNotAllocated.JPG" attr="" comment="" date="1218282331" name="VeloTopNotAllocated.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotAllocated.JPG" size="116559" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotAllocated.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTopNotReady.JPG" attr="" comment="" date="1218282349" name="VeloTopNotReady.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotReady.JPG" size="116411" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopNotReady.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloActionReport.JPG" attr="" comment="" date="1218282379" name="VeloActionReport.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloActionReport.JPG" size="21687" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloActionReport.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="Velo_TFC.JPG" attr="" comment="" date="1218283321" name="Velo_TFC.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\Velo_TFC.JPG" size="38514" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\Velo_TFC.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="Velo_HLT.JPG" attr="" comment="" date="1218283333" name="Velo_HLT.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\Velo_HLT.JPG" size="60663" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\Velo_HLT.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTopOperate.JPG" attr="" comment="" date="1218283958" name="VeloTopOperate.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopOperate.JPG" size="17442" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTopOperate.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Configure.JPG" attr="" comment="" date="1218284023" name="VeloTop_Configure.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Configure.JPG" size="117625" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Configure.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Ready.JPG" attr="" comment="" date="1218284193" name="VeloTop_Ready.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Ready.JPG" size="114417" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Ready.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_StartRun.JPG" attr="" comment="" date="1218284385" name="VeloTop_StartRun.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_StartRun.JPG" size="116009" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_StartRun.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Active.JPG" attr="" comment="" date="1218284402" name="VeloTop_Active.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Active.JPG" size="113533" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Active.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Go.JPG" attr="" comment="" date="1218284417" name="VeloTop_Go.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Go.JPG" size="114900" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Go.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Running.JPG" attr="" comment="" date="1218284427" name="VeloTop_Running.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Running.JPG" size="113508" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Running.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_AbortRun.JPG" attr="" comment="" date="1218284705" name="VeloTop_AbortRun.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_AbortRun.JPG" size="115267" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_AbortRun.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Paused.JPG" attr="" comment="" date="1218284901" name="VeloTop_Paused.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Paused.JPG" size="114272" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Paused.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_StopRun.JPG" attr="" comment="" date="1218284919" name="VeloTop_StopRun.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_StopRun.JPG" size="116278" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_StopRun.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Stopped.JPG" attr="" comment="" date="1218284930" name="VeloTop_Stopped.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Stopped.JPG" size="115504" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Stopped.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VeloTop_Reset.JPG" attr="" comment="" date="1218284946" name="VeloTop_Reset.JPG" path="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Reset.JPG" size="116770" stream="\\cern.ch\dfs\Users\s\sdecapua\Desktop\stefano\PVSS\screenshots\VeloTop_Reset.JPG" user="Main.StefanoDeCapua" version="1"

Revision 192008-08-09 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 5 to 5
 
<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->
Added:
>
>
 
Added:
>
>

Introduction

The VELO ECS project controls the whole Velo detector: it includes the DAQ domain, the DCS domain, the HV domain and DAI domain. It runs on vedaqa01 (linux) under the velo_user account.
 

Starting the VELO ECS

  • Log on to a Windows console in the online network (LHCb domain).

Revision 182008-08-08 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 8 to 8
 

Starting the VELO ECS

Changed:
<
<
  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
  3. Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG
>
>
  • Log on to a Windows console in the online network (LHCb domain).
  • Open the following directory: G:\online\ecs\Shortcuts\VELO
  • Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG
 

Changed:
<
<
  1. Right-click on VELO. The following panel will pop up:
>
>
  • Right-click on VELO. The following panel will pop up:
 
veloc_released_310.png

Changed:
<
<
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data. The VELO User Panel button opens a panel with a collection of useful tool for monitoring (instructions here).
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  3. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
  4. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:
>
>
  • The panel is composed of three parts: on the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data. The VELO User Panel button opens a panel with a collection of useful tools for monitoring (instructions here).
  • Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  • Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. turning on LV and HV). Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data.
  • If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:
 
veloc_deallocated_310.png

Line: 34 to 34
 The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png

Changed:
<
<

Farm monitoring

>
>

Farm monitoring

 If you want to check the log output of the eventbuilder log in to any online machine (e.g. the plus analysis farm) and execute the following commands:
  • cd /group/online/dataflow/scripts
  • ./farmMon -part=VELO
Line: 60 to 61
 
    • slice test: slicetest_slot_slotLabel_tell1_Tell1SerialNumber_runType_yymmdd_hhmm.dat
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: yymmdd_hhmm_slotLabel_modulepowerup_runType_hvStatus.dat
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
Added:
>
>

Releasing the VELO ECS

If you want to release the VELO ECS click on the top padlock and choose release all; if the VELO control has to change its mode from local to global, don't forget to deallocate before to release. Never close the VEECS1_UI_FSM panel whithout releasing it!
 -- StefanoDeCapua - 06 Mar 2008

META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"

Revision 172008-08-08 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 16 to 16
 
  1. Right-click on VELO. The following panel will pop up:

veloc_released_310.png

Changed:
<
<
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
>
>
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data. The VELO User Panel button opens a panel with a collection of useful tool for monitoring (instructions here).
 
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  2. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
  3. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:

Revision 162008-07-16 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 52 to 52
 
  1. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
  2. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
  3. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
Changed:
<
<
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:".
>
>
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:". The files in the directory /daqarea/lhcb/data/2008/ on the online network can be found on Castor at /castor/cern.ch/lhcb/online/point8/2008.
 
  1. Create a symbolic link using the command "ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink" in the directory
    • slice test: /group/velo/slicetest/data/
    • module power up: /group/velo/modulepowerup/data

Revision 152008-06-30 - MarkTobin

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->
Changed:
<
<
>
>
 

Starting the VELO ECS

  1. Log on to a Windows console in the online network (LHCb domain).
Line: 34 to 34
 The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png

Added:
>
>

Farm monitoring

 If you want to check the log output of the eventbuilder log in to any online machine (e.g. the plus analysis farm) and execute the following commands:
Changed:
<
<
  • export DIM_DNS_NODE= subfarmName where the subfarmName can be extracted from the picture above (in that case HLTC08)
  • /opt/FMC/bin/logViewer -s /*/gaudi/log
>
>
  • cd /group/online/dataflow/scripts
  • ./farmMon -part=VELO
  • ./errorLog VELO
 

Taking Data

Revision 142008-06-26 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 31 to 31
 
  • a slice of the storage system to store the data
  • a slice of the monitoring system
Changed:
<
<
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png
>
>
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png

If you want to check the log output of the eventbuilder log in to any online machine (e.g. the plus analysis farm) and execute the following commands:
  • export DIM_DNS_NODE= subfarmName where the subfarmName can be extracted from the picture above (in that case HLTC08)
  • /opt/FMC/bin/logViewer -s /*/gaudi/log
 

Taking Data

Revision 132008-06-26 - EddyJans

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 45 to 45
 
  1. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
  2. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
  3. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
Changed:
<
<
  1. After logging in to the analysis farm plus you can find the data in the file indicated in the text field next to "Storing Data On:".
  2. Make a symbolic link to the directory (ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink)
>
>
  1. After logging in to the analysis farm plus you can find the data in the directory indicated in the text field next to "Storing Data On:".
  2. Create a symbolic link using the command "ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink" in the directory
 
    • slice test: /group/velo/slicetest/data/
Changed:
<
<
    • module power up: /group/velo/modulepowerup/data/
  1. Rename the file to
>
>
    • module power up: /group/velo/modulepowerup/data
  1. Use as NameOfTheLink:
 
    • slice test: slicetest_slot_slotLabel_tell1_Tell1SerialNumber_runType_yymmdd_hhmm.dat
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: yymmdd_hhmm_slotLabel_modulepowerup_runType_hvStatus.dat
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.

-- StefanoDeCapua - 06 Mar 2008

Changed:
<
<
META FILEATTACHMENT attachment="veloc_released_310.png" attr="" comment="" date="1214347572" name="veloc_released_310.png" path="veloc_released_310.png" size="44677" stream="veloc_released_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
>
>
 
META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"
Added:
>
>
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_released_310.png" attr="" comment="" date="1214347572" name="veloc_released_310.png" path="veloc_released_310.png" size="44677" stream="veloc_released_310.png" user="Main.OlafBehrendt" version="1"

Revision 122008-06-25 - KazuyoshiAkiba

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 31 to 31
 
  • a slice of the storage system to store the data
  • a slice of the monitoring system
Changed:
<
<
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png
>
>
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png
 

Taking Data

Line: 46 to 46
 
  1. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
  2. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
  3. After logging in to the analysis farm plus you can find the data in the file indicated in the text field next to "Storing Data On:".
Changed:
<
<
  1. Copy the data to the directory
    • slice test: /daqarea/data/velo/slicetest
    • module power up: /daqarea/data/velo/modulepowerup
>
>
  1. Make a symbolic link to the directory (ln -s /daqarea/lhcb/data/2008/RAW/VELOC/RECIPENAME/RUNNUMBER/ NameOfTheLink)
    • slice test: /group/velo/slicetest/data/
    • module power up: /group/velo/modulepowerup/data/
 
  1. Rename the file to
Changed:
<
<
    • slice test: slicetest_slot_slotLabel_tell1_Tell1SerialNumber_runType_yymmdd_hhmm.dat
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: yymmdd_hhmm_slotLabel_modulepowerup_runType_hvStatus.dat
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
>
>
    • slice test: slicetest_slot_slotLabel_tell1_Tell1SerialNumber_runType_yymmdd_hhmm.dat
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: yymmdd_hhmm_slotLabel_modulepowerup_runType_hvStatus.dat
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
  -- StefanoDeCapua - 06 Mar 2008
Deleted:
<
<
META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
 
META FILEATTACHMENT attachment="veloc_released_310.png" attr="" comment="" date="1214347572" name="veloc_released_310.png" path="veloc_released_310.png" size="44677" stream="veloc_released_310.png" user="Main.OlafBehrendt" version="1"
Added:
>
>
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"

Revision 112008-06-25 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
Changed:
<
<
  1. Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG
>
>
  1. Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG
 

  1. Right-click on VELO. The following panel will pop up:
Changed:
<
<

VELO_TOP.JPG

>
>

veloc_released_310.png

 
Changed:
<
<
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  3. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo and VELO_TFC should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
>
>
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo, the TFC system, the HLT, the storage and the monitoring are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  3. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo, VELO_TFC, VELO_HLT, VELO_Storage and VELO_Monitoring should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
 
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:
Changed:
<
<

VELO_TOP_ALLOCATE.JPG

>
>

veloc_deallocated_310.png

 
Changed:
<
<
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:

VELO_TOP_ALLOCATED.JPG
>
>
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:

veloc_allocated_310.png
 
Added:
>
>
This assigns
  • a readout supervisor (ODIN) to the VELO providing clock and fast signals
  • a subfarm of the HLT to acquire the data
  • a slice of the storage system to store the data
  • a slice of the monitoring system
 
Changed:
<
<
This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
You can check which partition has been dynamically allocated double clicking on VELO_TFC:

VELO_TFC.JPG
>
>
The system should be afterwards in the state "NOT_READY".
You can check which TFC partition has been dynamically allocated by double clicking on VELO_TFC:

tfc_allocated_310.png
You can check which HLT subfarm has been dynamically allocated by double clicking on VELO_HLT:

hlt_allocated_310.png
 

Taking Data

Line: 41 to 41
 
  1. Check that "Step Run with" below "Automated Run with Steps:" is NOT selected if you do not want to perform a parameter scan.
  2. Configure the system by selecting "Configure" after clicking on "NOT_READY". This should bring the included subsystems into the state "READY".
  3. Start the system by selecting "START_RUN" after clicking on "READY". This should bring the TFC subsystem into the state "ACTIVE" and the other subsystems into the state "RUNNING".
Deleted:
<
<
  1. Start the eventbuilder!
 
  1. Start the run by selecting "GO".
  2. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
Deleted:
<
<
  1. Stop the eventbuilder!
 
  1. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
  2. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
Changed:
<
<

Running the Eventbuilder

The filter farm will be included into PVSS shortly.

Setup (only at the start of the day)

  1. Login to the filter farm node hlte0603 (Linux) and change to the directory /group/velo/sw/scripts.
  2. Setup the environment for the eventbuilder by executing the command "source startEventbuilder.sh". You should end up in the directory /group/velo/sw/cmtuser/Online_v3r2/Online/OnlineTasks/v1r4/job

Configuration (only if you change the TELL1(s))

  1. Open a shell on any machine in the online network. Change to the directory /group/velo/sw/scripts. Adjust the configuration files of the eventbuilder to the TELL1 under test by making use of one of the PERL scripts
    • slice test: configureEventbuilderSlicetest with the following syntax: ./configureEventbuilderSlicetest Tell1IpAlias (e.g. "./configureEventbuilderSlicetest vetella17")
    • module power up: configureEventbuilderModulepowerup with the following syntax: ./configureEventbuilderModulepowerup Tell1IpAlias [Tell1IpAlias2] ... [Tell1IpAliasN] (e.g. "./configureEventbuilderModulepowerup vetella17 vetellc13")

Running the Eventbuilder

  1. Go back to the shell on the filter farm node hlte0603.
  2. Start the Eventbuilder with the command:
    • slice test: ./slicetest.sh slotLabel Tell1SerialNumber runType
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: ./modulepowerup.sh slotLabel runType hvStatus
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
  3. Many windows will pop up.
  4. Check that there are three buffers in the window "MBMMon". If not, stop the Eventbuilder (see below) and start over from 1.
  5. Wait for the message "crhhh...3 Event# nrx" to appear in the window "EvtProd".
  6. Start the run in PVSS!
  7. Should the message "Unexpected event package from ..." or "Missing event package from ..." appear call the expert.
  8. Wait until the run stops.
  9. Check that the expected number of events really has arrived in all the buffers displayed in the window "MBMMon".
  10. Stop the Eventbuilder with the help of ./stopEventbuilder.sh. Answer the arising question with "y".
  11. You find the data in the directory /data/velo/slicetest/ or /data/velo/modulepowerup
>
>
  1. After logging in to the analysis farm plus you can find the data in the file indicated in the text field next to "Storing Data On:".
  2. Copy the data to the directory
    • slice test: /daqarea/data/velo/slicetest
    • module power up: /daqarea/data/velo/modulepowerup
  3. Rename the file to
    • slice test: slicetest_slot_slotLabel_tell1_Tell1SerialNumber_runType_yymmdd_hhmm.dat
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: yymmdd_hhmm_slotLabel_modulepowerup_runType_hvStatus.dat
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
  -- StefanoDeCapua - 06 Mar 2008
Line: 87 to 63
 
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" version="1"
Added:
>
>
META FILEATTACHMENT attachment="veloc_deallocated_310.png" attr="" comment="" date="1214347332" name="veloc_deallocated_310.png" path="veloc_deallocated_310.png" size="44259" stream="veloc_deallocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_allocated_310.png" attr="" comment="" date="1214347387" name="veloc_allocated_310.png" path="veloc_allocated_310.png" size="43660" stream="veloc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_configured_310.png" attr="" comment="" date="1214347406" name="veloc_configured_310.png" path="veloc_configured_310.png" size="43031" stream="veloc_configured_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="hlt_allocated_310.png" attr="" comment="" date="1214347455" name="hlt_allocated_310.png" path="hlt_allocated_310.png" size="23158" stream="hlt_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="tfc_allocated_310.png" attr="" comment="" date="1214347469" name="tfc_allocated_310.png" path="tfc_allocated_310.png" size="17726" stream="tfc_allocated_310.png" user="Main.OlafBehrendt" version="1"
META FILEATTACHMENT attachment="veloc_released_310.png" attr="" comment="" date="1214347572" name="veloc_released_310.png" path="veloc_released_310.png" size="44677" stream="veloc_released_310.png" user="Main.OlafBehrendt" version="1"

Revision 102008-06-23 - StefanoDeCapua

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
Changed:
<
<
  1. Double click on VEECS1_UI_FSM. The following panel will pop up:

VELO_FSM.JPG
>
>
  1. Double click on VEECS1_UI_FSM. The following panel will pop up:
    VELO_FSM.JPG


 
  1. Right-click on VELO. The following panel will pop up:

VELO_TOP.JPG
Added:
>
>


 
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  3. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo and VELO_TFC should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
  4. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:


VELO_TOP_ALLOCATE.JPG

Added:
>
>


 
Changed:
<
<
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:
>
>
If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:
 
VELO_TOP_ALLOCATED.JPG
Changed:
<
<
This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
You can check which partition has been dynamically allocated double clicking on VELO_TFC:
>
>
This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
You can check which partition has been dynamically allocated double clicking on VELO_TFC:
 
VELO_TFC.JPG
Deleted:
<
<
 

Taking Data

  1. Make sure that all the components you want to use and which are not included in the FSM are configured.

Revision 92008-05-07 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 41 to 41
 
  1. Start the run by selecting "GO".
  2. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
  3. Stop the eventbuilder!
Added:
>
>
  1. Stop the run by selecting "STOP_RUN" after clicking on "PAUSED". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "READY".
 
  1. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".

Running the Eventbuilder

Revision 82008-05-06 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 16 to 16
 
VELO_TOP.JPG
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
Changed:
<
<
  1. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
>
>
  1. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).

    Some hints:
    Typically VELO_Runinfo and VELO_TFC should be included to send triggers and take data. For the module power up the following settings are foreseen: Exclude all components of half you do NOT use. VELO(A/C)_DCS, VELO(A/C)_HV and VELO(A/C)_DAI should be excluded. In the subpanel VELOA(C)_DAQ only the node VELOA(C)_DAQ_TE should be included. In VELOA(C)_DAQ_TE select only the TELL1s you want to use (typically the two corresponding to the module under test).
 
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:


VELO_TOP_ALLOCATE.JPG

Line: 62 to 62
 
  1. Go back to the shell on the filter farm node hlte0603.
  2. Start the Eventbuilder with the command:
Changed:
<
<
    • slice test: ./slicetest.sh slotLabel Tell1SerialNumber runType. Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: ./modulepowerup.sh ??? (to be defined)
>
>
    • slice test: ./slicetest.sh slotLabel Tell1SerialNumber runType
      Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: ./modulepowerup.sh slotLabel runType hvStatus
      An example for the slotLabel is VL03_C. For the runType please choose one of "cabletest", "tp" or "ntp". Take R0V_P50V as an example for the hvStatus.
 
  1. Many windows will pop up.
  2. Check that there are three buffers in the window "MBMMon". If not, stop the Eventbuilder (see below) and start over from 1.
  3. Wait for the message "crhhh...3 Event# nrx" to appear in the window "EvtProd".

Revision 72008-05-06 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 14 to 14
 
VELO_FSM.JPG
  1. Right-click on VELO. The following panel will pop up:

VELO_TOP.JPG
Changed:
<
<
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DAQ, DAI, DCS and HV), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
>
>
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DCS, HV, DAI and DAQ), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
 
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
Changed:
<
<
  1. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
>
>
  1. Include (exclude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Include" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exclude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
 
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:


VELO_TOP_ALLOCATE.JPG

Line: 31 to 31
 

Taking Data

Changed:
<
<
  1. Make sure that all the components not included in the FSM are configured.
>
>
  1. Make sure that all the components you want to use and which are not included in the FSM are configured.
 
  1. Select the activity you want from the pull down menu.
Changed:
<
<
  1. Select "Limited to" below "Max Nr. Triggers:" and enter 10000.
  2. Select "No Steps" below "Automated Run with Steps:" if you do not want to perform a parameter scan.
>
>
  1. Select "Run limited to" below "Max Nr. Events:" and enter the number of event you want to acquire. Typically 10000 events are acquired for noise and pedestals runs and 5000 events for the cable test.
  2. Check that "Step Run with" below "Automated Run with Steps:" is NOT selected if you do not want to perform a parameter scan.
 
  1. Configure the system by selecting "Configure" after clicking on "NOT_READY". This should bring the included subsystems into the state "READY".
  2. Start the system by selecting "START_RUN" after clicking on "READY". This should bring the TFC subsystem into the state "ACTIVE" and the other subsystems into the state "RUNNING".
  3. Start the eventbuilder!

Revision 62008-05-06 - EddyJans

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
Changed:
<
<
  1. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
  2. Right-click on VELO. The following panel will pop up: VELO_TOP.JPG
>
>
  1. Double click on VEECS1_UI_FSM. The following panel will pop up:

VELO_FSM.JPG
  1. Right-click on VELO. The following panel will pop up:

VELO_TOP.JPG
 
  1. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DAQ, DAI, DCS and HV), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  3. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
Changed:
<
<
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
>
>
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE:


VELO_TOP_ALLOCATE.JPG

If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here:
VELO_TOP_ALLOCATED.JPG

This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
You can check which partition has been dynamically allocated double clicking on VELO_TFC:
VELO_TFC.JPG

 

Taking Data

Revision 52008-04-24 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 13 to 13
 
  1. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
  2. Right-click on VELO. The following panel will pop up: VELO_TOP.JPG
  3. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DAQ, DAI, DCS and HV), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
Changed:
<
<
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
>
>
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
 
  1. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
  2. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
Line: 31 to 31
 
  1. Stop the eventbuilder!
  2. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
Added:
>
>

Running the Eventbuilder

The filter farm will be included into PVSS shortly.

Setup (only at the start of the day)

  1. Login to the filter farm node hlte0603 (Linux) and change to the directory /group/velo/sw/scripts.
  2. Setup the environment for the eventbuilder by executing the command "source startEventbuilder.sh". You should end up in the directory /group/velo/sw/cmtuser/Online_v3r2/Online/OnlineTasks/v1r4/job

Configuration (only if you change the TELL1(s))

  1. Open a shell on any machine in the online network. Change to the directory /group/velo/sw/scripts. Adjust the configuration files of the eventbuilder to the TELL1 under test by making use of one of the PERL scripts
    • slice test: configureEventbuilderSlicetest with the following syntax: ./configureEventbuilderSlicetest Tell1IpAlias (e.g. "./configureEventbuilderSlicetest vetella17")
    • module power up: configureEventbuilderModulepowerup with the following syntax: ./configureEventbuilderModulepowerup Tell1IpAlias [Tell1IpAlias2] ... [Tell1IpAliasN] (e.g. "./configureEventbuilderModulepowerup vetella17 vetellc13")

Running the Eventbuilder

  1. Go back to the shell on the filter farm node hlte0603.
  2. Start the Eventbuilder with the command:
    • slice test: ./slicetest.sh slotLabel Tell1SerialNumber runType. Examples for the slotLabel and the Tell1SerialNumber are "VL05_CT" and "207", respectively. For the runType please choose one of "delayscan", "cabletest", "tp" or "ntp".
    • module power up: ./modulepowerup.sh ??? (to be defined)
  3. Many windows will pop up.
  4. Check that there are three buffers in the window "MBMMon". If not, stop the Eventbuilder (see below) and start over from 1.
  5. Wait for the message "crhhh...3 Event# nrx" to appear in the window "EvtProd".
  6. Start the run in PVSS!
  7. Should the message "Unexpected event package from ..." or "Missing event package from ..." appear call the expert.
  8. Wait until the run stops.
  9. Check that the expected number of events really has arrived in all the buffers displayed in the window "MBMMon".
  10. Stop the Eventbuilder with the help of ./stopEventbuilder.sh. Answer the arising question with "y".
  11. You find the data in the directory /data/velo/slicetest/ or /data/velo/modulepowerup
 -- StefanoDeCapua - 06 Mar 2008

META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"

Revision 42008-04-23 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 13 to 13
 
  1. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
  2. Right-click on VELO. The following panel will pop up: VELO_TOP.JPG
  3. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DAQ, DAI, DCS and HV), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
Changed:
<
<
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control. If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  2. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
  3. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
  4. Once allocated, the system can be configured; click on the State button and select Configure:
  5. On the bottom left corner, the two VELO halves are displayed. If you click one of them, you will get an identical panel referring to the corresponding half.
>
>
  1. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
    If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  2. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
  3. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG

Taking Data

  1. Make sure that all the components not included in the FSM are configured.
  2. Select the activity you want from the pull down menu.
  3. Select "Limited to" below "Max Nr. Triggers:" and enter 10000.
  4. Select "No Steps" below "Automated Run with Steps:" if you do not want to perform a parameter scan.
  5. Configure the system by selecting "Configure" after clicking on "NOT_READY". This should bring the included subsystems into the state "READY".
  6. Start the system by selecting "START_RUN" after clicking on "READY". This should bring the TFC subsystem into the state "ACTIVE" and the other subsystems into the state "RUNNING".
  7. Start the eventbuilder!
  8. Start the run by selecting "GO".
  9. Wait until the run is automatically stopped. The included subsystems should be in the state "READY".
  10. Stop the eventbuilder!
  11. Reset the system by selecting "RESET" after clicking on "READY". This should bring the subsystems VELOA(C)_DAQ, VELOA(C)_Runinfo and VELOA(C)_TFC into the state "NOT_READY".
  -- StefanoDeCapua - 06 Mar 2008

Revision 32008-04-23 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 11 to 11
 
  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
  3. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
Changed:
<
<
  1. Right-click on +VELO. The following panel will pop up: VELO_TOP.JPG
  2. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
  3. The panel is composed of the 4 sub-domains (DAQ, DAI, DCS and HV) plus the TFC system: VELO_TOP_TAKEN.JPG
>
>
  1. Right-click on VELO. The following panel will pop up: VELO_TOP.JPG
  2. The panel is composed of three parts: On the top left the FSM trees of the 4 sub-domains (DAQ, DAI, DCS and HV), the Runinfo and the TFC system are accessible. On the bottom left the FSM trees of the two VELO halves are accessible. From both parts of the panel you finally access the same VELO components, just once structured in a functional way, once representing the physical layout of the VELO. The right part of the panel contains all the necessary functionality to take data.
  3. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control. If you just want to operate one VELO half you may also consider to double click on VELOA or VELOC and start from a similar panel there.
  4. Include (exlude) the parts of the FSM tree that you (do not) want to use. To do so click on the padlocks and choose "UnlockOut&Inlcude" ("Exclude&LockOut") to include (exclude) the corresponding part of the FSM tree. In case of the green tickmarks (red crosses) just click on them and change from exclude to include (include to exclude) via "Enable" or "Disable".
    You may want to exlude certain parts from the FSM tree to operate the components manually for safety reasons or to have better control of the things happening (e.g. configuring the hybrids, turning on LV/HV, ...).
 
  1. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
  2. Once allocated, the system can be configured; click on the State button and select Configure:
  3. On the bottom left corner, the two VELO halves are displayed. If you click one of them, you will get an identical panel referring to the corresponding half.

-- StefanoDeCapua - 06 Mar 2008

Revision 22008-04-23 - OlafBehrendt

Line: 1 to 1
 
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->
Line: 13 to 13
 
  1. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
  2. Right-click on +VELO. The following panel will pop up: VELO_TOP.JPG
  3. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
Changed:
<
<
  1. The panel is composed by the 4 sub-domains (DAQ, DAI, DCS and HV) plus the TFC system: VELO_TOP_TAKEN.JPG
  2. If the VELO is NOT_ALLOCATED, then click on the corrisponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assign a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
  3. Once allocated, the system can be configured; click on the State button and select Configure:
  4. On the bottom left corner, the two VELO halves are dislpayed. If you click one of them, you will get an identical panel referred to the corrisponding half:
>
>
  1. The panel is composed of the 4 sub-domains (DAQ, DAI, DCS and HV) plus the TFC system: VELO_TOP_TAKEN.JPG
  2. If the VELO is NOT_ALLOCATED, then click on the corresponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assigns a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
  3. Once allocated, the system can be configured; click on the State button and select Configure:
  4. On the bottom left corner, the two VELO halves are displayed. If you click one of them, you will get an identical panel referring to the corresponding half.
  -- StefanoDeCapua - 06 Mar 2008

Revision 12008-03-06 - StefanoDeCapua

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="ECSmanual"
<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

<!-- /ActionTrackerPlugin -->

Starting the VELO ECS

  1. Log on to a Windows console in the online network (LHCb domain).
  2. Open the following directory: G:\online\ecs\Shortcuts\VELO
  3. Double click on VEECS1_UI_FSM. The following panel will pop up: VELO_FSM.JPG
  4. Right-click on +VELO. The following panel will pop up: VELO_TOP.JPG
  5. Click on the top padlock and Take. If the padlock is closed and red, then someone else has already taken the control.
  6. The panel is composed by the 4 sub-domains (DAQ, DAI, DCS and HV) plus the TFC system: VELO_TOP_TAKEN.JPG
  7. If the VELO is NOT_ALLOCATED, then click on the corrisponding button and ALLOCATE: VELO_TOP_ALLOCATE.JPG
    If the system is already ALLOCATED, then DEALLOCATE and ALLOCATE it back. The system will go in the state shown here: VELO_TOP_ALLOCATED.JPG. This assign a readout supervisor (ODIN) to the VELO providing clock and fast signals. The system should be afterwards in the state "NOT_READY".
    You can check which partition has been dynamically allocated double clicking on VELO_TFC: VELO_TFC.JPG
  8. Once allocated, the system can be configured; click on the State button and select Configure:
  9. On the bottom left corner, the two VELO halves are dislpayed. If you click one of them, you will get an identical panel referred to the corrisponding half:

-- StefanoDeCapua - 06 Mar 2008

META FILEATTACHMENT attachment="VELO_TFC.JPG" attr="" comment="" date="1204843632" name="VELO_TFC.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" size="34150" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TFC.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATED.JPG" attr="" comment="" date="1204843493" name="VELO_TOP_ALLOCATED.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" size="89427" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATED.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_FSM.JPG" attr="" comment="" date="1204841474" name="VELO_FSM.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" size="17929" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_FSM.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP.JPG" attr="" comment="" date="1204842092" name="VELO_TOP.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" size="89076" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_TAKEN.JPG" attr="" comment="" date="1204842685" name="VELO_TOP_TAKEN.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" size="91246" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_TAKEN.JPG" user="Main.StefanoDeCapua" version="1"
META FILEATTACHMENT attachment="VELO_TOP_ALLOCATE.JPG" attr="" comment="" date="1204842936" name="VELO_TOP_ALLOCATE.JPG" path="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" size="91406" stream="C:\Documents and Settings\stefano\Documenti\Immagini\VELO_ECS\VELO_TOP_ALLOCATE.JPG" user="Main.StefanoDeCapua" 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