<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Paul,<br>
<br>
No, we are not changing the rules now as everything is already
standardized following GlueX-doc-2293, which is the final document
on labeling. This has been the case for years and all the cables
are already labeled for all detectors, and correctly. Nerses and
everyone else have had this document for years and the TOF has
been set for that long also and all the cables and PMTs are
labelled correctly now.<br>
<br>
GlueX-doc-2019 is dated to 2008, if you look carefully. This was
actually a slide I presented at a collaboration meeting to serve
as guidance wrt the detector orientation in the hall. Granted that
not many people were involved with these issues at the time but if
you look carefully, all the labels were not "as built". For
instance the FCAL has no specifics on the beam "hole"; the TOF
does not have two PMTs, the BCAL has layers, etc.<br>
<br>
So, let's stick with norm: GlueX-doc-2293.<br>
<br>
Best regards,<br>
Fernando<br>
<br>
<br>
On 5/13/2014 12:07 PM, Paul Eugenio wrote:<br>
</div>
<blockquote cite="mid:46456E0C-651D-4401-9DD4-E0F5B4A6B822@fsu.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi,
<div><br>
</div>
<div>There is some confusion here. GlueX-doc-2293 is a xlsx
sheet titled “Hall D Crates, Chassis & Cable Maps” whereas
GlueX-doc-2019 is a pdf titled “Hall D Detector Naming
Convention” dating back to 31May2012.</div>
<div><br>
</div>
<div>It looks like the problem originated with an incomplete
scheme for the TOF in GlueX-doc-2019 in that it does not account
for individual TOF PMTs. This ambiguity could be fixed
logically by extending the convention as Nerses proposed or
modified as was done for the cable labels to provide a less
logical but condensed scheme. Both are correct as the current
document goes, but since a decision was made to modify the
naming scheme for TOF (and we have all channels labeled that
way) we should have the doc-2019 updated to reflect this.
Fernando, since you are the author of doc-2019, can you modify
it.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Paul</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div>On May 13, 2014, at 11:31 AM, Fernando J Barbosa <<a
moz-do-not-send="true" href="mailto:barbosa@jlab.org">barbosa@jlab.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">Hi Hovanes,<br>
<br>
I think you meant to say GlueX-doc-2293, which is the actual
implementation. I distributed this to all involved a long
time ago.<br>
<br>
GlueX-doc-2019 dates back to 2008 and is intended, still, to
provide the user with orientation information on the
detector and what information should be included.<br>
<br>
Best regards,<br>
Fernando<br>
<br>
<br>
On 5/13/2014 10:03 AM, Hovanes Egiyan wrote:<br>
<blockquote type="cite">Until now the slow controls was
using<br>
GlueX-doc-2019 "Hall D Detector Naming Convention" for
guidance. If it is currently obsolete, it needs to be
removed<br>
or labeled as such, or needs to be updated.<br>
Hovanes.<br>
<br>
<br>
On 5/13/2014 9:35 AM, Paul Eugenio wrote:<br>
<blockquote type="cite">Nerses,<br>
<br>
Fernando is correct.<br>
<br>
We need to follow the GlueX convention. We do not
want to have HV cable labels, off line channels, and
slow control channels with names that differ.<br>
<br>
Hussein will show this naming in his update today.<br>
<br>
<br>
On a more general note. You have implemented a naming
scheme for other slow control systems. You should
check that they follow the GlueX standard (i.e. you can
just look at the HV cable labels or talk with Fernando).<br>
<br>
<br>
Paul<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On May 12, 2014, at 10:57 PM, Fernando J. Barbosa <<a
moz-do-not-send="true" href="mailto:barbosa@jlab.org">barbosa@jlab.org</a>>
wrote:<br>
<br>
<blockquote type="cite">Hi Paul, Nerses,<br>
<br>
Specifically,<br>
TOF-N-1 to 44<br>
TOF-S-1 to 44<br>
TOF-UP-1 to 44<br>
TOF-DW-1 to 44<br>
<br>
Obviously, the same paddle has TOF-N-1 and TOF-S-1 and
so forth.<br>
<br>
Best regards,<br>
Fernando<br>
<br>
----- Original Message -----<br>
From: Fernando J. Barbosa <<a
moz-do-not-send="true"
href="mailto:barbosa@jlab.org">barbosa@jlab.org</a>><br>
To: Paul Eugenio <<a moz-do-not-send="true"
href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a>><br>
Cc: GlueX Particle ID Mailing List <<a
moz-do-not-send="true"
href="mailto:halld-pid@jlab.org">halld-pid@jlab.org</a>>,
Nerses Gevorgyan <<a moz-do-not-send="true"
href="mailto:nerses@jlab.org">nerses@jlab.org</a>><br>
Sent: Mon, 12 May 2014 22:44:49 -0400 (EDT)<br>
Subject: Re: [Halld-pid] Naming the TOF HV channels<br>
<br>
Hi Paul, Nerses,<br>
<br>
Gluex-doc-2018 should be followed. All the cables are
already labeled accordingly.<br>
<br>
Best regards,<br>
Fernando<br>
<br>
<br>
<br>
----- Original Message -----<br>
From: Paul Eugenio <<a moz-do-not-send="true"
href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a>><br>
To: Nerses Gevorgyan <<a moz-do-not-send="true"
href="mailto:nerses@jlab.org">nerses@jlab.org</a>><br>
Cc: GlueX Particle ID Mailing List <<a
moz-do-not-send="true"
href="mailto:halld-pid@jlab.org">halld-pid@jlab.org</a>><br>
Sent: Mon, 12 May 2014 17:06:48 -0400 (EDT)<br>
Subject: Re: [Halld-pid] Naming the TOF HV channels<br>
<br>
Hi Nerses,<br>
<br>
I like what you propose, and as I mentioned it is
important the follow a general convention.<br>
<br>
My concern that we keep the plane orientation
information which is provided in the {N,S,T,B} scheme.
To change these later values from letter to number
would would require a change of the [1,2] to something
like [H(orizontal),V(ertical)]. I say we keep it as
you propose, but I will pass this information on to
others in the TOF group for their concerns.<br>
<br>
<br>
Paul Eugenio<br>
<br>
<br>
On May 12, 2014, at 3:40 PM, Nerses Gevorgyan <<a
moz-do-not-send="true" href="mailto:nerses@jlab.org">nerses@jlab.org</a>>
wrote:<br>
<br>
<blockquote type="cite">Hi Paul,<br>
<br>
The current naming scheme I've implemented is:<br>
<br>
TOF:hv:[1,2]:[1-44]:{N,S,T,B}:property<br>
<br>
For example: TOF:hv:1:23:T:status<br>
<br>
Nerses<br>
<br>
<br>
hvCaenApp/src/tt.d<br>
05/02/14 10:59 -ում, Nerses Gevorgyan-ը գրել է:<br>
<blockquote type="cite">Dear TOF Experts,<br>
<br>
I started to work on the TOF HV slow controls.<br>
We need Your opinion how to name the channels in
the EPICS, so the name would be not too long and
at the same time uniqely will identify hardware.<br>
<br>
The are 2 documents GlueX-doc-2019 "Hall D
Detector Naming Convention" and<br>
GlueX-doc-2293 "Hall D Crates, Chassis & Cable
Maps" where on the D2-8-TOP sheet is the HV Crate
and channel connections are described.<br>
<br>
The Detector Naming convention proposes the name
TOF-plain-paddle (ex: TOF-2-11)<br>
Since, each paddle has 2 PMTs attached with 2
separate HV channels it could be extended like
TOF-plain-paddle-side (ex: TOF-2-11-2)<br>
<br>
In the Crates, Chasis and Cable Maps the channels
are like TOF-{N,S,UP,DW}-[1-44] (ex: TOF-UP-24)<br>
<br>
We already have some rules in our naming scheme
implemented for other detectors, which we would
like to be applied to TOF too.<br>
<br>
1) The delimeter is not '-' but ':'<br>
2) The name is a hierarchy like
DETECTOR:HV_TYPE:SUBDETECTOR:SUBSUBDETECTOR:...:CHANNEL_PROPERTY<br>
For example for TOF it would be something like:<br>
<br>
TOF:hv:PLAIN:PADDLE:PADDLE_SIDE:status or<br>
TOF:hv:PLAIN:DETECTOR_SIDE:CHANNEL:status or<br>
TOF:hv:DETECTOR_SIDE:CHANNEL:status<br>
<br>
Where PLAIN could be {1,2} or {F,B} (i.e. Forward,
Backward) or {U,D} (i.e. Upstream, Downstream)<br>
PADDLE could be [1-22]<br>
PADDLE_SIDE [1-2] or it could be {N,S,U,D} (i.e.
North South Up Down) or {N,S,T,B} (i.e. North
South Top Bottom) or {L,R,T,B} (i.e. Left Right
Top Bottom)<br>
DETECTOR_SIDE could be {1,2,3,4} or it could be
{N,S,U,D} (i.e. North South Up Down) or {N,S,T,B}
(i.e. North South Top Bottom) or {L,R,T,B} (i.e.
Left Right Top Bottom)<br>
The channel, I guess, would be just number in the
range 1-44<br>
<br>
As You see, there are many possibilities.<br>
I would prefer in each field to have 1 letter or
couple of digits.<br>
Secondly, I'd like to have many hierarchies but to
clearly identify the channel.<br>
<br>
Regards,<br>
Nerses<br>
</blockquote>
</blockquote>
-- <br>
Prof. Paul Eugenio<br>
Florida State University<br>
Department of Physics<br>
Tallahassee, Florida, USA 32306<br>
<br>
(850) 325-0314<br>
<a moz-do-not-send="true"
href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Halld-pid mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Halld-pid@jlab.org">Halld-pid@jlab.org</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-pid">https://mailman.jlab.org/mailman/listinfo/halld-pid</a><br>
<br>
_______________________________________________<br>
Halld-pid mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Halld-pid@jlab.org">Halld-pid@jlab.org</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-pid">https://mailman.jlab.org/mailman/listinfo/halld-pid</a><br>
<br>
<br>
</blockquote>
-- <br>
Prof. Paul Eugenio<br>
Florida State University<br>
Department of Physics<br>
Tallahassee, Florida, USA 32306<br>
<br>
(850) 325-0314<br>
<a moz-do-not-send="true" href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Halld-pid mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Halld-pid@jlab.org">Halld-pid@jlab.org</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/halld-pid">https://mailman.jlab.org/mailman/listinfo/halld-pid</a><br>
</blockquote>
<br>
</blockquote>
<br>
<span><barbosa.vcf></span></blockquote>
</div>
<br>
<div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">-<br>
Paul E.<br>
1981 C&C Landfall 38<br>
S/V Johanna Rose<br>
Carrabelle, FL</div>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>