MYSQL

Shiuan-Hal,Shiu

Flow chart

Mysql server

Dimuon track information

Possible track numbers

Trigger matrix

Look up table

Sql script

Fortran & perl

VHDL

3

SeaQueL Server

Schema

IntroductionSQL Server

MySQL Query Browser

Schemas

Gun mode: a simulation of each proton in the high-energy collision for as many protons are specified.

Dimuon mode : this mode processes only those proton collisions that result in a dimuon pair being produced.

Pythia mode: is a special set of simulated data that comes from the Pythia generator.

6

Tables in schemas:– Run: a days-long period of run-time– Spill: each 5s of beam– Event: each bunch of 40,000 protons– Hit: hits on detectors– Dimuon: reconstructed track pairs– Track: reconstructed tracks from hits

• Also: mHit, mTrack, mDimuon

Tables in schemas

An 'm' in front of a table stands for “MC Truth”.

mHits

acceptAll

mDimuon.z

Track Data

How to choosing data

mHit mDimuon

Detectorname

Is not “H??”

Detectorname

Is “H??”z<0 and

acceptAll='1'

others

runIDeventIDtrackID1

trackID2

Data we

want

Sql script create table E906trigger.r280v1mHit select *

from production_dimuonR280V1.mHit Where detectorName like 'H%';

create table E906trigger.r280v1mDimuon select * from production_dimuonR280V1.mDimuon Where z<0 and acceptAll='1';

Sql script use E906trigger; select r280v1mHit.runID, r280v1mHit.mHitID,

r280v1mHit.trackID, r280v1mHit.eventID, r280v1mHit.dimuonID, r280v1mHit.x, r280v1mHit.y, r280v1mHit.z, r280v1mHit.detectorName, r280v1mHit.particleID from r280v1mHit inner join r280v1mDimuon on r280v1mHit.runID=r280v1mDimuon.runID and r280v1mHit.eventID=r280v1mDimuon.eventID and (r280v1mHit.trackID=r280v1mDimuon.trackID1 or r280v1mHit.trackID=r280v1mDimuon.trackID2) order by trackID, dimuonID, runID, mHitID;

example

example

How to increase the processing speed Indexes helps retrieving data from tables

quicker.

Index example use E906trigger;

create index dimuonID on r280v1mDimuon(dimuonID);

create index runID on r280v1mDimuon(runID); create index eventID on

r280v1mDimuon(eventID); create index trackID1 on

r280v1mDimuon(trackID1); create index trackID2 on

r280v1mDimuon(trackID2);

create index test on r280v1mDimuon(trackID1,trackID2,dimuonID,runID);

Possible dimuon track numbers

Horizontal paddle

Vertical paddle

Possible dimuon track numbers

From the database production_dimuonR280V1

H paddle track count# =923

V paddle track count# =3102

Over all track count # =33140

Future work To confirm the dimuon selecting conditions are

correct.

Generate the trigger matrix.

Translating the trigger matrix into look up table.

Test some conflict trigger conditions.