Tuda logbooks General E1104 ISACII E1195 E1103 E1147 S1287 S1203 S1233 S1284 S1447 23Na(a,p) S1540 S1381  S1847 Catania
  S1203, Page 1 of 1  ELOG logo
New entries since:Wed Dec 31 16:00:00 1969
ID Date Author Type Category Subject
  15   Thu Jul 7 19:43:43 2011 Hicham  s1203 logbook
Attachment 1: s1203Logbook.PDF
s1203Logbook.PDF
  14   Fri Jun 10 08:24:45 2011 Derek and SarahRoutineGeneralDay Shift summary Friday

08:20 Beam back and running agains

Rate: 2200

Lost proton beam at 9:41

Proton and Li beam back 11:23

 

For some reason the Li scaler has been freezing up.  If it stays frozen for a few minutes a call to ISAC OPs generally gets it going in short order.

 

14:51 Ops are checking beam.  Stopped run 383.

 

15:43 Beam tuned through the 1mm collimator with ~40% transmission.  S4: Scaler reading 120

 

Leakage Currents

DE0      -   0.06

E3         -   0.25

DE2       -   0.09

E5         -   0.31

DE4       -   0.03

E7         -   0.44

DE6       -   0.05

E2         -   0.49

UP 0     -   0.05

UP 1     -   0.05

UP 2     -   0.03

UP 3     -   0.00

UP 4     -   0.01

UP 5     -   0.05

UP 6     -   0.09

UP 7     -   0.23

S2         -  0.93

  13   Fri Jun 10 07:13:58 2011 Greg Tomney  Shift Overview for 00 - 8:00 June 10

Beamrate (scintillator) - 0
Accepted Trigger - 0
Trigger - 3

 

Run Summaries

372 - Ran for approximately 2 hours. Aside from a peculiar dip in beam intensity at ~00:25 the run was fine.

373 - Ran for about 1 hour 18 minutes. Lithium-11 beam had been down for more than 10mins so the run was stopped.

374 - Beam ran for about 56 minutes.  A spike in the pressure was observed at 2:54. The intensity of the beam flatlined at 2:58, however prior experience leads me to believe this was likely the fault of EPICS. Beam intensity fell to zero at 3:03 for a short time. Another spike in the pressure was observed at 3:19. The problem with the beamline is allegedly relating to a coil in one of the cavities.

375 - Beam ran for 9 minutes before failing.

376 - With the cavity tripped, no lithium-11 was present. However, data was taken to observe background effects. This was done for about 25 minutes.

378 - Another background run was done for about 2 hours this time.

Leakage Currents

DE0      -   0.06

E3         -   0.25

DE2       -   0.09

E5         -   0.31

DE4       -   0.02

E7         -   0.44

DE6       -   0.05

E2         -   0.49

UP 0     -   0.05

UP 1     -   0.04

UP 2     -   0.01

UP 3     -   0.00

UP 4     -   0.01 (fluctuating as high as 0.43)

UP 5     -   0.06

UP 6     -   0.09

UP 7     -   0.23

S2         -  0.91

 

  12   Thu Jun 9 15:47:41 2011 Derek, SambuuRoutineGeneralDay shift summay Thursday

No troubles

Beamrate: 1600

Trigger Rate: 9

Accepted trigger rate: 9

  11   Wed Jun 8 09:09:31 2011 Alex RojasRoutineGeneralBeam maintenance

Beam interrupted at 8am for maintenance scheduled.

Beam back at 10am.

  10   Wed Jun 8 07:05:12 2011 David CrossRoutineGeneralShift report 00:00 - 08:00
Beamrate (scintillator) - 2240
Accepted Trigger - 7
Trigger - 7

General notes:

- Striptool would freeze for ~5-10 minutes at a time sporadically throughout the shift
- One proton beam dropout at about 3:30 AM, did not stop run as they came back quickly.

Special note:

