11 am: Changed configuration of power source for AIDA PSU (see paper logbook). Now both cables with power for
USB relay are connected to the 'C' unit of the F11 power supply. They use different socket pads, and share them
with power cables for raspberry pi and NIM crates. Situation intermediate to what we have on Tuesday.

Resolution of pulser peaks improved slightly w.r.t. yesterday, but still we have the high frequency noise
(500kHz) present (attachments).

12 pm: We found the FEEs crash (loose connection/synchronization) when we enable the fast discriminators (see
attach. 1). This could be in the case when some of the discriminator channels are triggering at a fast rate
(noise above threshold). We observed the same pattern a few times.

5 pm: During all afternoon we've not been able to put AIDA in an operational state. There is always one or more
FEEs that do not synchronize or loose connection. Also the fuse of the PSU broke and we had to replace them.
Source for state of the system could be related to current configuration of PSU power, or the presence of noise
we observed in last couple of days.


6 pm: Back to configuration of PSU from yesterday:

F11 power supply 'C' ---->----> PSU relays 1-4
                          |
                          |---> NIM crates, RPI, etc


F11 power supply 'B' ----> PSU relays 5-8



Started by checking the options. Loaded Options 2016May03-20.44.33. It looks like settings of ASICs are not the
standard ones (e.g. threshold 47). Tried restore settings in Save/Restore option. It worked for all but NNAIDA25
(fri22.png), but other have proper settings (but values of #25 also look ok!).

Performed 'Check ASIC clock timestime' in systemwide checks: all failed (fri23.png)
Performed 'Check ADC calibration' in systemwide checks: all passed, except for nnaida26 (fri24.png)
Master Timestamp Control -> Perform ReSYNC: worked for all modules except nnaida26


we lost connection to 26..... (fri26.png)

Attempted ADC calibration of NNAIDA26 (FADC align and control) failed (fri27.png)

Disabled NNAIDA from Run Control, and Reset all modules. But now after reset the setup button does not appear,
just Reset one as if the action had no effect.

Tryed restore settings again. Again nnaida25 returned problem, but yet again nnaida26 is the one that actually
doesn't have proper ASIC settings. Confirmed this with 'Check ASIC control' (fri29.png). Is there an error in the
error report message of 'Restore Settings'?

We checked cable connections (HDMI, ethernet), and afterwards NNAIDA26 keeps giving problems. We give up on it,
remove it from DAQ configuration (https://elog.ph.ed.ac.uk/AIDA/189), and system nos seems to be runing ok
without it.


8 pm: disconnected all remaining cables from MACB->other crates (only daq correlation in macb1), and went back to
yesterdays configuration of PSU power with all power from 'C'

F11 power supply 'C' ---->----> PSU relays 1-4
                     |    |
                     |    |---> PSU relays 5-8
                     |
                     |--->---> NIM crates, RPI, etc

14.30 Adjusted and checked insertion of AIDA snout into BRIKEN (CH2)n moderator.
      up-down    AIDA snout appears centred (@ (CH2)n centre) and tracks into (CH2)n moderator with no
significant vertical movement
      left right AIDA snout appears centred (@ (CH2)n centre) and tracks into (CH2)n moderator with ~3mm
horizontal movement left to right (looking upstream)

15.28 DSSSD bias/leakage current OK - see attachments 1-2
      FEE64 temperatures OK - see attachment 3

      B2F/F11 temperature +24.8 deg C, d.p. +11.8 deg C,  RH 44.4%

16.00 Power off to place ac mains distribution unit between AIDA and BRIKEN

18.34 Power up PCS request for remote data/diagnostics collection

00:11 BigRIPS has started a new run at 00:10:42 run 0165.
      AIDA subrun R16_357 was about halfway (~1 GB) at 00:11.
      BRIKEN run 21 ( so-called 170331_0012_Mg40 )

      Check clock status: FEE64 module nnaida1 global clocks failed, 6 [ as usual, and it is set to ch 2 ]
      ADC calib all pass
      Clock timestamp, passed
      Sync counter error, passed
      Sync pulses all consistently near 3 x 10^7
      Memory info from Linux FEE64 all around 35k to < 40k
     
      Sync check on the BRIKEN terminal is looking all consistent to me.

      Temperatures are seen as attachment 1, temps_31_a.png
      Biases and leak currents seen as attachment 2, bias_31_a.png

      As for what I've checked then we continue on in what appears to be a stable condition.
     
01:12 I can see BigRIPS team at their DAQ PC about to change the run.
      2017-03-31 01:12:24 BigRIPS run 0166 starts
      AIDA subrun R16_372 is 75% finished at 1:12
      BRIKEN run 22, [ 170331_0114_Mg40 ] -- timestamp beginning at 1:14 means they are almost exactly at the
beginning of AIDA R16_373

      Check clock status, ibid to above
      Check ADC calib, ibid
      Check ASIC clock timestamp, ibid
      Check sync errors, ibid
      Check sync pulses, 3.2 x 10^7 consistently
      Check FEE64 memory, 36k to 37k.

      Sync check at BRIKEN is still running and shows the clocks are lined up.

      Continue.
     

02:10 BigRIPS begins a new run, number 0167
      AIDA subrun R16_386 finished at 2:10, so BigRIPS 0167 should correspond nicely with the start of AIDA R16_387
      BRIKEN run number 23 [ 170331_0214_Mg40 ]

      All six (6) system wide checks were performed.  The situation remains stable as above.

03:13 BigRIPS starts a new run at 3:12:51
      AIDA R16_402 is about 50% complete at 3:13
      BRIKEN 24 [ 170331_0314_Mg40 ]

      All system-wide checks are passed.  Number of sync pulses is ~3.7 x 10^7

03:33 Bored so here's some spectra, attachment 3 as pulses_31_b.png.  It looks good.

04:10 BigRIPS run 0169 began at 2017-03-31 04:09:50
     AIDA is R16_416 50% though at this time.
     BRIKEN 25 [ 170331_0413_Mg40 ]

     All checks passed.  I'm not just writing it, but they were performed :)

     See attachment 4 for bias.  had screencapped temp but forgot to update so it was just a clone of attachment 1 (this
was noticed at 8:07)

04:58 Beam operators called.  They stopped the beam so they can exchange the carbon stripper foil.
     AIDA R16_428 was 25% through at 4:58.

05:02 R16_429 is at 600 MB I hear the chime to indicate the beam is back
     BigRIPS 2017-03-31 05:02:57 run 0170 is started
     BRIKEN run 27 [ 170331_0504_Mg40 ] -- NB: Run 26 was junk (some mistake)

     All six (6) system wide checks are a go.  3.7 x 10^7 is the sync pulse count.
     Continue.

05:12 I show you the AIDA look good in attachment 5 spec_31_c.png

06:10 still waiting on BigRIPS to notice what time it is.

06:14 BRIKEN sends the resync.  (this note is written at 7:11..see below)

06:16 R16_447 Jorge realizes there are no neutrons in BRIKEN, and we realize the second beam physicist is on the phone.

06:29 Beam physicists hang up the phone...2017-03-31 06:29:30 BigRIPS run 0171
     AIDA run R16_451 is almost exactly beginning at 6:29
     BRIKEN run number 28
     The system wide checks are consistent as before
          FEE64 module nnaida1 global clocks failed, 6 
          Check sync pulses sees 3.9 x 10^7
     
06:36 - I asked the BigRIPS team the situation.  Basically, they calibrate the faraday cup and also three plastic
scints near F0 (primary target) for calibrartion (cross section estimation) purposes.
     So it seems in this time THEY have the beam yet we do not because it is not reaching all the way to F11 the
entire time.
     Though I do not want to bother the operators with too many questions, it can be that parts of BigRIPS run 0170
near the end will not correlate with our data.

07:11 - I had not caught that BRIKEN sent the resync.  It was confirmed that it was the only resync issued tonight.
     Please see the attachment 6 "spec_31_d.png", though I'm not sure it would be useful

07:47 Not sure the situation.  Beam physicists were near their DAQ PC for a bit, then on the phone, but their run has not
restart.
     AIDA run R16_469 at this time, just to note.

07:57 2017-03-31 07:55:33 BigRIPS run 0177 is started.  Evidently run 0176 is skipped somehow.
     AIDA R16_471 was at 1.9 GB at 7:57 so probably it mostly correlates with the start of the BigRIPS run.
     BRIKEN run number 29 (?) [ 170331_0758_Mg40 ]

     [8:15 - confirmed the problem with beam physicists was a DAQ issue.  Thus BigRIPS run 0172 is junk, and they took
some time to resolve their issue.]
      
     System-wide checks look normal.  4 x 10^7 sync pulses
     Attachments 7 and 8 have bias and temp ("bias_31_e.png" and "temp_31_e.png")

08:07 When doing the temperature this time, I realized that an early temperature "temp_31_b" was just a clone of
"temp_31_a" as I forgot to refresh.  Now the attachment numbering changes as I delete it, and the elog is updated to
correctly reflect the new ordering.  I should be more careful.

08:56 BigRiips start run 0174
      End of AIDA file R16_485
      BRIKEN file 31
      System wide checks all ok *except* nnaida1 fails global clocks 6
      ASIC check all ok

09:44 BigRips stopping the beam
      Half way through AIDA file R16_498

09:57 System wide checks all ok *except* nnaida1 fails global clocks 6

10:01 BigRips start run 0175
      Start of AIDA file R16_502
      BRIKEN file 32

10:11 Biases and leakage currents ok (See attachment 9)

10:19 BigRips start run 0176
      End of AIDA file R16_506
      
10:23 BRIKEN start file 33
      AIDA on file R16_507

11:21 BigRips start run 0177
      End of AIDA file R16_521
      BRIKEN start file 34
      System wide checks all ok *except* nnaida1 fails global clocks 6
      Temperatures ok (See attachment 10)

12:21 BigRips start run 0178
      AIDA file end of R16_536
      BRIKEN start run file 35
      System wide checks all ok *except* nnaida1 fails global clocks 6
      ASIC load check ok

12:43 Biases and leakages are ok (See attachment 11)
      
13:20 BigRips run 0179
      AIDA halfway through R16_551
      BRIKEN start run file 36
      System wide checks all ok *except* nnaida1 fails global clocks 6

13:39 bigRips run 0180
      AIDA file end of R16_555

14:44 System wide checks all ok *except* nnaida1 fails global clocks 6
      ASIC load check ok
      Temperatures all ok (See attachment 12)
      Biases and leakage currents ok (see attachment 13)

15:14 BigRips is stopped
      AIDA file R16_579

15:16 BigRips started run 0181
      AIDA file  end of R16_579

15:24 BRIKEN starts file 37
      AIDA file 3/4 of R16_581

16.18 BigRIPS file 0182.
      Just after start of R16_595.
      BRIKEN file 38 starts @ 16.21.

16.55 All system-wide checks ok except nnaida1 fails global clocks 6.
      Temps, bias and leakage currents (see attachment 14) all ok.
      
17.18 BigRIPS run 0183.
      ~1/2 way through R16_609.
      BRIKEN run 39.

18.27 BigRIPS file 0184 started. Start of R16_627.

18.31 Beam stopped at F11 for stripped foil change. Very end of R16_628.

18.38 Beam returned to F11. 1.3GB through R16_630.
      BigRIPS file 0185.
      BRIKEN run 40.

19.15 System-wide checks as previously.

19.38 BigRIPS file 0186. End of R16_654

19.43 BRIKEN file 41 started.

20.48 BigRIPS file 0187 started for 30Ne tuning.
      BRIKEN will not be taking data.

20:50 AIDA stopped on file R16_663
      Stopped as end of 39Na and the start of the BigRIPS sweep of settings.

20:52 BigRips starting with 30Ne

20:53 Started AIDA file R17. Centring beam along ZDS.
      F11 rate ~50cps. All variable degrader in (19mm).
  
20.58 BigRIPS file 0188 started.   

21.04 30Ne setting started. BigRIPS file 0189 started.

21.20 30Ne stopped for 31Ne centring. BigRIPS file 0190.

21.27 BigRIPS file 0191 started for 31Ne yield measurement. 
      (JLT has spoken with operators and it seems up until now beam has been stopped at F7. We are taking this to be the
case unless advised otherwise.)

21.59 BigRIPS file 0192 started on 32Ne yield setting. Beam to F11.

22.01 R17 stopped and R18 started.

22.05 32Ne setting finished.
      R18 stopped.
      
22.19 BigRIPS file 0194 started for 34Ne setting.
      AIDA run R19 started.
      BRIKEN run 43.
      Currently 10mm degrader but LISE predicts everything should pass through.

22.43 Degrader changed to 19mm Al at start of R19_6.
      LISE predicts implants in DSSD#2.

23.23 Beam stopped to F11. 1.8 GB into R19_15.

23.25 Beam returned to F11. 1GB into R19_16.
      BigRIPS file 0195.
      Degrader reduced to 16.8mm Al.

Overnight
      Degrader OUT
      DAQ ran OK - data file R22
      DSSSD #3 (N1419 ch #2) tripped, re-enabled OK 

      Attachments 1-15 from R22
      nnaida10 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      nnaida2 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      nnaida1 DSSSD #1 ASIC #1-4 HEC ADC spectra + hit patterns
      HEC fast comparator LLD 0x8 - standard ASIC parameters

09.06 Beam off

09.36 Beam on

09.46 R23
      HEC fast comparator LLD 0x8 -> 0x2

c. 10.00 beam lost, cyclotron re-tuning

10.56 R23 stopped

11.20 FEE64 firmware update - /MIDAS/Aida/FEE_Riken_Apr14_26.bin
      See attachment 16

11.58 R24
14.35 R24 stopped

      R25 diode link threshold nnaida1 0xca -> 0xba, nnaida3 0x11 -> 0x18
14.52 R25 stopped

      R26 diode link threshold nnaida1 -> 0xbc, nnaida3 -> 0x1c
15.06 R26 stopped

15.00 Beam off

15.25 BigRIPS changed to 110Zr setting. Tuning.

17.05 Beam on

Ignore R27_0

17.06 R28
17.49 R28 stopped

Ignore R29, R30

22.56 diode link threshold 0xca -> 0xb6 (cf. preAmp ref 0xb2)
                           0x11 -> 0x2c (cf. preAmp ref 0x30)

      ASIC parameters saved to      /MIDAS/DB/EXPERIMENTS/AIDA/2015Apr30-diode-mod

23.18 Fast LEC/MEC discriminators disabled:
      Mask bits 31->0, 63->32 *not* 0->31 and 32->63 as implied by Disc Controls window

         Chan                 Mask
                             31->0      63->32
nnaida1                        0x0   0x4000000
nnaida2  ch 22, 26       0x4400001   0x8000000
nnaida6  ch  1                 0x1         0x0
nnaida9  ch 45 "               0x0      0x2000
nnaida10 ch 31 "        0x82000000  0x80000000
nnaida11 ch 55 "               0x0    0x800000
nnaida13                       0x0   0x4000000
nnaida16 ch 55 "               0x0    0x800000

00.04 Local Controls -> Timing O/P Control Register 0xc -> 0xe (OR64) https://elog.ph.ed.ac.uk/AIDA/79

09.18 SN changed degrader to 5.7mm Al (4mm + all variable degraders + additional 1mm)

09.24 R53 continues

      DSSSD#1 I_L to 8.16uA
      FEE64 temps OK
      Julabo FL11006 recirculating chiller OK - op temp +20 deg C

      Example HEC ADC spectra DSSSD #1-3 (attachments 1-12) 

09.59 R53 ends 
      Beam off - problem with refrigeration plant for BigRIPS quads

10.39 FEE64 temperatures (attachment 13)

10.51 Check ALL ASIC Control parameters 

11.15 Stat and Hit spectra for all AIDA FEE64 modules (attachments 14-15)
      Illustrates common noisy channels for each FEE64 channels 1 & 55 of 0-63
   

11.28 R54 
      Short run without beam, BNC PB-4 pulser frequency ~1Hz

12.55 R54 ends OK

14.00 Plot of leakage currents up to now included.
      Gradual increase in all detectors over course of experiment.
      Bias voltage on detector 1 (ch 1) increased to +150V at 0900 on 03/05, causing 
      an increase in I_L over preceding value.

16.00 Beam expected 21.00

18.30 No beam.
      HV ch 2 tripped (det 3)
      Reset HV and observed expected leakage current

19.00 HV ch 1 also tripped.
      Increased HV to +150V. Leakage current @ 8.02uA

3ph 100VAC/50Hz to Julabo FL11006 3ph 230VAC/50Hz via local transformer

Started AIDA at 11:54am, writing to disk: file BG18OCT2/R5, stopped at 19:14

pict1: HV supply
pict2: temperature
pict3: spectrum in stat, layout2
pict4: statistics

pict5: sum spectra at 18:20 (3.4 hours)

system power off and unbiased

R1118 ended OK

R1119 DAQ GO, check AIDA SYNCs OK, toggle merge input etc 

Merge then halted with the usual unable to connect to COUNTER, nnaida1, nnaida1 etc error messages
so unable to reset, setup etc

Power-cycling and rebooting

Stack has been changed in configuration from a 6 DSSD stack to 8 DSSD stack.
What was detectors 1-6 are now 3-8 with 2 new detectors added to the front.

The stack order is now:
    DSSD 1 3058-25 Top
    DSSD 2 3058-2
    DSSD 3 3058-4
    DSSD 4 3058-3
    DSSD 5 2998-23
    DSSD 6 3058-5
    DSSD 7 3058-6
    DSSD 8 3058-7  Bottom

To handle the new detectors an additional 4 FEE modules 8 FEE64 were installed in the system with MAC addresses:
    FEE 25 - 2B 09 E7
    FEE 26 - 2B 22 55
    FEE 27 - 2A F6 D4
    FEE 28 - 2A ED 8F
    FEE 29 - 2A D0 1A
    FEE 30 - 2B 33 0C
    FEE 31 - 2A B6 45
    FEE 32 - 2A B2 B2

FEE Mapping is now:
                FEE Number
    DSSD     A    B    C    D
     1       25   28   30   31
     2       26   27   29   32
     3       1    20   22   23
     4       2    19   21   24
     5       9    12   14   15
     6       10   11   13   16
     7       17   4    6    7
     8       18   3    5    8

     All 4 new p side cables were made using 33" ribbon cables
     The n side cables for detector 2 were made using 37" cables
     The n side cables for detector 1 were made using 39" ribbon cables (37" was to short)

     Non-isolated cables related to C connector on DSSD

     The detectors were placed inside the snout with two reference lines for insertion.
     The first labelled as June 18 6 stack will place the centre of the detector stack (Between detectors 5 and
6) in the centre of BRIKEN
     when inserted up to this line.

     Distance from edge of BRIKEN to centre is 37.5cm

     The second mark is 1cm along from this and is labelled June 18 8 stack. This positions the centre of the
stack (Between detectors 4 and 5), what would be 3 and 4 if only 6 detectors)
     in the centre of the BRIKEN array.

     One thing to note is that with 8 detectors getting the snout on is a tight fit and can push down the rods
