ADC 400F Manual descargar pdf (Pagina 11)

Chapter 2. Setting up the software

The software modiﬁcations needed to make the above setup work can be divided into three tasks:

1. Telling the software what electronics we are using.

2. Telling the software how to respond to event triggers.

3. Telling the software how to analyze the data acquired.

2.1. Readout software

In order to tell the software about our electronics we are going to develop a C++ class for our module.

That class will be a derived class but we don’t need to concern ourselves with the details of the parent

class. Like all of the software tailoring we need to do, most of the details are hidden and we need only to

ﬁll in a few holes.

The following commands will make a new directory and copy the skeleton ﬁles to it:

mkdir -p ~/experiment/readout

cd ~/experiment/readout

cp /usr/opt/daq/pReadoutSkeleton/* .

2.1.1. Modifying the Readout Skeleton

Now that we have obtained a copy of the Skeleton ﬁle we can began to think about the modiﬁcations we

need to make. We need to tell the software what kind of module we are using, how to initialize it, how to

clear it, and how to read it. We will do this by creating a class called by MyEventSegment. In order to

follow good coding practice and to make our code as versatile as possible we will write our class in two

separate ﬁles, a header ﬁle and an implementation ﬁle. Start by creating a ﬁle called MyEventSement.h.

It should look like this:

Example 2-1. Header for MyEventSegment

This is the header file to define the MyEventSegment class, which

is derived from CEventSegment. This class can be used to read

out any number of CAEN modules covered by the CAENcard class.

Those cards include the V785, V775, and V792.

1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 73 74

Sin comentarios

ADC 400F Manual Pagina 11