- Ops called and said Protons are going away at 07:00 for a maintenance period. Earliest anticipated return of
beam is at 09:00
- I will initiate a background run after this elog entry, that will be run #349 and I have asked Ops to put a
Faraday Cup in so as not to put beam into a background run if it comes back early. So just ask them to take the
cup out when they say 11Li is ready to come back.
- UPDATE: Ritu has said not to worry about any background. #349 has been stopped and no data is being taken.
  9   Tue Jun 7 23:39:08 2011 Greg and Sambuu  Shift Overview for 16-22:00 June 7

Beamrate (scintillator) - 2592
Accepted Trigger - 7
Trigger - 7

 

Minutes from the Shift

18:15 - Lithium beam went down for approximately 6 minutes at about this time. After the beam was reestablished the control room quickly performed a calibration. This can be seen in the data by the re-emergence of the detected proton beam prior to the scintillator detecting any lithium-11.

20:10 - A run that had begun at 18:51 was stopped by R. Kanungo to see if the data collection for the delta-E detector could be improved. Counts for delta-E were low. (note from R. Kanungo to be attached)

21:53 - The control room called to say that a cavity had 'dropped out'. This issue was resolved and a new run began however counts were not taken from the short run which had started at 21:47.

22:22 -  The StripTool Graph on the EpicsPC recorded an abnormally stable lithium-11 beam intensity and proton beam current (zero fluctuation)  for approximately 5 minutes. However, during this time CAEN readouts from the scintillator on Tuda 3 continued to fluctuate suggesting the issue is with EpicsPC or StripTool.

Leakage Currents

DE0      -   0.06

E3         -   0.25

DE2       -   0.08

E5         -   0.31

DE4       -   0.03

E7         -   0.47

DE6       -   0.05

E2         -   0.52

UP 0     -   0.05

UP 1     -   0.04

UP 2     -   0.04

UP 3     -   0.00

UP 4     -   0.01

UP 5     -   0.06

UP 6     -   0.09

UP 7     -   0.23

S2         -  0.91

Other Issues

A quick run-through of the channels showed that channels 19 and 32 on UP 1 (adc 11) are probably broken.

  8   Tue Jun 7 16:17:17 2011 Julian  11Li spectroscopy June 7th - 8am-4pm shift

At 9:30am the beam was given to the controll room in between 2 runs.

At ~10am the beam tripped--> restarted and data was coming in, but SC8 showed nothing --> DAQ was restarted from the control room --> problem solved

Beam was off and on occasionally between 10:15 and 2, but fairly consistent thereafter.

 

  7   Tue Jun 7 07:48:52 2011 Andrew ValencikRoutineGeneralOwl Shift June 7 - DTL Tripping issues

0:02 Run 328 started

1:33 Run 328 stopped so ISAC control could run tests and take measurements

1:36 Run 329 starts. Beam drops at 2:30am. Stop runat 2:36. "DTL tank 1 tripped off" -ISAC Summary

2:40 Run 330 starts. DTC Tank 1 trips again, lost beam for about 6min

3:23-3:49 no beam

3:49 beam returns, start run 331, beam only lasts for 3 minutes

No beam…

5:14 beam returns. Start run332 continues for 2 hours

7:15 new run started. Leakage currents measured, all normal.

 

Beam issues were caused by a waterflow problem in the DTL tanks, more details available on the ISAC Operations Logbook for June 7

 

 
 

 

 

 

 

 

 

 

 

  6   Mon Jun 6 22:47:35 2011 Hicham  11Li beam, yehhhhhhhhhhhhhhhhhhh !

 

Persons on shift : Ritu, Nigel, Alex, Sambuu & Hicham

Finally, we got our first 11Li beam around of 1800 pps for 4.77 MeV/u @ 21h55.

The CD2 target is 184ug/cm2 thick

The setup is 4 dE-E LEDA downstream sectors (~6cm) + 8 LEDA upstream sectors (~5cm) + 1 S2 downstream (~65cm)

We are using a scintillator to measure the 11Li beam intensity

The turbo is off, the pressure is around 3e-6 and stable for more than 3hours

The Chiller temp. is set to 3 Celsius, the preamp temp is stable around 10C

We saw the elastic scattering in the S2 detectors, and some hit in the upstream detector.

  5   Sun Jun 5 23:44:54 2011 Andrew ValencikOtherGeneralADC Assignment Summary