the detectors are held on. This was previously
     a friction fit between the rods and the snout base. The rods had to be pulled out slightly to allow for the
extra length needed for 8 detectors.
     To aid in the rods were not slipping grub nuts were moved to the bottom and locked in position. This may
not hold the strain of someone pushing the snout against them so caution
     is still advised when putting this on.

     When in the 8 stack configuration DSSD 1 is 4.5cm from the end of the snout. To support more detectors
longer rods would be needed though.

[UPDATED 22/4: initial LISE file had incorrect thickness for MACi plastic]

Calculations for Al degrader thickness required to implant ions in AIDA DSSD stack.

Calculations are based on LISE files from main experiment, and done for settings with expected longest and shortest range 
of 
ions 
before implantation setup: 
- LISE++ for the 95Br BigRIPS setting : B1_U_BefissionZDSLAA_95Br_6mmF1.lpp
- LISE++ for the 85Ga BigRIPS setting : B1_U_BefissionZDSLAA_85Ga_6mmF1.lpp

Setup after last beamline detector (IC): 180cm Air + Al degrader + MACi (7mm plastic@45 degrees) + AIDA (3mm silicon) + 
thick 
Al 
plate (1 cm).


+ 84Zn setting (long range):

 - Al degrader of 1 mm required in front of implantation setup to stop 84Zn activity in AIDA (end of stack).  The range in 
