| |
ID |
Date |
Author |
Subject |
|
|
389
|
Tue Oct 26 16:08:46 2021 |
NH | FEE and Adaptor board groundings | > During investigations into the noise today by NH and OH a couple of findings were made on the grounding of the FEEs and Adaptor boards.
>
> - The adaptor boards have no connection to the FEE ground over the ERNI connector
> - Currently we are providing one via a ground cable between the FEE Al cooling and the Lemo ground on the adaptor board
> - The Al cooling plate is not electrically isolated from the copper plate on the ASIC and both are connected to the electrical ground on the FEE
> - Verified with 0 resistance between plate and HDMI ground shield
> - The FEE is electrically isolated from the frame but when cabling is connected they show 0 resistance
> - With electrics disconnected but water still connected they show 200kOhm
> - With the bias core going to FEE14 and the braid going to FEE8 better performance in FEE14 is obtained by disconnecting FEE8 adaptor board from the ground
> - The cost of this is the rate of FEE8 goes up to 300k
> - It is essential to have the adaptor board ground on the FEE ground but unsure why having both adaptor boards connected to their respective grounds makes one worse
> - The resistance between all FEEs is not zero. Some show a 5Ohm and some show a 35Ohm resistance between each other
>
The adapter boards have ERNI ground pins, and the FEE64 has a grounded plane on its ERNI connector, unfortunately the orientation means the ground pins do not touch the plane on the FEE64 and hence no contact is made
Would require installing board "upside down" but then the ASIC connections would be wrong. A new adapter board layout would be necessary to correct this
Tomorrow will investigate direct connection of all FEE64s to mechanical ground via dedicated copper cable.
Currently FEE64s get ground via Pulser(->NIM) ((weak ground)), HDMI(->NIM) ((possibly?)) and Power(->PSU) (primary grounding)
HV Bias is floating at NIM side and so does not provide ground path (intentional)
TD may have ideas to isolate pulser from AIDA FEE ground
Unsure if HDMI ground is a problem
The ground quality via the power may not be ideal over long cables of relatively thin wire. (5 * 20 AWG) and then unsure how ground of PSU connects to mechanical ground
Explicit grounding may help keep resistance between FEEs < 1 Ohm.
Will also mount a DSSD and see situation without pulser, with/without mechanical grounding and maybe with various LK jumpers. |
|
|
29
|
Thu Mar 21 14:10:10 2019 |
NH | FEE Temperatures | All 12 FEEs powered up, and temperatures are OK.
Passed ASIC checks and system wide checks - now checking cabling and to mount snout. |
|
|
275
|
Sat Apr 24 05:17:51 2021 |
ML | End of beam | Beam has now stopped (end of expriment) and background measurements starts. |
|
|
156
|
Mon Mar 16 07:25:24 2020 |
NH | End of Experiment | 08:25 Beam Stopped, end of S480
Tape Server stopped at R12_2097
Started again in no storage mode
Will leave compressing runs |
|
|
34
|
Fri Mar 22 15:44:20 2019 |
NH | End of 22.03.2019 | End of the day - Detector unbiased and FEE64s turned off for the weekend as they won't be monitored.
Water will remain on. |
|
|
541
|
Tue Mar 19 10:17:30 2024 |
NH | Dry Run 2024 - 19th March 24 | AIDA has 8 FEEs and 1 DSSSD
Aida08 (HDMI#12) had no WR again, I moved it to a different MACB and now it gets WR
The MACB (currently with jsut HDMI#10) seems issues, check/replace the upstream HDMI and thent eh MACB (after dry run!)
DSSSD#1 biased to -120 V, leakage current 5.6 uA (fig 1)
(also on Grafana)
Temps OK fig2
System Checks (fig3-5)
Clocks OK
aida07 fails calibration, others OK
WR OK (aida04 0x10, seems OK)
FPGA OK
Did "Synchronise ASIC clocks" to align ASIC clocks
(Notes for scalers: SC41L HDMI 5, SCI41R HDMI 9)
18:12 FRS is taking beam, AIDA is powered off and unbiased |
|
|
69
|
Wed Oct 30 11:51:08 2019 |
CA, TD, NH | Detector biasing | 12.51 - detector bias and leakage currents - detector 3 has no current
- other detectors ok
13.13 - tried changing from HV3 cables to HV4 - still open circuit
- tried different permutations of moving HV-4 braid and core cables (high voltage to ground connections)
(dssd3)
(all directions defined as if looking upstream)
- core -> bottom, braid -> left open - circuit
- core -> top, braid -> right trips at 8V
- core -> bottom, braid -> right open - circuit
- core -> top, braid-> left trips at 8V
- removed jumpers - still trips
13.36 - testing continuity of bond wires on dsssd 3208-14 & 3208-15
- observe 20 ohm resistance on p+p and p+n bond wires
19:41 - dsssd 1 and 2 not biasing, 3 ok.
- changed bias configuration -> HV core 1 & 2 now on top, braid on right
- ribbon cables for DSSSD #1 & #2 p+n junction strips down were misaligned
- all detectors biased succesfully
HV cable configuration (looking upstream): HV-1 Core -> top-inner (FEE 1)
HV-2 Core -> top-middle (FEE 5)
HV-3 Core -> bottom-outer (FEE 11)
HV-1 Braid -> right-inner (FEE 2)
HV-2 Braid -> right-middle (FEE 6)
HV-3 Braid -> left-outer (FEE 12)
Attachment 3 - rough sketch of HV cable configuration, looking upstream.
|
|
|
639
|
Wed Jun 5 08:34:47 2024 |
JB. AM, MP, MY | Detector bias tests | We are trying to bias each system on its own and in sequence biasing each other detector system to see the interdependence.
HV OK. TEMP OK. Attachment 1 &2.
9.43 bPlast unbiased, BB7 unbiased. Attachments 3-6 is the noise situation with only AIDA biased (bPlast was biased but turned off after AIDA was biased.)
10/16 FEEs < 20k noise. Max noise is 250k. Downstream AIDA appears to be seeing additional noise since S100.
11:21 Returning after an hour the noise has increased significantly in many channels. Scale changed to 10000 in histograms, it appears that the problem is from a couple hot channels.
11:41 'Power' cycled AIDA turned off. bPlast turned on, on its own, then BB7. bPlast doesn't seem to notice anything.
12:21 bPlast and BB7 on. AIDA ON. Rates and histograms given by attachment 7-8. More FEEs noisy, but same level as 11:21. There appears to be the same noisy channel in all of the FEEs (?) Some grounding not properly accounted for, or a wire touching somewhere (?)
13:55h: AIDA & BB7 on. Rates and histograms given in attachments 9-10. Same level as bplast & AIDA on. Same noisy channels in FEEs. According to Nic, these correspond to the end of the ribbon cables & is normal.
13:59 AIDA, bPlast & BB7 on before lunch. Same levels of noise as in previous combinations (attachments 11-12).
So it seems we can run with the three sub-systems biased simultaneously.
|
|
|
11
|
Thu Dec 6 15:31:40 2018 |
TD, CA, NH | December 6th 2018 | 15.32 1.8.W spectra for aida01, aida09, aida10, aida11, aida12 (attachments 1, 2, 3)
2 and 3 expanded in Y and X direction respectively
15.35 good event statistics (attachment 4)
FEE temperatures (attachment 5)
leakage currents/bias (attachment 6)
17.20 attachment 7 - loose ground wire
attachment 8,9,10 - pictures of wire connections
attachment 11 - side on view of dsssd mounted in aida snout
17.28 Pulser widths:
aida10 -> 101.24
aida09 -> 136.22
aida11 -> 66.31
aida12 -> 87.17
aida01 -> 15.29 |
|
|
104
|
Fri Dec 6 20:34:56 2019 |
CA, DK, NH | Dec 6 Night Shift | 21.35 AIDA DAQ currently running, TapeService on, not writing to storage
System wide checks ok
Attachments 1-3: temperatures, good event stats, detector bias/leakage currents ok
22.04 waiting for beam. Possibility of fragments, further news to come
22.43 expecting fragments with 300 MeV/u 40Ar primary beam
histograms zeroed
00.31 still waiting for beam
detector bias/leakage currents ok (see google spreadsheet)
FEE64 temps and good event statistics ok
02:02 still awaiting beam - issues with interlock
03:17 beam tuning - centering primary beam on target
03:43 beam reached AIDA, fragmentation beam (see elog entry by DK for PID)
primary beam 300 Mev/u 40Ar, fragments in region of 34Si
started writing to file Dec19/R2 at rate ~ 4000 kb/s
histograms zeroed
03.49 system wide checks all ok
attachments 4-6:
temperatures ok
bias/leakage currents ok
good event statistics ok, except aida09 running slightly fast
04:03 attachments 7-8 - 1.8.H energy spectra
- no high energy events seen in aida10 -> checked ASIC control
- still no high energy events in aida10
04:09 attachment 9 - rate spectra for all FEE modules
04.16 attachment 10 - 1D hits for all FEE modules
04.19 beam stop - file R2_3
04:52 beam back on - file R2_6 - rate of ~ 5000 ions per spill
06:13 temperatures ok
good event statistics ok (aida09 still running fast) - attachment 11
detector bias/ leakage currents ok - see google spreadsheet
all system wide checks ok
1.8.H spectra - attachments 12/13
06:20 attachment 14 - rate spectra for all FEE modules
attachment 15 - 1D hits for all FEE modules
still no high energy events in aida10
|
|
|
103
|
Thu Dec 5 22:00:11 2019 |
CA, DK, NH | Dec 5 Night Shift | 15:30
TD found the merger was running at ~43 Mb/s
The odd-numbered FEE64s all had significant (>200k) disk rates
ALL LEC/MEC fast discriminators and increased slow comparator from 0xa to 0x14
Merger rate dropped to a more nominal value like 2.3 Mb/s
Settings not saved
40Ar beam 300 MeV/u expected, but SIS problem at the moment.
23:00
Leak currents are stable as previously (20-21 Nov) and entered to Google spreadsheet
S4 vault is closed.
Presently AIDA is running without tape storage
System wide checks:
Master clock / aida01 sync reports error as expected;
All white rabbit decoders fail, but they are just off by 1 bit (no problem)
Everything else okay.
Stats look okay, but keep in mind above discriminator threshold -- see attachment 1
Temperatures fine -- see attachment 2
MBS looks okay -- we see a possible hint for the 1 bit difference with an "unexpected data word" -- see attachment 3
Data rate is 1.7 Mb/s, merger okay -- see attachment 4
23:30
Now we wait for the beam
00:05
Attachments 5-11: results of system wide checks after collecting sync errors and WR errors from baseline - all ok
00:25
Histograms zeroed at 00:25.
00:35
1.8.L pulser peak widths
FEE64 width(ch)
1 92
2 131
3 75
4 97
5 89
6 117
7 90
8 87
9 223
10 58
11 112
12 126
no peak observed on aida09
For comparison, pulser peaks measured on 13/11/19:
pulser peak widths:
FEE width (ch)
aida01 - 130
aida02 - 168
aida03 - 83
aida04 - 83
aida05 - 200
aida06 - 148
aida07 - 250
aida08 - 81
aida09 - 134
aida10 - 190
aida11 - 333
aida12 - 149
2:00
40Ar beam tuning is finished. Intensity at S4 is about 3 kHz per spill. 1 spill per / 10 seconds
MBS system cannot be used for online merging tonight, because NeuLAND group left their connection open
We can merge offline using the White Rabbit timestamps
Remove the beam blocking steel flange from in front of AIDA et al.
Writing to file Dec19/R1
03.20 Rate, Stat, 1.8.L, 1.8.H, 1.8.W spectra - attachments 13-20
Observe
light ions in 1.8.L spectra
low energy (<1.5GeV) heavy ions in 1.8.H spectra with most heavy ions stopping in DSSSDs 1 & 2
Stat hit patterns indicate broad (c. 5cm FWHM) centred heavy ion peak
03.24 Detector biases & leakage currents OK - attachment 21
FEE64 temperatures OK - attachment 22
Good event statistics (12 of 12 < 50k) - attachment 23
System wide checks
List All Sync Error Counters - attachment 24
List all Sync Received Counters - attachment 25
Baseline invoked earlier c. 00.05
Collect all SYNC Error Counters for Baseline
Collect All White Rabbit status Error Counters for Baseline
04:07 2.6 mm Al degrader. 300Hz beam. 300 MeV/u 40Ar beam.
04.14 pulser peak seen in aida09 after performing ASIC check-load earlier in shift - width = 219 ch
04.45 1.8.H energy spectra (attachment 26/27)
06:08 attachments 28-30: detector bias/leakage currents ok
temperatures ok
good event statistics ok
all system wide checks ok
08:49 DAQ stop/start. TapeServer writing to No Storage. End of beam.
|
|
|
79
|
Fri Nov 1 09:30:17 2019 |
NH | Database error stopping run? | Strange error about Database options appearing during run stop.
Does not seem to affect stopping/starting/data? |
|
|
68
|
Wed Oct 30 08:06:49 2019 |
CA, TD, NH | DSSSD stack | Ribbon cables fitted with kapton PCB couplers -> 3 isolated + 1 non-isolated for each cable length/DSSSD
Ribbon cable lengths:
without kapton PCB coupler (cm) - 40, 47, 51.5
with kapton PCB coupler (cm) - 50.5, 57.5, 62
gap between plastic and dsssd - 15 mm
length between top of snout and dsssd - 5cm |
|
|
535
|
Wed Mar 13 13:02:19 2024 |
JB, NH, HA, MA | DSSD 1 biasing tests | Dismounted Snout and biased DSSSD1 channels
leftmost waifer working
middle waifer reaches 90V then current ramps up
rightmost waifer reaches 80V then current ramps up
DSSSD2 had fingerprint near connections, as shown in the attached image some had been squashed. |
|
|
382
|
Mon Oct 18 13:03:23 2021 |
OH | DHCPd.conf backup | |
|
|
617
|
Sun Apr 28 15:49:58 2024 |
TD | DAQ restart short(er) cut |
16.45 aida04 stopped producing data
DAQ STOP (workspace 2, display 1, browser 'Run Control' tab)
aida04 did not stop, all other FEE64s stopped
restart Merger (workspace 3, display 2, select 'NewMerger' icon)
SETUP Merger (workspace 3, display 1, browser 'NewMerger' tab)
GO Merger (workspace 3, display 1, browser 'NewMerger' tab)
aida04 now stops
disable *all* #1 data transfer
DAQ GO (workspace 2, display 1, browser 'Run Control' tab)
check WR timestamps OK (workspace 2, display 1, GSI WR Timestamp Control)
DAQ STOP (workspace 2, display 1, browser 'Run Control' tab)
enable *all* #1 data transfer
DAQ GO (workspace 2, display 1, browser 'Run Control' tab)
No reboot or power cycle required. Just clear the Merger data links, restart DAQ.
|
|
|
398
|
Wed Mar 2 09:08:44 2022 |
OH | DAQ Status 2nd March 2022 | DAQ was found yesterday with none of the FEEs reporting any good events on any FEE - attachment 1
Temperature menu is still responsive and all FEEs report a temperature
Looking at the white rabbit timestamps aida09 has a gibberish timestamp - attachment 2
Merger shows no data arriving as expected - Attachment 3
Merger data buffers for each FEE - attachment 4
Merger time errors - attachment 5
DAQ has not yet been restarted in case Patrick wanted to look. |
|
|
399
|
Wed Mar 2 10:05:13 2022 |
OH | DAQ Status 2nd March 2022 | > DAQ was found yesterday with none of the FEEs reporting any good events on any FEE - attachment 1
> Temperature menu is still responsive and all FEEs report a temperature
> Looking at the white rabbit timestamps aida09 has a gibberish timestamp - attachment 2
> Merger shows no data arriving as expected - Attachment 3
> Merger data buffers for each FEE - attachment 4
> Merger time errors - attachment 5
>
> DAQ has not yet been restarted in case Patrick wanted to look.
Looking at the first attachment..... aida09 has rebooted. So it is not setup at all.
This has caused the NewMerger to hang .... which surprises me .... as I thought it was designed to spot a bad FEE and continue with the rest.
Yes I will have a look today as I'm in Daresbury.
More later ...... |
|
|
631
|
Thu May 9 09:08:26 2024 |
TD | Current NewMerger install - aida-gsi | [npg@aidas-gsi MIDAS]$ ls -l
total 524
drwxrwxr-x. 2 npg npg 156 Mar 17 2021 Aida
drwxrwxr-x. 2 npg npg 4096 Jul 13 2015 bin_Linux64
drwxrwxr-x. 4 npg npg 38 Jul 3 2018 config
drwxr-xr-x. 3 npg npg 22 Jan 23 2019 config_ORIG
drwxr-xr-x. 3 npg npg 17 Jan 23 2019 Data_Acq
drwxrwxr-x. 25 npg npg 4096 Aug 19 2020 DataPackage
drwxrwxr-x. 3 npg npg 25 Aug 29 2019 DB
drwxr-xr-x. 3 npg npg 25 Jan 23 2019 DB_ORIG
lrwxrwxrwx. 1 npg npg 14 May 30 2019 Embedded -> /home/Embedded
drwxrwxr-x. 2 npg npg 4096 Mar 17 2021 ISOL_Aida
drwxrwxr-x. 2 npg npg 4096 Nov 29 2018 ISOL_Aida_PreApr9
drwxrwxr-x. 7 npg npg 87 Jul 8 2009 lib
drwxrwxr-x. 2 npg npg 4096 Sep 19 2012 lib_Linux64
drwxr-xr-x. 5 npg npg 47 Jan 23 2019 Linux
drwxrwxr-x. 6 npg npg 58 Feb 22 2018 linux-ppc_4xx
drwxr-xr-x. 6 npg npg 58 Jan 23 2019 linux-ppc_4xx_ORIG
drwxrwxr-x. 3 npg npg 73 Feb 16 2022 log
-rwxrw-r--. 1 npg npg 12862 Jul 9 2009 midasicon.ico
-rwxrw-r--. 1 npg npg 773 Jul 23 2012 midasicon.png
-rwxrwxr-x. 1 npg npg 772 Jan 20 2019 MIDASNewGen_BuildAIDA.txt
-rwxrwxr--. 1 npg npg 2532 Jan 19 2019 MIDASNewGen_BuildCore.txt
drwxrwxr-x. 14 npg npg 4096 Feb 22 2018 MIDASpackages
drwxrwxr-x. 6 npg npg 124 May 14 2022 NewMerger
-rw-rw-r--. 1 npg npg 118873 Oct 18 2019 NewMergerdiff.log
-rw-rw-r--. 1 npg npg 118971 Oct 18 2019 NewMergerdiff.log~
drwxrwxr-x. 5 npg npg 52 Jan 8 2019 NewMerger_PreApr9
drwxrwxr-x. 6 npg npg 124 Mar 12 2020 NewMerger_PreMar21
drwxrwxr-x. 7 npg npg 104 Oct 17 2019 NewMerger_PreOct19
-rw-r--r--. 1 npg npg 230517 Mar 12 2020 NewMerger.tgz
drwxr-xr-x. 14 npg npg 4096 Jan 23 2019 OLD
drwxr-xr-x. 3 npg npg 17 Jan 23 2019 SOAP
drwxrwxrwx. 4 npg npg 67 Aug 19 2021 SpecData
drwxrwxr-x. 3 npg npg 21 Nov 15 2019 TapeServer
drwxr-xr-x. 3 npg npg 21 Jan 23 2019 TapeServer_PreFeb21
drwxrwxr-x. 3 npg npg 21 Nov 15 2019 TapeServer_PreMar21
drwxr-xr-x. 2 npg npg 44 Feb 2 2021 tcl
drwxr-xr-x. 12 npg npg 152 Jan 23 2019 TclHttpd
drwxrwxr-x. 11 npg npg 155 Oct 26 2017 TclTkpackages
lrwxrwxrwx. 1 npg npg 26 May 30 2019 XilinxLinux -> /home/Embedded/XilinxLinux
[npg@aidas-gsi NewMerger]$ ls -lR
.:
total 32
-rw-rw-r--. 1 npg npg 15096 Apr 16 2019 Aida_ASICreadout.c
drwxrwxr-x. 3 npg npg 23 Oct 18 2019 Html
drwxrwxr-x. 2 npg npg 172 May 14 2022 include
drwxrwxr-x. 8 npg npg 256 May 14 2022 MergeServer
-rw-rw-r--. 1 npg npg 11048 Aug 29 2019 R3B_readout.c
-rw-rw-r--. 1 npg npg 152 Oct 17 2019 README
drwxrwxr-x. 2 npg npg 34 Apr 29 2021 tcl
./Html:
total 0
drwxrwxr-x. 6 npg npg 187 Oct 13 2020 NewMerger
./Html/NewMerger:
total 60
lrwxrwxrwx. 1 npg npg 21 Oct 18 2019 Html -> /MIDAS/NewMerger/Html
drwxrwxr-x. 2 npg npg 6 Aug 26 2019 LinkRates
-rw-rw-r--. 1 npg npg 1210 Aug 26 2019 NewMerger.js
-rw-rw-r--. 1 npg npg 9417 Aug 29 2019 NewMerger.tcl
-rw-rw-r--. 1 npg npg 9332 Aug 26 2019 NewMerger.tcl~
-rw-rw-r--. 1 npg npg 13052 Aug 27 2019 NewMerger.tml
-rw-rw-r--. 1 npg npg 13851 Aug 26 2019 NewMerger.tml~
drwxrwxr-x. 2 npg npg 82 Oct 13 2020 Options
drwxrwxr-x. 2 npg npg 102 Oct 13 2020 RunControl
drwxrwxr-x. 2 npg npg 192 Aug 29 2019 Stats
./Html/NewMerger/LinkRates:
total 0
./Html/NewMerger/Options:
total 24
-rwxrwxr-x. 1 npg npg 725 Aug 26 2019 Options.js
-rwxrwxr-x. 1 npg npg 3934 Aug 26 2019 Options.tcl
-rwxrwxr-x. 1 npg npg 7864 Aug 27 2019 Options.tml
-rw-rw-r--. 1 npg npg 7864 Aug 27 2019 Options.tml~
./Html/NewMerger/RunControl:
total 44
-rw-rw-r--. 1 npg npg 4791 Aug 26 2019 implementation.tcl
-rw-rw-r--. 1 npg npg 1643 Aug 26 2019 stats.defn.tcl
-rw-rw-r--. 1 npg npg 539 Aug 26 2019 stats.tcl
-rw-rw-r--. 1 npg npg 12328 Aug 29 2019 sys.tcl
-rw-rw-r--. 1 npg npg 12231 Aug 26 2019 sys.tcl~
./Html/NewMerger/Stats:
total 52
-rw-rw-r--. 1 npg npg 2880 Aug 26 2019 MergeStatsALL.tcl
-rw-rw-r--. 1 npg npg 1013 Aug 26 2019 MergeStats.js
-rw-rw-r--. 1 npg npg 1534 Aug 26 2019 MergeStatsSINGLE.tcl
-rw-rw-r--. 1 npg npg 4259 Aug 26 2019 MergeStats.tcl
-rw-rw-r--. 1 npg npg 8467 Aug 27 2019 MergeStats.tml
-rw-rw-r--. 1 npg npg 8338 Aug 26 2019 MergeStats.tml~
-rw-rw-r--. 1 npg npg 1829 Aug 29 2019 stats.defn.tcl
-rw-rw-r--. 1 npg npg 1943 Aug 29 2019 stats.defn.tcl~
./include:
total 52
-rw-rw-r--. 1 npg npg 1079 Apr 16 2019 buffer.h
-rw-rw-r--. 1 npg npg 4473 Apr 16 2019 common.h
-rw-rw-r--. 1 npg npg 1199 Jul 16 2019 merge.h
-rw-rw-r--. 1 npg npg 1273 Apr 16 2019 message.h
-rw-rw-r--. 1 npg npg 1273 Oct 17 2019 message.h~
-rw-rw-r--. 1 npg npg 5288 Aug 29 2019 netvar.h
-rw-rw-r--. 1 npg npg 5256 Apr 16 2019 netvar.h~
-rw-rw-r--. 1 npg npg 912 Apr 16 2019 services.h
-rw-rw-r--. 1 npg npg 886 Apr 18 2019 stats.h
-rw-rw-r--. 1 npg npg 2710 Apr 16 2019 transfer.h
./MergeServer:
total 60
-rw-rw-r--. 1 npg npg 2606 Apr 16 2019 alloc_data_area.c
drwxr-xr-x. 2 npg npg 69 Aug 27 2019 bin64
drwxrwxr-x. 2 npg npg 128 Apr 6 2021 bin64.BackUp
-rw-rw-r--. 1 npg npg 10510 Sep 19 2019 buffer.c
-rwxrwxr-x. 1 npg npg 305 Apr 16 2019 build
drwxrwxr-x. 3 npg npg 279 May 14 2022 link
-rw-rw-r--. 1 npg npg 494 Apr 16 2019 Makefile
drwxrwxr-x. 3 npg npg 160 Apr 6 2021 master
drwxrwxr-x. 3 npg npg 143 Apr 6 2021 merge
-rw-rw-r--. 1 npg npg 3225 Sep 19 2019 message.c
-rw-rw-r--. 1 npg npg 3199 Sep 19 2019 netvar.c
-rwxrwxr-x. 1 npg npg 397 Aug 26 2019 run
-rw-rw-r--. 1 npg npg 15309 Sep 19 2019 signal.c
drwxrwxr-x. 3 npg npg 101 Sep 19 2019 statrate
-rw-rw-r--. 1 npg npg 1548 Sep 19 2019 stats.c
-rw-rw-r--. 1 npg npg 593 Apr 16 2019 version.c
./MergeServer/bin64:
total 148
-rwxr-xr-x. 1 npg npg 51964 May 11 2021 link64
-rwxr-xr-x. 1 npg npg 33312 May 11 2021 master64
-rwxr-xr-x. 1 npg npg 36027 May 11 2021 merge64
-rwxr-xr-x. 1 npg npg 21370 May 11 2021 statrate64
./MergeServer/bin64.BackUp:
total 256
-rwxr-xr-x. 1 npg npg 51948 Mar 16 2021 link64
-rwxrwxr-x. 1 npg npg 33184 Apr 6 2021 master64
-rwxr-xr-x. 1 npg npg 33312 Mar 16 2021 master64.new
-rwxr-xr-x. 1 npg npg 36027 Mar 16 2021 merge64
-rwxr-xr-x. 1 npg npg 35368 Mar 9 2021 merge64.new
-rwxrwxr-x. 1 npg npg 35910 Mar 8 2021 merge64.orig
-rwxr-xr-x. 1 npg npg 21370 Mar 16 2021 statrate64
./MergeServer/link:
total 164
-rw-rw-r--. 1 npg npg 10216 Oct 18 2019 handle_buffer.c
-rw-rw-r--. 1 npg npg 24623 Sep 19 2019 link_server.c
-rw-rw-r--. 1 npg npg 24732 Oct 18 2019 link_server.c~
drwxrwxr-x. 2 npg npg 217 Oct 24 2019 Linux64
-rw-rw-r--. 1 npg npg 7051 Sep 19 2019 main.c
-rw-rw-r--. 1 npg npg 7029 Oct 18 2019 main.c~
-rw-rw-r--. 1 npg npg 14464 Sep 19 2019 processAIDADATAbuffer.c
-rw-rw-r--. 1 npg npg 14463 Oct 18 2019 processAIDADATAbuffer.c~
-rw-rw-r--. 1 npg npg 14950 Sep 19 2019 processR3BDATAbuffer.c
-rw-rw-r--. 1 npg npg 14925 Oct 18 2019 processR3BDATAbuffer.c~
-rw-rw-r--. 1 npg npg 15077 Aug 22 2019 processR3BDATAbuffer.c_PreAug22
./MergeServer/link/Linux64:
total 176
-rw-rw-r--. 1 npg npg 3088 Oct 24 2019 alloc_data_area.o
-rw-rw-r--. 1 npg npg 6216 Oct 24 2019 buffer.o
-rw-rw-r--. 1 npg npg 29840 Oct 24 2019 handle_buffer.o
-rwxrwxr-x. 1 npg npg 50660 Oct 24 2019 link64
-rw-rw-r--. 1 npg npg 24464 Oct 24 2019 link_server.o
-rw-rw-r--. 1 npg npg 14864 Oct 24 2019 main.o
-rw-rw-r--. 1 npg npg 795 Aug 22 2019 Makefile
-rw-rw-r--. 1 npg npg 776 Apr 16 2019 Makefile~
-rw-rw-r--. 1 npg npg 5264 Oct 24 2019 message.o
-rw-rw-r--. 1 npg npg 12848 Oct 24 2019 signal.o
-rw-rw-r--. 1 npg npg 3480 Oct 24 2019 stats.o
-rw-rw-r--. 1 npg npg 1864 Oct 24 2019 version.o
./MergeServer/master:
total 40
-rw-rw-r--. 1 npg npg 7850 Sep 18 2019 handle_signals.c
drwxrwxr-x. 2 npg npg 223 Oct 24 2019 Linux64
-rw-rw-r--. 1 npg npg 6952 Sep 19 2019 main.c
-rw-rw-r--. 1 npg npg 6973 Sep 19 2019 main.c~
-rw-rw-r--. 1 npg npg 1722 Aug 29 2019 start_link.c
-rw-rw-r--. 1 npg npg 1885 Aug 22 2019 start_link.c~
-rw-rw-r--. 1 npg npg 1372 Apr 16 2019 start_merge.c
-rw-rw-r--. 1 npg npg 1345 Apr 16 2019 start_statrate.c
./MergeServer/master/Linux64:
total 120
-rw-rw-r--. 1 npg npg 3408 Oct 24 2019 alloc_data_area.o
-rw-rw-r--. 1 npg npg 4168 Oct 24 2019 buffer.o
-rw-rw-r--. 1 npg npg 22840 Oct 24 2019 main.o
-rw-rw-r--. 1 npg npg 793 Jul 16 2019 Makefile
-rwxrwxr-x. 1 npg npg 33184 Oct 24 2019 master64
-rw-rw-r--. 1 npg npg 5264 Oct 24 2019 message.o
-rw-rw-r--. 1 npg npg 14616 Oct 24 2019 signal.o
-rw-rw-r--. 1 npg npg 3408 Oct 24 2019 start_link.o
-rw-rw-r--. 1 npg npg 2904 Oct 24 2019 start_merge.o
-rw-rw-r--. 1 npg npg 2808 Oct 24 2019 start_statrate.o
-rw-rw-r--. 1 npg npg 3480 Oct 24 2019 stats.o
-rw-rw-r--. 1 npg npg 1864 Oct 24 2019 version.o
./MergeServer/merge:
total 48
drwxrwxr-x. 2 npg npg 228 Oct 24 2019 Linux64
-rw-rw-r--. 1 npg npg 5130 Sep 19 2019 main.c
-rw-rw-r--. 1 npg npg 4579 Oct 24 2019 mergeAIDA.c
-rw-rw-r--. 1 npg npg 4119 Oct 17 2019 #merge.c#
-rw-rw-r--. 1 npg npg 4148 Oct 21 2019 merge.c
-rw-rw-r--. 1 npg npg 3703 Sep 19 2019 mergeR3B.c
-rw-rw-r--. 1 npg npg 8060 Sep 17 2019 merge_server.c
-rw-rw-r--. 1 npg npg 2394 Sep 17 2019 storage.c
./MergeServer/merge/Linux64:
total 120
-rw-rw-r--. 1 npg npg 3088 Oct 24 2019 alloc_data_area.o
-rw-rw-r--. 1 npg npg 3872 Oct 24 2019 buffer.o
-rw-rw-r--. 1 npg npg 10944 Oct 24 2019 main.o
-rw-rw-r--. 1 npg npg 789 Jul 16 2019 Makefile
-rw-rw-r--. 1 npg npg 776 Apr 16 2019 Makefile~
-rwxrwxr-x. 1 npg npg 35910 Oct 24 2019 merge64
-rw-rw-r--. 1 npg npg 9064 Oct 24 2019 merge.o
-rw-rw-r--. 1 npg npg 8160 Oct 24 2019 merge_server.o
-rw-rw-r--. 1 npg npg 5264 Oct 24 2019 message.o
-rw-rw-r--. 1 npg npg 12744 Oct 24 2019 signal.o
-rw-rw-r--. 1 npg npg 3480 Oct 24 2019 stats.o
-rw-rw-r--. 1 npg npg 4048 Oct 24 2019 storage.o
-rw-rw-r--. 1 npg npg 1864 Oct 24 2019 version.o
./MergeServer/statrate:
total 16
drwxrwxr-x. 2 npg npg 161 Oct 24 2019 Linux64
-rw-rw-r--. 1 npg npg 1876 Sep 19 2019 main.c
-rw-rw-r--. 1 npg npg 1717 Sep 19 2019 main.c~
-rw-rw-r--. 1 npg npg 2645 Apr 16 2019 statrate_server.c
-rw-rw-r--. 1 npg npg 2645 Apr 16 2019 statrate_server.c~
./MergeServer/statrate/Linux64:
total 80
-rw-rw-r--. 1 npg npg 8880 Oct 24 2019 main.o
-rw-rw-r--. 1 npg npg 725 Apr 16 2019 Makefile
-rw-rw-r--. 1 npg npg 728 Apr 16 2019 Makefile~
-rw-rw-r--. 1 npg npg 5376 Oct 24 2019 message.o
-rw-rw-r--. 1 npg npg 10144 Oct 24 2019 signal.o
-rwxrwxr-x. 1 npg npg 21370 Oct 24 2019 statrate64
-rw-rw-r--. 1 npg npg 4664 Oct 24 2019 statrate_server.o
-rw-rw-r--. 1 npg npg 3480 Oct 24 2019 stats.o
-rw-rw-r--. 1 npg npg 1872 Oct 24 2019 version.o
./tcl:
total 4
-rw-rw-r--. 1 npg npg 1775 Aug 26 2019 NewMergerControl.tcl |
|
|
220
|
Wed Apr 14 12:14:47 2021 |
PJCS | Corrections and changes | 14/4/21 @12:00 UK time
Corrected the failure of FADC re-calibration All modules. The problem was a missing > in the .tml file
Edited the sys.tcl file in /MIDAS/TclHttpd/Html/RunControl to comment out where the status of the waveform enable was able to stop the creation of the .W spectra. This will now function at SETUP.
Edited the sys.tcl file to remove the test for Master module at the enable of the Correlation Scalar readout. All modules will now be enabled.
Successfully re-calibrated the LMK3200 in aida09 to remove the clock fault reported in System Wide Checks.
Successfully "sync ASIC clocks" followed by calibrate all module FADCs ( except aida09 which required seperate attention. )
All the Edits first carried out and tested at Daresbury T9 system. |
|