ΔE LEDA Detector

ΔE0 ADC1 0 - 15
ΔE1 ADC1 16 - 31
ΔE2 ADC2 0 - 15
ΔE3 ADC2 16 - 31
ΔE4 ADC3 0 - 15
ΔE5 ADC3 16 - 31
ΔE6 ADC4 0 - 15
ΔE7 ADC4 16 - 31
 
E LEDA Detector
E2 ADC5 0 - 15
E3 ADC6 16 - 31
E5 ADC7 16 - 31
E7 ADC8 16 - 31
 
S2 Detector
S2 rings ADC9 0 - 31
S2 rings ADC10 0 - 15
S2 sector ADC10 16 - 31
 
Upstream LEDA Detector
UP0 ADC11 0 - 15
UP1 ADC11 16 - 31
UP2 ADC12 0 - 15
UP3 ADC12 16 - 31
UP4 ADC13 0 - 15
UP5 ADC2 16 - 31
UP6 ADC14 0 - 15
UP7 ADC14 16 - 31

 

Attachment 1: ADC_Assignment_2011.pdf
ADC_Assignment_2011.pdf
  4   Sun Jun 5 17:57:52 2011 Andrew ValencikRoutineGeneralREADME for MIDAS DAQ

 

README.MIDAS


 

Shutting Down MIDAS DAQ
-----------------------

The following procedure describes a 'cold' stop of the DAQ.
Normally one would only need to perform steps 1 to 2.

1) If possible, stop data acquisition

   MIDAS Data Acquisition Experiment Control -> select STOP
   
2) If possible, quit data acquisition

   MIDAS Main Menu -> select Quit
   
   From the Quit Session Confirmation pop-up window
   
   select -> Yes
   
3) If possible, stop TapeServer. The TapeServer is normally run from
   a terminal session on tuda2.

   In the command window where the TapeServer was started enter CTRL-C
   
   The TapeServer should respond confirming that its processes have
   received an INT signal.

MIDAS Tape Driver (5615): Received INT signal; exiting.
MIDAS Tape Driver (5614): Received INT signal; exiting.
MIDAS Tape Driver (5613): Received INT signal; exiting.
 
Starting MIDAS DAQ
------------------

The following procedure describes a 'cold' start of the DAQ.
Normally one would only need to perform steps 5 to 9.

1) Login to Sun Blade 100 workstation - tuda2 ISAC-II Experimental Hall

   user: tuda
   password:

2) Switch off the VME crate.
   Wait 20s.
   Switch on the VME crate.
   
   After a short delay (c. 20-30s) you will observe significant network
   load on the Allied Telesys 8-port switch on top of the TUDA 19" racks
   whilst the Lynx operating system is downloaded to the MVME 2431 CPU 
   and the DAQ application is loaded. 
   
3) Open (another) command window on tuda2. Enter the commands

   cd /MIDAS/TapeServer/SunOS
   ./master
   
   This will start the TapeServer process which should conclude with
   messages of the type
   
   MIDAS Data Link (5821): MIDAS Data Link thread 0 using TCP port 10305.
   MIDAS Data Link (5821): Entering server loop
   MIDAS Data Link (5821): thread 0 listening on port 10305

4) Check whether the EPICS access repeater process is running

    tuda2> ps -ef | grep caRepeater
    tuda  2182     1   0 12:35:07 pts/2       0:00 caRepeater

   If the EPICS access repeater is not running, you can start it
   by requesting any EPICS variable, e.g.

   tuda2> caget CCS2ISAC:BL2ACURRENT
   CCS2ISAC:BL2ACURRENT          0

5) Open (another) command window. Enter the command

   MIDAS-session

   From the pop-up window select -> MIDAS Data Acquisition

   If you wish to run a MIDAS session remotely (tuda3 ISAC-II Counting
   Room 1) establish a Secure Shell (ssh) connection from tuda3 to tuda2

   tuda3> ssh tuda2 -l tuda

   and enter the command MIDAS-session in this terminal session.

   It is *strongly* recommended that you do NOT run the MIDAS DAQ
   locally *and* remotely.