Si 
is 
reduced by ~1.1 mm per each mm of Al added in degrader. 

 - Activity from heavier (more intense) isotopes seems to be implanted at similar location as more exotic isotopes (always 
considering 1p knockout channel, might be worth looking also at unreacted channels).

+ 94Se setting (short range):
 
 - Activity stopped before AIDA. We'll need to remove MACi if we want ions implanted in AIDA (unless the tail of energy 
distribution 
after secondary target is very large).
 
 - If we remove the MACi plastic, we would need 2 to 3 mm of Al degrader to stop ions in AIDA (assuming the 1mm veto after 
segmented 
MACi plastics remain).



See attachments for detailed description

We've constructed a beta trigger with the signals from the p-side of the three DSSDs (OR of all fast
discriminator channels of each FEE).

det1 -> NNAIDA#6 -> MACB#10.2
det1 -> NNAIDA#10 -> MACB#3.4
det2 -> NNAIDA#2 -> MACB#10.3
det2 -> NNAIDA#14 -> MACB#3.2
det3 -> NNAIDA#1 -> MACB#10.4
det3 -> NNAIDA#13 -> MACB#3.3

beta-trigger is OR of all above MACB trigger outputs. Diagram for logic circuit is in paper logbook.


Bellow are some oscilloscope sceenshots. Some things to note about the MACB trigger outputs:

