Email from Mark Hayes on 8-2-2000
Email received from Mark Hayes on the 8th of February.
Original message sent by Mark Hilton to Mark Hayes
Return-Path:
<Mark.Hayes@desy.de>
Delivery-Date: Tue, 8 Feb 2000 14:04:13 +0000 From: Mark.Hayes@desy.de
Sender: mhayes@mail1-195.desy.de
Date: Tue, 08 Feb 2000 14:58:13 +0100
X-Accept-Language: en
To: Mark Hilton <mark@theyellowroom.freeserve.co.uk> CC: Mark Hayes <meh@hep.ucl.ac.uk>,
Yee Li <y.li@ucl.ac.uk>,
"M. Mo" <m.mo@ucl.ac.uk>, Khadija Muluddin <zcapp75@ucl.ac.uk>,
"J. Ramanlal" <j.ramanlal@ucl.ac.uk>, "J. Loizides"
<j.loizides@ucl.ac.uk> Subject: Re: UCL 3C41 Group Project on Zeus X-Status:
$$$$
X-UID: 0000000001
Hi Mark & Jayesh,
Sorry for the delay.
Down
to work. The q^2 and x values can be calculated on an event to event basis using
a combination of tracking and calorimeter information.
In neutral current there are four ways of doing it, in charge current only one.
The analysis code/kumac should also be working out the numbers separately and
just display them on the webpage.
On to the event display/web page. I've reduced the code to a manageable level, and will send it to you in a following email. This is in case you don't receive it then I can just send it again, without having to type all this in.
it consists of the following directory structure
java_display/classes/
event/
geometry/
html/
classes contains the compiled JAVA code, which you should use as is for now. event contains a description of the event in ASCII form (see below). geometry contains the detector geometry. html contains the actual html page to be displayed.
If
you have a look inside them, you will find the bare minimum of stuff.
I hope this makes it easier to understand. My suggestion is you power up netscape/explorer
and try viewing the html file in the html/ directory.
This should mean you can see an event display and some text at the bottom.
OK. what now? My suggestion is to firstly look at the html file and get a vague idea what is going on, and what is calling what. ignore the geometry directory for now and the JAVA stuff. I still have no documention on that. it's not too important since all detectors look fundamentally like a cylinder to begin with.
Then
try editing/writing your own ASCII event file: Here is a summary of the WIRED
event format.
*
* p 960524
* k Px Py Pz E P charge trklen xv yv zv x y z eps z0 theta phi kappa colour
* ...
* v Px Py Pz E P charge trklen xv yv zv x y z eps z0 theta phi kappa colour
* ...
* e x y z value colour
* ...
*
* For tracks, (xv,yv,zv) (what Mark calls (x0,y0,z0)) gives the vertex
* position, while (x,y,z) gives the first measured point.
* (eps,z0,phi,theta,kappa) are the perigee parameters (for some * reason, only
the magnitude of kappa is given, scaled by 1000).
* where the record headers denote p=DAS date, k=TK, v=TV, e=TE * (value=0 for
hits). In all cases the colour is optional.
*
* Currently (xv,yv,zv) and (x,y,z) are offset (for k,v,e) so that * the primary
vertex is at (0,0,0). This would be better handled * in the event display.
Translation:
TK=track, TV=track after vertexing (WIRED doesn't distinguish
these except by default colour), TE=hit/calo.
OK. I also include a postsript file which describes the "perigree" parameters.
So
that should be enough to be getting on with.
If you don't receive the .tar.gz file immediately after this one, let me know.
Cheers,
mark.
Mark
Hilton wrote:
>
> Hi Mark,
>
> I have been waiting for our data to be analysed and our understanding of
the
> electron-proton scattering process to increase and I think that I am now
> ready to work on the event display. Myself and Jayesh Ramanlal will be
> working on it together.
>
> So far we want to display information from the calorimeter, TRD and the
CTD,
> and show values of q^2 and x (can these be calculated directly from the
> event data set or do we work them out separately and just display this
> number?).
>
> I would appreciate any information on XML as mentioned in your email and
the
> next step to create this event display. We also have got a ZEUS data file
to
> take event information from. What file format should this data be saved
as?
>
> I hope that these requests make sense if not mail me back to clarify. Thank
> you very much,
>
> Mark
Attachment Converted: "R:\DOS\EUDORA\tkparm.ps"
Created by Jayesh Ramanlal