Feature #7517
closed
detector name in hardware-carrier.xml
Added by Michelagnoli Caterina almost 11 years ago.
Updated almost 11 years ago.
Description
In the hardware-carrier.xml, for the carrier server in the address the detector name is given...
is that necessary? It is somehow given twice in this way...
thanksss
- Project changed from AGATA DAQ to Topology Manager
- Status changed from New to Feedback
- Assigned To set to Michelagnoli Caterina
hardware-carrier.xml file isn't part of topology manager software, it is used by one of the tool of the topology manager software.
Can you append the hardware-carrier.xml file to your ticket and give the number of the line which is a problem to you ?
Thanks in advance, xavier
Ci-dessous the part of the hardware-carrier.xml I was referring to (ok?)
I was just wondering if, since we give already somewhere else the relation carrier-detector, one can avoid to re-edit it here... but it may be not
so important...! thnaks a lot!
<!-- Carriers and Crystals relations -->
<!--
<!-- <device device_type="server" name="carrier-006_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/00C" path="." internal_ref="00C"></device> -->
<device device_type="server" name="carrier-041_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/01B" path="." internal_ref="01B"></device>
<device device_type="server" name="carrier-025_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/01C" path="." internal_ref="01C"></device>
<device device_type="server" name="carrier-062_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/00B" path="." internal_ref="00B"></device>
<device device_type="server" name="carrier-074_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/00C" path="." internal_ref="00C"></device>
<device device_type="server" name="carrier-005_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/04B" path="." internal_ref="04B"></device>
<device device_type="server" name="carrier-039_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/04C" path="." internal_ref="04C"></device>
<device device_type="server" name="carrier-071_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/05A" path="." internal_ref="05A"></device>
<device device_type="server" name="carrier-061_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/05B" path="." internal_ref="05B"></device>
<device device_type="server" name="carrier-069_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/05C" path="." internal_ref="05C"></device>
<device device_type="server" name="carrier-063_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/07B" path="." internal_ref="07B"></device>
<device device_type="server" name="carrier-014_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/06B" path="." internal_ref="06B"></device>
<device device_type="server" name="carrier-065_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/06C" path="." internal_ref="06C"></device>
<device device_type="server" name="carrier-070_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/07A" path="." internal_ref="07A"></device>
<device device_type="server" name="carrier-057_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/06A" path="." internal_ref="06A"></device>
<device device_type="server" name="carrier-028_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/07C" path="." internal_ref="07C"></device>
<device device_type="server" name="carrier-018_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/12A" path="." internal_ref="12A"></device>
<device device_type="server" name="carrier-035_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/12B" path="." internal_ref="12B"></device>
<device device_type="server" name="carrier-010_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/13A" path="." internal_ref="13A"></device>
<device device_type="server" name="carrier-013_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/13B" path="." internal_ref="13B"></device>
<device device_type="server" name="carrier-019_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/13C" path="." internal_ref="13C"></device>
<device device_type="server" name="carrier-006_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14A" path="." internal_ref="14A"></device>
<device device_type="server" name="carrier-015_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14B" path="." internal_ref="14B"></device>
<device device_type="server" name="carrier-042_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14C" path="." internal_ref="14C"></device>
<device device_type="server" name="agava_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/FRS" path="." internal_ref="FRS"></device>
thanks for the feedback
by detector do you mean crystal ?
And what's bothering you is the internal_ref attribute ?
I think I have understood your need, I'll implement it this after noon.
This line :
<device device_type="server" name="carrier-042_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14C" path="." internal_ref="14C"></device>
will become in your file:
<device device_type="server" name="carrier-042_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14C" path="."></device>
The topology manager will answer :
<device device_type="server" name="carrier-042_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14C" path="." internal_ref="14C"></device>
if the relations are present in the Data Base
it will return
<device device_type="server" name="carrier-042_server" port="2345" kind="CARRIER" address="http://scgw2.agata.daq:2020/14C" path="." internal_ref="###"></device>
if no relations to do the calculation are available
yes sorry by detector I meant crystal!
What I was meaning is that when you write the relation for a given crystal (!)
you already write which is the corresponding carrier(s) and here the name of the
crystal is somehow repeated (so one has to remember to change it there as well...)
but it is certainly not a sever problem...!! merci beaucoup
- Status changed from Feedback to Closed
- Assigned To changed from Michelagnoli Caterina to Grave Xavier
310:a8388e6f0e22 contains the requested feature.
There is no more need to fill internal_ref in the hardware-digitizer.xml and hardware-carrier.xml files.
318:e7cab8beeed0 is installed on scgw2 => closing the ticket
Also available in: Atom
PDF
Updated by 
Updated by Grave Xavier almost 11 years ago
Updated by