- all show multiple outputs for each pulser input. Some channels seem to have higher level for such 'multiplicity'.

- the width of the outputs varies for different channels (from ~40 ns to ~300 ns)

- the delay between the pulser signal and the output from the MACB is quite large, and also different for each
MACB (measured from ~800 ns up to 2 usec).


Scope screenshots: 

 - light blue is the trigger output from Pulser
 - dark blue is output from trigger channel of MACB

 MACB#10.2: tek00001.tif
 MACB#3.4: tek00002.tif
 MACB#10.3: tek00005.tif
 MACB#3.2: tek00007.tif
 MACB#10.4: tek000011.tif
 MACB#3.3: tek000018.tif

A first online analysis code is running now in Desktop 4 aidas1

The source code and executable are in 

/homes/npg/AIDAonline

The following command launches the program from the above directory:

aidas1> ./AIDA-online.exe 

The code is set to update histograms every 10e6 events (about once per minute?).

Otherwise, click on the terminal running the program and press any key. This will produce the following menu:

online monitor is paused;
press 0 <Enter> to stop, 1 <Enter> to restart;


If <1> is selected the histogram are updated and the execution is continued.

If <0> is selected the program requests a confirmation and then exits (without saving the histograms, that's the
next step).


A few (interesting) screenshots attached.

