Lhep: 1 revision imported

2015-03-18T07:49:29Z

1 revision imported

← Older revision	Revision as of 09:49, 18 March 2015
(No difference)

Lhep at 09:28, 9 January 2009

2009-01-09T09:28:32Z

New page

In order to publish the located vertex one need to produce the file
named bxxxxxx.feedback (6 digits)

in the bxxxxxx directory.

[[bxxxxxx.feedback Input file format]]

example (these are dummy values!) of a file related to an event with 2 vertexes and 5 tracks:

[[bxxxxxx.feedback Example]]

Then issue the command:

source runvertex.sh

You'll get an invitation to enter the brick number:

<pre>
[scanner@lheppc56 b071899]$ source runvertex.sh
--------------------------------------------------------------------------
reconstruction information into Opera CentralDB
-------------------------------------------------------------------------
please enter brick number :

</pre>

Give it a number without leading "1", f.e. for brick 1071899 you give only 71899

the full log of publication will look like this:

<pre>
[scanner@lheppc56 b071899]$ source runvertex.sh
--------------------------------------------------------------------------
reconstruction information into Opera CentralDB
-------------------------------------------------------------------------
please enter brick number :
71899
input file : b071899.feedback
brick number :1071899
input file read
vertices :
4058 31433.26 26600.62 -13768.196 1 0 0
tracks :
3000 4058 -1 31559.344 26622.203 -13048.251
0.177604 0.036001 3.032554 -1.0 -99.0 0.0 0.0
0 1 1 0
3977 4058 -1 31462.117 26526.607 -13048.251
0.043181 -0.096823 3.042419 -1.0 -99.0 0.0 0.0
0 0 1 0
4006 4058 -1 31645.828 26784.574 -13048.251
0.297182 0.26252 3.651628 -1.0 -99.0 0.0 0.0
0 0 0 0
3007 4058 -1 32461.842 26613.924 -11756.301
0.509063 2.26E-4 15.2323 -1.0 -99.0 0.0 0.0
0 0 0 0
----> Connecting to DB-BERN4
Connection ok
Insertion date : 2009-01-09 10:11:17
{call pc_add_proc_operation_brick(5000000000000022,5000000004330002,500000000013
0001,1071899,null,to_timestamp('2009-01-09 10:11:17','YYYY-MM-DD HH24:MI:SS'),'F
eedback',?)}
Process ID :5000000008510004
BEGIN insert into tb_reconstructions(id_eventbrick,id_processoperation) values(
1071899,5000000008510004) returning id into ?; END;
Process ID :5000000008510005
insert into tb_reconstruction_options (id_eventbrick, id_reconstruction, geometr
ical_probability, physical_probability)values (1071899,5000000008510005,0,0)
insert into vw_feedback_vertices(id_eventbrick,id_reconstruction,id_vertex,posx
,posy,posz,isprimary,ischarm,istau)values(1071899,5000000008510005,4058,31433.26
,26600.62,-13768.196,'Y','N','N')
insert into vw_feedback_tracks (id_eventbrick, id_reconstruction, id_track, id_u
pvtx, id_downvtx,x, y, z, sx, sy, upip, downip, p, pmin, pmax, manual, particle,
scanback, darkness)values(1071899,5000000008510005,3000,4058,NULL,31559.344,266
22.203,-13048.251,0.177604,0.036001,3.032554,-1.0,-99.0,0.0,0.0,'N','MUON','Y','
MIP')
insert into vw_feedback_tracks (id_eventbrick, id_reconstruction, id_track, id_u
pvtx, id_downvtx,x, y, z, sx, sy, upip, downip, p, pmin, pmax, manual, particle,
scanback, darkness)values(1071899,5000000008510005,3977,4058,NULL,31462.117,265
26.607,-13048.251,0.043181,-0.096823,3.042419,-1.0,-99.0,0.0,0.0,'N','N','Y','MI
P')
insert into vw_feedback_tracks (id_eventbrick, id_reconstruction, id_track, id_u
pvtx, id_downvtx,x, y, z, sx, sy, upip, downip, p, pmin, pmax, manual, particle,
scanback, darkness)values(1071899,5000000008510005,4006,4058,NULL,31645.828,267
84.574,-13048.251,0.297182,0.26252,3.651628,-1.0,-99.0,0.0,0.0,'N','N','N','MIP'
)
insert into vw_feedback_tracks (id_eventbrick, id_reconstruction, id_track, id_u
pvtx, id_downvtx,x, y, z, sx, sy, upip, downip, p, pmin, pmax, manual, particle,
scanback, darkness)values(1071899,5000000008510005,3007,4058,NULL,32461.842,266
13.924,-11756.301,0.509063,2.26E-4,15.2323,-1.0,-99.0,0.0,0.0,'N','N','N','MIP')
update tb_proc_operations set success='Y',finishtime= to_timestamp('2009-01-09 1
0:11:17','YYYY-MM-DD HH24:MI:SS')where id=5000000008510004
Process Operation ID :5000000008510004

</pre>

The process operation ID is returned in the last output line, use it for EventTracer and for Central DB publication.

Good luck!
I.K.

Vertex publication - Revision history

Lhep: 1 revision imported

Lhep at 09:28, 9 January 2009