As promised a few weeks ago, the DAQ CVS repository has been reorganized.
The new CVSROOT is sun2.hirg.bnl.gov:~daq/oncs_cvs.
All the old daq modules have been moved to the new repository. Code not
yet in CVS, but to be imminently committed, includes the vxworks kernel
build stuff, TPC pad monitor and high-voltage and trigger control.
A motion was put forward by Christian Holm to place the ONCS CVS repository
on AFS. As nobody seconded it and I did not get any more feedback on the
issue, for now, the repository will stay on sun2. I do like the proposal
and am looking into resolving issues of accessing AFS from our online and
daq computers.
K.O.
P.S. For your enjoyment, the original proposal is attached below:
On Tue, Oct 19, 1999 at 05:46:43PM -0400, Konstantin Olchanski wrote:
>
>
>
> Subject: Proposal for the BRAHMS ONCS CVS repository
> Date: 13 OCT 1999
> Author: K.Olchanski
>
>
> This is a proposal to combine all the "online" software under a single
> CVS tree, tentatively called "ONCS" (online computing system). This
> CVS repository will contain the DAQ components (vxworks kernels,
> code running on vxworks, event builder, run control), slow controls
> components, trigger controls, raw data handling utilities and maybe
> detector monitoring software.
>
> The next section present the details of the CVS tree implementation.
>
> The CVS tree will be physically located on sun2.hirg.bnl.gov
> in the "daq" account, under ~daq/ONCS_CVS. The ~daq disk is
> backed up by the BNL EPOCH automatic backup system.
>
> Local sun2.hirg.bnl.gov accounts will be required to access the
> repository from offsite, using CVSROOT "sun2.hirg.bnl.gov:~daq/ONCS_CVS".
> If requiring local accounts is too much of a bother, we can try to
> use the "pserver" feature of CVS. This would also allow "anonymous"
> read-only CVS access.
>
> An incomplete list of proposed modules under ~daq/ONCS_CVS is:
>
> libBrOnline - sources (.h and .cpp) for the Raw Data handling library,
> libBrOnline.a
> utils - "one C file" utilities, such as rawdump.cpp, DaqWrite.cpp
> (Note1: the current DAQ "online" module will be split in these two modules.)
> (Note2: "utils" is reserved for code written in C and C++. For shell, TCL
> and perl scripts, use the "scripts" module.)
> evb - DAQ event builder
> java - DAQ Run control and GUI software. This is the current
> DAQ "java" module. At some point it may be split
> into separate modules, but this is outside of the
> current proposal.
> config - current DAQ "config" module.
> scripts - current DAQ "scripts" module. To contain any shell, TCL
> or perl scripts that do not fit elsewhere.
> vxworks-sbe-5.2
> vxworks-mv2305-5.3
> vxworks-mv2305-5.4
> - repository for the corresponding vxworks BSPs
> daqppc - DAQ code that runs on Vxworks MVME (PPC) VME boards.
> current DAQ "fastbus" module.
> daqsbe - DAQ code that runs on Vxworks SBE VME boards.
> current DAQ "fastbus/sbe" module.
> tclvx - TCL implementation for vxworks
> current DAQ "tclvx" module.
> trigger - trigger control code.
>
> hv1440 - high voltage controls. Or should they be all
> hv4032 - in one module?
> hv1450 -
>
>
> I am looking forward to questions and suggestions. I guess the most
> questionable parts of the proposal are remote access to the CVS
> repository and the list of modules.
>
>
> K.O.
>
>
> --
> Konstantin Olchanski
> Physics Department, Brookhaven National Laboratory, Long Island, New York
> olchansk@bnl.gov
-- Konstantin Olchanski Physics Department, Brookhaven National Laboratory, Long Island, New York olchansk@bnl.gov
This archive was generated by hypermail 2b29 : Tue Feb 01 2000 - 20:35:05 EST