Some first analysis of building events to look for implants and decays

Using both DISC and slow comparator values for time-stamp (whatever is available). Clearly there are some ADC
hits with a very early value for their corresponding time-stamp, that result in negative or very large dTS
values. Probably safer to use only ADC data for now (it's likely the simple algorithm used to correlate
discriminator hits and ADC hits can not cope with current conditions of ADC hits >> DISC hits):

time_stamp_dist_disc.png

Comparing analysis of file R51_3 for the two conditions: using the Fast discriminator data when available for
low energy range, or using only the time-stamp from the ADC hits.


The first two figures (time_stamp_dist_disc.png, XY_implant_disc_R51.png) are for including DISC hits as
time-stamp for event building: some have much smaller values than corresponding ADC hits, so the event is cut
short and we see a small number of identified implants.

Second set of plots is the same data but using only the timestamp for the slow comparator of the low energy
range. The number of identified events is much higher (compare 'Integral' value of the stats box).

Online spectra to monitor condition during run R51.

Position and energy spectra indicate implantation in 2nd DSSD. 

Tracking spectra is consistent with a larger beam angle on the horizontal direction.

Online monitor program for AIDA is in  /homes/npg/AIDAonline

The program is now running in Desktop#4 of aidas1, with mode to forward data to BRIKEN PC enabled (if more than one instance forwarding data are running, the code could get stalled).