6) From the MIDAS Main Menu select Experiment Control ... and wait
   until start sequence is complete

7) From MIDAS Data Acquisition Experiment Control select SETUP.
   From Confirmation Request for Data Acquisition Setup pop-up window
   select Setup Everything
   
   ... and wait until the sequence is complete with the message
   
   MIDAS DA is SETUP and ready to GO at 

8) From the MIDAS Main Menu select Experiment Control select -> Advanced.
   Select Configuration/Test/Debug Frame. From confirmation pop-up select
   -> Yes - Please Continue
   
   Check the TDC mode is Common Stop, TDC reference is 0, and readout mode is 1.

   Check Data Destination:Tape Server is tuda2daq and select 'Setup Connection'

   Select Update.

   Dismiss the Configuration/Test/Debug Frame.

9) From MIDAS Data Acquisition Experiment Control select Tape Control.

   From the Tape Drive Control window select Allocated? button adjacent
   to /dev/file/0 - No should toggle to Yes.

   Select corresponding Load Tape -> Mount (Append Data to old tape)
   Volume name (S1195) should appear, select Continue.

   If you do not wish to write data to disk (/dev/file/0) select No Storage.

   Dismiss the Tape Drive Control Window.

   From MIDAS Data Acquisition Experiment Control select Redisplay. Tapes
   in use should change to:

   /dev/file/0 (if you are writing to disk)
   Storage is not enabled (if you have selected No Storage)

   Check Histogramming Enabled and TS Transfer Enabled are selected.
   The TS Transfer Enabled button should be green indicating a good
   connection to the Tape Server.

9) From the MIDAS Main Menu select Experiment Control select Go

   If you have selected No Storage you will be reminded of this and asked
   whether you wish to continue, or abort data acquisition start.

Starting data run   
-----------------   
   
Assumes DAQ is already stopped.   
   
1) Clear VME CPU histograms (if required)   
   
   From Spectrum Directory Browser frame select -> Resource -> hist   
   Select -> Select All   
   Select -> Actions -> Zero & Deselect   
   
   The footer of window should show zeroing of spectra in progress.   
   
2) Clear online sort spectra (if required)   
   
   From Spectrum Directory Browser frame select -> Resource -> SortSas   
   Select -> Select All   
   Select -> Actions -> Zero & Deselect   
   
   The footer of window should show zeroing of spectra in progress.   
   
3) Start DAQ   
   
   From MIDAS Data Acquisition Experiment Control select -> GO   
   
   If the DAQ has started OK you should see the 'Good Events' scaler   
   increment and 'Good Events /s' should be non-zero.   
   
4) Complete Elog entry  
  
   The Session Log window will show the start time & date  
   
5) Check run data file

   Open a command window and enter command(s)

   ls -l /net/tuda2/data2/data/S1195; sleep 60; ls -l /net/tuda2/data2/data/S1195

   and check current run data file is increasing in size.
    
Stopping data run  
-----------------  
  
Assumes DAQ is going.  
  
1) Stop DAQ  
     
   From MIDAS Data Acquisition Experiment Control window select -> STOP  
  
2) Save VME CPU histograms  
  
   From Spectrum Directory Browser select -> Actions -> Save  
   The Spectrum Copy & Online Histogram Save window should appear.  
   Select -> Source Resource -> hist  
   Select -> Select All  
   Check destination Directory (e.g. /home/tuda/S1195/spectra)  
   Enter (sub-)Directory (e.g. run100)  
   Select -> Execute  
  
3) Save online sort spectra  
  
   From Spectrum Directory Browser select -> Actions -> Save  
   The Spectrum Copy & Online Histogram Save window should appear.  
   Select -> Source Resource -> SortSas  
   Select -> Select All  
   Check destination Directory (e.g. /home/tuda/S1195/spectra)  
   Enter (sub-)Directory (e.g. run100)  
   Select -> Execute  
  
4) Complete Elog entry  
  
   The Session Log window will show the stop time & date and # blocks written to disk 

T.Davinson - May 2009
Revised - April 2011
    

 

Attachment 1: README.MIDAS
Shutting Down MIDAS DAQ
-----------------------

