\magnification=\magstep1 \parindent=0pt { % a front or cover page for EG docs suitable for inclusion inside % a titlepage environment in a LaTeX document % for use with Plain TeX uncomment the \nopagenumbers and the \eject \hoffset=0truein \hsize=6.25truein %\hoffset=.5truein %\hsize=5.25truein \vsize=10.25truein %---gives left and right margins of 1.5truein \font\small=cmssbx10 scaled \magstep2 \font\medium=cmssbx10 scaled \magstep3 \font\large=cmssbx10 scaled \magstep4 \nopagenumbers \hrule height 0pt \parindent=0pt %\parskip=0pt \large \rightline{EDOC???} \vskip .5truein \large EUROGAM PROJECT\par \vskip 1.5truein \hrule height 2pt \vskip 20pt \large NSF DATA ACQUISITION SYSTEM\par \vskip .5truein \baselineskip 25pt EUROGAM Database Requirements\par \vskip 20pt \hrule height 2pt \vskip 1truein \medium Edition 1\par \vskip 5pt October 1990\par \vfill \medium NSF Experimental Group\par \vskip 5pt UK Science and Engineering Research Council\par \vskip 5pt Daresbury Laboratory\par \vskip .5truein \eject } \centerline{\bf EUROGAM Database Requirements} \vskip .3in \centerline{\bf Edition 1, October 1990} \centerline{\bf Mike Bentley} \vskip .3in \quad \quad The following document outlines the requirements of a user accessible database for the EUROGAM array. The database should contain all the information necessary for setting up and running an experiment, and also for general information. \par \vskip 0.3in {\bf 1. Access} \par \vskip 0.2in \quad \quad The database should be accessible for reading from the EUROGAM control station as it will contain parameters necessary for setting up an experiment. It should also be accessible from the network, as users at remote stations should have the information available for reading only. Ideally, access from France should also be available. \par \quad \quad Clearly, input to the database will only be allowed selectively. For example, it is necessary for the detector laboratory staff to update the latest information on Ge detectors. Users in general will not be able to write to the database. The EUROGAM control system itself will be able to automatically update database parameters where necssary. \par \vskip 0.3in {\bf 2. Information to be contained} \par \vskip 0.2in \quad \quad The following is a list of parameters which should be stored along with an indication of where the information is obtained from, and how the information is provided. \par \vskip 0.1in (2.1) Array information \vskip 0.1in \quad \quad Each detector position in the array has a permanent number - as has been defined in the document EDOC046. For each array position, the following information should be contained. \par \vskip 0.1in (a) Number of the position \par \quad {\it information in EDOC046 - not to be changed} \par (b) Number of the "face" (12 faces in the dodecahedral array) - this is relevant as each face has one VXI card, one autofill manifold, one pre-amp supply etc. \par \quad {\it faces not defined yet - not to be changed once defined} \par (c) Angle of the detector with respect to the beam line \par \quad {\it information in EDOC048 - not to be changed} \par (d) Ge VXI channel number and BGO VXI channel number \par \quad {\it information to be written when setting up, and to be changed only when a VXI channel is changed} \par (e) Name of Ge detector currently occupying position \par \quad {\it information written during setup of the array - to be changed automatically by the control software when a detector is changed.} \par (f) Name of last Ge detector to occupy position \par \quad {\it information written automatically by computer - see above} \par (g) Name of BGO shield currently occupying position \par \quad {\it information written during setup of the array - to be changed automatically by control software when a detector is changed.} \par (h) Name of last BGO detector to occupy position \par \quad {\it information written automatically by computer - see above} \par (i) Number of the autofill manifold that fills detector position \par \quad {\it information not defined - to be changed only by detector laboratory staff when necessary} \par (j) Channel number of Ge HV supply for that position in the array \par \quad \quad {\it not defined yet - not to be changed once defined} \par (j) Channel numbers of BGO HV supplies for that position in the array \par \quad \quad {\it not defined yet - not to be changed once defined} \par \vskip 0.1in (2.2) Ge detector information. \par \vskip 0.1in \quad \quad Each Ge detector has a name assigned to it (see EDOC047). A typical name for a detector is GUOC5 - the first four letters define the type of detector, its country of origin and the manufacturer. The number at the end of the name is the number of the detector, and is particular to a detector. In the above example, detector number 5 refers only to GUOC5. If there are 45 detectors, they will be numbered 1 to 45. For each Ge detector, the following information will be required \vskip 0.1in (a) Name of detector \par \quad {\it each detector is named by Daresbury as soon as it is delivered in the country} \par (b) Physical characteristics of detector. These should include the following: \par \quad \quad (i) Manufacturer \par \quad \quad (ii) University owenership of the detector \par \quad \quad (iii) Size of Ge crystal (front diameter, rear diameter and length) \par \quad \quad (iv) Bias voltage - this information must be accessible by the high voltage control software. \par \quad {\it all the above information will be provided by the detector laboratory staff - updated when necessary} \par (c) Array information \par \quad \quad (i) Current position of detector in the array \par \quad \quad (ii) Last position of detector in the array. \par \quad {\it This information will be written or updated by the control software automatically when a detector is changed} \par (d) Performance characteristics \par \quad \quad (i) Last measured efficiency (IEEE standard) \par \quad \quad (ii) Last measured 1.33 MeV resolution for amplifier shaping times of 2 and 6$\mu$s \par \quad \quad (iii) Last measured 0.122 MeV resolution for amplifier shaping times of 2 and 6$\mu$s \par \quad \quad (iv) Last measured timing measurements for 0.122 MeV and 1.33 MeV $\gamma$-rays \par \quad \quad (v) A selected set of measurements from the manufacturers specification sheet. \par \quad \quad {\it all the above information will be provided by the detector laboratory staff - updated when necessary} \par (e) General comments including known faults \par \quad \quad {\it information provided by detector laboratory staff when necessary} \vskip 0.1in (2.3) BGO detector information \vskip 0.1in \quad \quad Each BGO detector has a name as defined in EDOC047. Like the Ge detector, it consists of a set of letters followed by the detctor number. For each BGO detector (or shield) the following information is required \vskip 0.1in (a) Name of detector \par \quad \quad {\it each detector is named by Daresbury when it is delivered} \par (b) Physical characteristics of detector \par \quad \quad (i) Manufacturer \par \quad \quad (ii) University ownership of detector \par \quad \quad (iii) Bias voltage for each of the 10 shield elements (labelled a to j - see EDOC46) - this information must be accessible by the high voltage control software. \par \quad {\it all the above information will be provided by the detector laboratory staff - updated when necessary} \par (c) Array information \par \quad \quad (i) Current position of detector in the array \par \quad \quad (ii) Last position of detector in the array. \par \quad {\it This information will be written during setup, and updated by the control software automatically when a detector is changed} \par (d) Performance characteristics \par \quad \quad (i) The last measured 0.667 MeV energy resolution. \quad {\it information will be provided by the detector laboratory staff - updated when necessary} \par \quad \quad (ii) A selected set of measurements from the manufacturers specification sheet. \par (e) General comments including known faults \par \quad \quad {\it information provided by detector laboratory staff when necessary} \vskip 0.3in {\bf 3. Operation of database} \vskip 0.2in \quad \quad Apart from providing users with information necessary to perform an experiment, the database should also provide information to the EUROGAM control system. For example, when it is required to apply the high voltage for the Ge detectors, the information that the HV control software requires is the value of the bias to applied for a particular detector position (each HV channel will correspond to a particular position in the array). This information is contained and retrieved from the database. The same philosophy applies to the BGO HV supply. When a detector (Ge or BGO) is placed, replaced, moved or removed in the array, this information must therefore be written to the database by the control software automatically. It is vital to ensure that this happens, as applying the wrong bias to a Ge detector can have serious consequences. \vfill \eject \end