These are the Tilecal shifter instructions, which are IN CONSTRUCTION, the goal is to give step by step instructions on what to do during a data taking shift, and also some basic troubleshooting.

I) Start of shift

1 Log into the ATLAS logbook: http://pcatdwww.cern.ch:8100/

- Make entries as "tile_shifter" - Write in the log you started the shift - Enter any observation you will do while monitoring data, every potential problem.

2 Check scheduled activities for the time period at:

http://pcatdwww.cern.ch/cgi-bin/webcal/webcal.cgi and go to "Private Calendar": TileCal

3 Log into the DCS machine (pcatltillv0) with the tile DCS account and start LV, HV panels (See Section II)

4 Log into the TDAQ machine with tile data acquisition account (pcatltildaq01) (See Section III)

- Go to the ROS machine in the pit :> ros01 - Start the TDAQ program :> runme - Set up DAQ

5 Log into the monitoring machine (pcatltilmon01) with tile data acquisition account

- start the OHP with the configuration file for the type of run you are taking (long cosmic run or long pedestal)

II) Start DCS

1) Low voltages

From a machine within point 1 network do:

%> rdesktop -f cerntsatldcs01

For LBA LVPS panel choose host:

%> pcatltillv2

and start the LBC LVPS panel:

%> fwTileLV\TilLBA.pnl

This will start the LVPS DCS project for A-side.

For LBC LVPS panel, choose host:

%> pcatltillv02

and the LVPS panel

%> fwTileLV\TilLBC.pnl

instructions for FSM missing still.

2) High voltage

For the moment we don't have FSM nor remote panels so we need to rdesktop directly to the HV PCs to operate HV from control room.

So in a shell do

rdesktop cerntsatldcs01

then select on top of the panel "rdesktop" Then type

pcatltillv1 

for the LBA HV project and

pcatltilcr0

for the LBC HV project.

For information the DIM version of HV runs on

pcatltilhv0

but you should not need that.

III) DAQ

1- Start the DAQPanel in the DAQ menu

2- Go to tab "main", and browse to choose "setup script".

3- Choose setup script

/db/current/tile/setup_daq.sh

(perhaps become later

/det/tile/rcd/setupdaq.sh

)

4- Browse database file and choose

/db/current/tile/partitions/TileCalPartition.data.xml

5- Push "Read info"

6- Push "Get partition"

The tile sw is installed under

/det/tile/rcd

people who belong to group Tile are allowed to write the sw to the

/det/tile/rcd

you need password for tileswinstaller account.

IV) More expert DAQ how-to

1) Location of TileDAQ software in the pit

TileCal DAQ software for ACR use is located under

/det/tile/rcd/

TileCal configuration DB is located under

/db/current/tile/

/db/current/tile/partitions/

2) machines we are using right now

pc-til-ros-com-01  our main DAQ machine which we also use as event builder in standalone run

ROS machines:
pc-til-ros-lba-01
pc-til-ros-lba-02

pc-til-ros-lbc-01
pc-til-ros-lbc-02

(sbc-till-acc-01  TTC SBC for EBA)
sbc-till-acc-02  TTC SBC for LBA
sbc-till-acc-03  TTC SBC for LBC
(sbc-till-acc-04  TTC SBC for EBC)

(sbc-till-rcc-01  ROD crate for EBA)
sbc-till-rcc-02  ROD crate for LBA
sbc-till-rcc-03  ROD crate for LBC
(sbc-till-rcc-04  ROD crate for EBC)

sbc-til-trg-01   Cosmic board crate

3) how to setup farmtool

Information from Giuseppe Avolio,December 1st

As i told you yesterday you have to source a script within your main setup script. You can source
this one

/preseries-scratch/farmtools/FarmTools_USE_THIS_ONE/setup.sh

This is not the final version but you can play with that (basically only the GUI version does not
work). The shiftertool developer is working on a full working release which should be ready by
monday.

4) how to use "FarmTools"

III) Take a run

1. - Check that LV is ON using the DCS LV panels write the list of drawers where LV is on and where LV is off in the logbook
2. - Check that HV is ON. How? write the list of drawers with HV on and HV off in the logbook. (3- Make DVS test for the modules that are supposed to be in the run Define minimum list of tests to carry out. What if the DVS GUI does not work? command line instructions, then still does not work, what experts to call)
3. - Start the run

• Monitor the data being taken (see Online monitoring section)

1. - During the run report any problem (DAQ stuck, DAQ error messages, LV or HV trip, error messages), into the ATLOG
2. - When you have taken the requested number of events then stop the run.
3. - At the end of the run save the monitoring histograms by pushing save button in OHP
4. - Move the OHP histogram to CASTOR [make script!]
5. - Write a comment in the ATLOG if this is a good or a bad run according to you.

• Reconstruct
• Analyse/ comment

Plenty of instruction at: TileCommOnlineTeam4 under Shifter manual Team 4: MobiDaq + RODDaq link to webpage

IV) GNAM monitoring

(responsible Andrea Dotti & Chiara Roda) https://uimon.cern.ch/twiki/bin/view/Atlas/GNAMHelp

Instructions on how to run GNAM monitoring can be found at GNAMHelp

b) "Event filter" monitoring (responsible Luca Fiorini)

Instructions on how to run "Event filter" monitoring can be found here CaloMonitoringJuly2006ExpertWeekInstructions

- what histograms to look at in first priority? - what to do in case of problem?

V) Troubleshooting

1) What to do in case of problems with DVS

2) What problems if DVS tests work but TDAQ hangs

3) What to do if problem with monitoring

VI) Phone numbers

USA15 counting room phone	77186
TileCal satellite control room	70954
ACR Tile desk phone	76007
LArg satellite control room	70949
Carlos	165518
Carsten (cooling)	165173
Christophe	162284
Giorgi	165241
Giovanna Lehmann (TDAQ group)	162076
Irakli	160287
Irene	162098
Jan (cooling)	164927
Oleg	163436
Oleg (IHEP)	+7 09677 13615

-- ChristopheClement - 05 Dec 2006