The following procedure describes a 'cold' stop of the DAQ.
Normally one would only need to perform steps 1 to 2.

1) If possible, stop data acquisition

   MIDAS Data Acquisition Experiment Control -> select STOP
   
2) If possible, quit data acquisition

   MIDAS Main Menu -> select Quit
   
   From the Quit Session Confirmation pop-up window
   
   select -> Yes
   
3) If possible, stop TapeServer. The TapeServer is normally run from
   a terminal session on tuda2.

   In the command window where the TapeServer was started enter CTRL-C
   
   The TapeServer should respond confirming that its processes have
   received an INT signal.

MIDAS Tape Driver (5615): Received INT signal; exiting.
MIDAS Tape Driver (5614): Received INT signal; exiting.
MIDAS Tape Driver (5613): Received INT signal; exiting.
 
Starting MIDAS DAQ
------------------

The following procedure describes a 'cold' start of the DAQ.
Normally one would only need to perform steps 5 to 9.

1) Login to Sun Blade 100 workstation - tuda2 ISAC-II Experimental Hall

   user: tuda
   password:

2) Switch off the VME crate.
   Wait 20s.
   Switch on the VME crate.
   
   After a short delay (c. 20-30s) you will observe significant network
   load on the Allied Telesys 8-port switch on top of the TUDA 19" racks
   whilst the Lynx operating system is downloaded to the MVME 2431 CPU 
   and the DAQ application is loaded. 
   
3) Open (another) command window on tuda2. Enter the commands

   cd /MIDAS/TapeServer/SunOS
   ./master
   
   This will start the TapeServer process which should conclude with
   messages of the type
   
   MIDAS Data Link (5821): MIDAS Data Link thread 0 using TCP port 10305.
   MIDAS Data Link (5821): Entering server loop
   MIDAS Data Link (5821): thread 0 listening on port 10305

4) Check whether the EPICS access repeater process is running

    tuda2> ps -ef | grep caRepeater
    tuda  2182     1   0 12:35:07 pts/2       0:00 caRepeater

   If the EPICS access repeater is not running, you can start it
   by requesting any EPICS variable, e.g.

   tuda2> caget CCS2ISAC:BL2ACURRENT
   CCS2ISAC:BL2ACURRENT          0

5) Open (another) command window. Enter the command

   MIDAS-session

   From the pop-up window select -> MIDAS Data Acquisition

   If you wish to run a MIDAS session remotely (tuda3 ISAC-II Counting
   Room 1) establish a Secure Shell (ssh) connection from tuda3 to tuda2

   tuda3> ssh tuda2 -l tuda

   and enter the command MIDAS-session in this terminal session.

   It is *strongly* recommended that you do NOT run the MIDAS DAQ
   locally *and* remotely.

6) From the MIDAS Main Menu select Experiment Control ... and wait
   until start sequence is complete

7) From MIDAS Data Acquisition Experiment Control select SETUP.
   From Confirmation Request for Data Acquisition Setup pop-up window
   select Setup Everything
   
   ... and wait until the sequence is complete with the message
   
   MIDAS DA is SETUP and ready to GO at <date/time>

8) From the MIDAS Main Menu select Experiment Control select -> Advanced.
   Select Configuration/Test/Debug Frame. From confirmation pop-up select
   -> Yes - Please Continue
   
   Check the TDC mode is Common Stop, TDC reference is 0, and readout mode is 1.

   Check Data Destination:Tape Server is tuda2daq and select 'Setup Connection'

   Select Update.

   Dismiss the Configuration/Test/Debug Frame.

9) From MIDAS Data Acquisition Experiment Control select Tape Control.

   From the Tape Drive Control window select Allocated? button adjacent
   to /dev/file/0 - No should toggle to Yes.

   Select corresponding Load Tape -> Mount (Append Data to old tape)
   Volume name (S1195) should appear, select Continue.

   If you do not wish to write data to disk (/dev/file/0) select No Storage.

   Dismiss the Tape Drive Control Window.

   From MIDAS Data Acquisition Experiment Control select Redisplay. Tapes
   in use should change to:

   /dev/file/0 (if you are writing to disk)
   Storage is not enabled (if you have selected No Storage)

   Check Histogramming Enabled and TS Transfer Enabled are selected.
   The TS Transfer Enabled button should be green indicating a good
   connection to the Tape Server.