The current code identifies implant and decays candidates by conditions on hit multiplicity, energy of n-side vs p-side, and cluster size. These are noted with the implant-flag and decay_flag variables, which are transmitted in the data buffer to the BRIKEN PC. If the flags are greater than one these are candidated for implants or decays at different DSSDs (valid codes, 1, 2, 3, 11, 12, 13; for now the program looks for implants in DSSD #2 and #3, and decays in all 3 DSSDs).

A few sample histograms from analyzing run R53_20 are attached

+++++++++++++++ HOW TO +++++++++++++++++++++++++++++++++++++++++++++

To start it type AIDA-online.exe from that directory:

aidas1> ./AIDA-online.exe
AIDA be like: in da F11!!
 declaring my class objects
I'm here
 and here...
... source ...
... unpacker ...
... calibrator ...
... analysis ...
 initializing things
-  DataSource: attaching online to shared memory area with ID= 0.
dataSpy Shared buffer area 0 (/SHM_110205) located at 0xca9f9000
dataSpy Current age 26182952 index 40
+  DataSource attached online  **************

Setting Transfer Block Size 65536
Setting Transfer Mode 3
TCP transfer library version 4.0T
2: TCP socket send buffer was 16384 - now 249856
2: TCP socket receive buffer was 87380 - now 249856
2: TCP socket created OK - now connecting to 10.32.6.54 port 10310
2: Connected to 10.32.6.54 port 10310
+  DataSource.cpp:: initialized data trasfer protocols  **************

 Calibrator.cpp:: LoadParameters() reached end of parameter file. Loaded new value for 202 parameters.
     InitAnalysis(): initialize histograms for evend clustering
db    Analysis.cpp: Initialized histograms and canvas for this step
 *** ANALYSIS: TIME WINDOW=  2000
almost in looop
before looop


Once it's runnig, one can reach a menu by typing 'space' (or any keyboard hit) in the terminal, and the following menu appears (note: select 1 to update histograms and dsiplay data at begining of run):

online monitor is paused;
press 0 <Enter> to stop, 1 <Enter> to update hitograms, 2 <Enter> to clear histograms;
1
You chose restart
monitor restarted, press <Space> to pause;
  Analysis::UpdateHistograms()... updating


online monitor is paused;
press 0 <Enter> to stop, 1 <Enter> to update hitograms, 2 <Enter> to clear histograms;
2
You chose clear
monitor restarted, press <Space> to pause;
        Analysis::ResetHistograms(): all histograms have been reset...

 

Plots of corr-scaler vs event number in Root files for 100Kr(?) setting: go4_40XX.root.

Same script, and plot description, as in the ELOG entry for go4_30XX.root files: https://elog.ph.ed.ac.uk/AIDA/112

These are accumulated events for each run (to map event# -> run number):

Number of entries in PID tree= 2606359 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4001.root
(accumulated= 2606359)
Number of entries in PID tree= 2609120 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4002.root
(accumulated= 5215479)
Number of entries in PID tree= 2607343 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4003.root
(accumulated= 7822822)
Number of entries in PID tree= 2603241 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4004.root
(accumulated= 10426063)
Number of entries in PID tree= 2602664 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4005.root
(accumulated= 13028727)
Number of entries in PID tree= 2597915 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4006.root
(accumulated= 15626642)
Number of entries in PID tree= 2606679 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4007.root
(accumulated= 18233321)
Number of entries in PID tree= 2604197 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4008.root
(accumulated= 20837518)
Number of entries in PID tree= 2604402 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4009.root
(accumulated= 23441920)
Number of entries in PID tree= 2604980 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4010.root
(accumulated= 26046900)

Number of entries in PID tree= 2608074 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4011.root
(accumulated= 2608074)
Number of entries in PID tree= 2609093 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4012.root
(accumulated= 5217167)
Number of entries in PID tree= 2608080 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4013.root
(accumulated= 7825247)
Number of entries in PID tree= 2605479 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4014.root
(accumulated= 10430726)
Number of entries in PID tree= 2598820 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4015.root
(accumulated= 13029546)
Number of entries in PID tree= 2603066 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4016.root
(accumulated= 15632612)
Number of entries in PID tree= 2605692 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4017.root
(accumulated= 18238304)
Number of entries in PID tree= 2611812 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4018.root
(accumulated= 20850116)
Number of entries in PID tree= 2607623 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4019.root
(accumulated= 23457739)
Number of entries in PID tree= 2607970 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4020.root
(accumulated= 26065709)

Number of entries in PID tree= 2609207 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4021.root
(accumulated= 2609207)
Number of entries in PID tree= 2602567 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4022.root
(accumulated= 5211774)
Number of entries in PID tree= 2613624 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4023.root
(accumulated= 7825398)
Number of entries in PID tree= 2612418 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4024.root
(accumulated= 10437816)
Number of entries in PID tree= 2615720 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4025.root
(accumulated= 13053536)
Number of entries in PID tree= 2615051 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4026.root
(accumulated= 15668587)
Number of entries in PID tree= 2610490 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4027.root
(accumulated= 18279077)
Number of entries in PID tree= 2608960 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4028.root
(accumulated= 20888037)
Number of entries in PID tree= 2599656 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4029.root
(accumulated= 23487693)
Number of entries in PID tree= 2611283 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4030.root
(accumulated= 26098976)

Number of entries in PID tree= 2597833 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4031.root
(accumulated= 2597833)
Number of entries in PID tree= 2574550 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4032.root
(accumulated= 5172383)
Number of entries in PID tree= 2592651 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4033.root
(accumulated= 7765034)
Number of entries in PID tree= 2598995 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4034.root
(accumulated= 10364029)
Number of entries in PID tree= 2605854 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4035.root
(accumulated= 12969883)
Number of entries in PID tree= 2603045 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4036.root
(accumulated= 15572928)
Number of entries in PID tree= 2596530 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4037.root
(accumulated= 18169458)
Number of entries in PID tree= 2582396 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4038.root
(accumulated= 20751854)
Number of entries in PID tree= 2573176 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4039.root
(accumulated= 23325030)
Number of entries in PID tree= 2579368 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4040.root
(accumulated= 25904398)

Number of entries in PID tree= 2576076 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4041.root
(accumulated= 2576076)
Number of entries in PID tree= 2571398 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4042.root
(accumulated= 5147474)
Number of entries in PID tree= 2561229 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4043.root
(accumulated= 7708703)
Number of entries in PID tree= 2555236 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4044.root
(accumulated= 10263939)
Number of entries in PID tree= 2550104 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4045.root
(accumulated= 12814043)
Number of entries in PID tree= 2617418 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4046.root
(accumulated= 15431461)
Number of entries in PID tree= 2625206 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4047.root
(accumulated= 18056667)
Number of entries in PID tree= 2619409 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4048.root
(accumulated= 20676076)
Number of entries in PID tree= 1540255 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_4049.root
(accumulated= 22216331)

The firmware of all FEEs was updated to the version in FEE_GF_Feb16_16.bin (https://elog.ph.ed.ac.uk/AIDA/215).
This provides a 25 MHz clock output from MACB, plus a manual reset request signal.

Attached are screen captures from smooth updating procedure. 

Checked correlation request signal from output2 of MACB: it's a pulse with ~180ns width and -0.7V. We could only
observe it when selecting 'act no all FEEs' in Correlation Control browser window (looking at MACB module on the
top of the tree). However, we didn't check that the output is produced from only one MACB module, if we select
the one of the corresponding FEE.

Some comments regarding source run for beta-gamma calibration, to complement EURICA16 elog entry:
http://ribf-exp.riken.jp/elog/EURICA+U-campaign+2016/

This corresponds to run files R7_* (AIDA) and BiCocal_run003.lmd and BiCocal_run004.lmd (run files could
increase for EURICA)

EURICA trigger: AIDA trigger (#1) OR pulser (~25MHz). 

Trigger rate: about 170 Hz

AIDA trigger: Detector 1 with low multiplicity condition; N=1, 2 or 3 within window of 5x40ns

AIDA trigger rate: Det1 X = 7500 (nnaida17+nnaida22)
                   Det1 Y = 800 (nnaida17+nnaida22)
                   coincidence X+Y= 330

The trigger output of MACB has an inverted logic (0 when trigger, -0.5 V otherwise) 

Attached are screenshots documenting conditions during run.

8am: closed file: R7_110.gz in AIDA, BiCocal*005.lmd in EURICA

> Some comments regarding source run for beta-gamma calibration, to complement EURICA16 elog entry:
> http://ribf-exp.riken.jp/elog/EURICA+U-campaign+2016/
> 
> This corresponds to run files R7_* (AIDA) and BiCocal_run003.lmd and BiCocal_run004.lmd (run files could
> increase for EURICA)
> 
> EURICA trigger: AIDA trigger (#1) OR pulser (~25MHz). 
> 
> Trigger rate: about 170 Hz
> 
> AIDA trigger: Detector 1 with low multiplicity condition; N=1, 2 or 3 within window of 5x40ns
> 
> AIDA trigger rate: Det1 X = 7500 (nnaida17+nnaida22)
>                    Det1 Y = 800 (nnaida17+nnaida22)
>                    coincidence X+Y= 330
> 
> The trigger output of MACB has an inverted logic (0 when trigger, -0.5 V otherwise) 
> 
> Attached are screenshots documenting conditions during run.

No
The clock is in 10 ns intervals 
So 5 => 50ns
The trigger is Fast NIM standard. Talk to Tom
With such a short time ,a lower limit of 1 and high rate discriminators the Trigger will appear true all the time.