9) From the MIDAS Main Menu select Experiment Control select Go

   If you have selected No Storage you will be reminded of this and asked
   whether you wish to continue, or abort data acquisition start.

Starting data run   
-----------------   
   
Assumes DAQ is already stopped.   
   
1) Clear VME CPU histograms (if required)   
   
   From Spectrum Directory Browser frame select -> Resource -> hist   
   Select -> Select All   
   Select -> Actions -> Zero & Deselect   
   
   The footer of window should show zeroing of spectra in progress.   
   
2) Clear online sort spectra (if required)   
   
   From Spectrum Directory Browser frame select -> Resource -> SortSas   
   Select -> Select All   
   Select -> Actions -> Zero & Deselect   
   
   The footer of window should show zeroing of spectra in progress.   
   
3) Start DAQ   
   
   From MIDAS Data Acquisition Experiment Control select -> GO   
   
   If the DAQ has started OK you should see the 'Good Events' scaler   
   increment and 'Good Events /s' should be non-zero.   
   
4) Complete Elog entry  
  
   The Session Log window will show the start time & date  
   
5) Check run data file

   Open a command window and enter command(s)

   ls -l /net/tuda2/data2/data/S1195; sleep 60; ls -l /net/tuda2/data2/data/S1195

   and check current run data file is increasing in size.
    
Stopping data run  
-----------------  
  
Assumes DAQ is going.  
  
1) Stop DAQ  
     
   From MIDAS Data Acquisition Experiment Control window select -> STOP  
  
2) Save VME CPU histograms  
  
   From Spectrum Directory Browser select -> Actions -> Save  
   The Spectrum Copy & Online Histogram Save window should appear.  
   Select -> Source Resource -> hist  
   Select -> Select All  
   Check destination Directory (e.g. /home/tuda/S1195/spectra)  
   Enter (sub-)Directory (e.g. run100)  
   Select -> Execute  
  
3) Save online sort spectra  
  
   From Spectrum Directory Browser select -> Actions -> Save  
   The Spectrum Copy & Online Histogram Save window should appear.  
   Select -> Source Resource -> SortSas  
   Select -> Select All  
   Check destination Directory (e.g. /home/tuda/S1195/spectra)  
   Enter (sub-)Directory (e.g. run100)  
   Select -> Execute  
  
4) Complete Elog entry  
  
   The Session Log window will show the stop time & date and # blocks written to disk 

T.Davinson - May 2009
Revised - April 2011
    
  3   Sun Jun 5 17:02:53 2011 RituOtherGeneralS1203 startup

 Saturday (June 4)

22Ne (8+) was tuned through TUDA @ ~ 110 enA checking on the

Faraday Cup. 

The transmission through a 3mm collimator was ~ 90%.

A low intensity tune ~ 200cps was tested using the scintillator.

After this the chamber was vented, to remove collimator and

alpha source was placed for calibrating upstream YY1 and dE(YY1).

There was a large noise in the free trigger (~ 2000cps) originating from  upstream 

YY1 detectors channels. 

Sunday (June 5)

Eventually  the threshold was raised and noise was reduced.

Calibration run taken for dE and upstream.

Vented chamber

fixed upstream cradle position

Inserted targets 

Pumped down.

 

  2   Sat May 28 21:16:45 2011 Hicham  Mounting S2+LEDA preamps

- Chamber stripped out after S1287

- Mounting premaps for S2 + 3xLEDA

  1   Sat May 28 19:18:11 2011 HichamRoutineGeneralproposal, safety report, and other documents

see attached

Attachment 1: S1203_200812S_merged.pdf
S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf S1203_200812S_merged.pdf
Attachment 2: S1203_201105_Safety.pdf
S1203_201105_Safety.pdf S1203_201105_Safety.pdf S1203_201105_Safety.pdf S1203_201105_Safety.pdf S1203_201105_Safety.pdf
Attachment 3: s1203_safety_report.odt
ELOG V2.9.2-2455