I added 250mL of water to the TCSy chiller this morning, bringing the reading on the scale from 4.5 to 9.0.
In addition, the TCSy CO2 laser tripped out this morning on a flow alarm. Peter and I reset the laser box (key off, then key on) to clear the alarm and restart the laser. Cheryl had trended the flow channel for the CO2 laser and indeed the flow dropped to zero and recovered (I don't have the trend, perhaps Cheryl will post it later). Maybe an air bubble working its way through the system?
(Late entry for yesterday's Maintenance Day activity) Kyle, Gerardo Scheduled preventative maintenance -> Measured discharge pressure to be =/> 115 psi - OK, greased motor shaft bearings with Chevron SRI and scroll compressor orbital shaft and crank pin bearings with Anest Iwata SL-140. Belts visual and adjustment - OK.
| Work Permit | Date | Description | alog/status |
| 6244.html | 2016-10-11 11:46 | Look at POP-X whitening chassis figure our why gains can only be odd values. Also look at second stage filter not engaging properly. Possibly replace chassis | The modbus internal readback is broken,but the device is functional, i.e., its input and outputs work as expected. Mark as "wont fix". |
| 6243.html | 2016-10-11 10:11 | At the request of DetChar, update the thresholds of the PSL ODC to account for the now operational HPO. A review of the current PSL ODC thresholds shows the only bit in need of updating is PSL ODC Bit 12: PMC Transmission Limit OK. The threshold will be changed from 11.5 to 50, to account for the increased power transmitted by the PMC. | 30405 |
| 6242.html | 2016-10-11 08:13 | migrate virtual machines from vmweare to proxmox | 30429 |
| 6241.html | 2016-10-11 08:04 | Briefly run scroll air compressor(s) on Vent/Purge-air supply skid*Lock-out/Tag-out power to Vent/Purge-air skid*Perform scheduled maintenance on scroll compressors #1 and #2 | preventative maintenance, will be a famis task and this is the initial entry |
| 6240.html | 2016-10-10 17:05 | Pico ctrl report error when off: revert logic - LO readback for spares flicker: use nom. of -100 to disable test - EOM driver RF monitor: increase tolerance to 1.5dB | 30406, 30429 |
| 6239.html | 2016-10-10 16:51 | Fix whitening ctrl in QPD | 30412, 30429 |
| 6238.html | 2016-10-10 16:13 | CALCS model update. A filter block will be added to the DARM_CTRL signal path (implemented at LLO alog 28268), changes to BUFFER_AND_AVERAGE.c code will be applied (LHO alog 30293). | 30411, 30429 |
| 6237.html | 2016-10-10 15:43 | Remove the Solaris QFS/NFS server h1ldasgw2. This was installed in the summer to NFS export frames to the NDS servers. It has served corrupted frames, so we will return to the previous configuration. | Did not remove h1ldasgw2, WP#6237, do to time constraints; will defer this to later in the week |
| 6236.html | 2016-10-10 12:46 | sister WP to 6234. Change h1susitmx and h1susetmx model code to read HWWD chassis status. DAQ restart required. Modify MEDM and alarms. | 30429 |
| 6235.html | 2016-10-10 11:50 | add an experimental feed forward path for jitter correction | 30412, 30429 |
| 6234.html | 2016-10-10 11:10 | Per FRS 4504, finish installation of the Hardware Watchdog (HWWD) electronics for ETMX and ITMX. Currently, ETMY and ITMY electronics are installed, with ITMY in a monitor-only mode. Plan is to install ETMX and ITMX in monitor-mode. List of items that need to be done: 1. Install D1300642 2. Pull in new BNC cabling to ISI Coil Drivers 3. Pull binary cabling DB9 4. Power electronics For complete installation, the ISI Coil Drivers (ETMX, ITMX, and ITMY) will need to be replaced with modified units that enable the HWWD electronics to power off the coil drivers. New work permit will be started for switching out the coil drivers. | 30418 |
| 6233.html | 2016-10-10 10:43 | Reconfigure lhoepics.ligo-wa... to host an EPICS to web bridge. This may interrupt the remote access medm. Also revisit the process for exporting the medm screens from CDS to ensure they still work after the recent shibboleth IdP changes. | 30372 |
| 6232.html | 2016-10-10 10:38 |
Install a newer daqd framewriter on h1fw0 and h1fw1. This will use the framewrite tested on h1fw2 which writes out checksum files with each frame file written. This will likely also involve a change to the wiper script to properly handle the checksum files |
30429 |
| 6231.html | 2016-10-10 10:24 | GDS and DMT Update GDS to gds-2.17.10, the DMT calibration code to gstlal-calibration-1.0.4-1 and install new calibration filters. Patch summary for GDS: a) t-domain lowpass filter and overlapped PSD measurements for SenseMon. b) a fix to prevent writing frames with wrong times. c) Cookie file for dmt-viewer d) prevent framelink from terminating immediately if the connection to the peer node fail. Patch summary for calibration: - Bug fix for coherence gating in kappa calculation - Explicit check on frame start time being integer multiple of frame duration - Increased debugging messages available for when discontinuities are encountered ALSO: install new calibration filters as available | 30409, 30403, & 30429 |
| 6230.html | 2016-10-10 08:58 | Replace bulkhead N connector for the 45MHz RF signal. Check associated field cables/connectors. | 30394, 30375 |
| 6229.html | 2016-10-10 08:50 | Update the TCS front end model to the latest. DAQ restart required. | 30384, 30429 |
| 6228.html | 2016-10-10 08:23 | PCal End X Transmitter module maintenance measurements and end station calibration. This will require that EX VEA is laser hazard. No viewports will be exposed during this work. | |
| 6227.html | 2016-10-10 08:23 | Complete ECR E1500325: Update HEPI Model to bleed off saturations from watchdogs--currently a weekly chore manually done by operators vis FAMIS. ISI already have this feature and has been working trouble free for months. | 30408, 30373, & 30429 |
| 6226.html | 2016-10-10 08:17 | Perform annual septic tank pump out. This includes all septic tanks on site. A report will be generated for LIGO and the DOH. | Contractor canceled. They will reschedule |
| 6225.html | 2016-10-09 10:17 | Remove viewport covers on HAM2 | 30364 |
| 6224.html | 2016-10-07 08:52 |
Install a new DAQD build on the framewriter that provides checksum information of each frame file that is writen, and reflecting some of this information into EPICS PVs. This will be done on h1fw2 as a test prior to deployment on the production frame writers. This will require remote access to CDS today for Jonathan. |
30292 |
| 6223.html | 2016-10-07 08:21 | Update GDS software to branch gds-2.17.9. This implements updated security code in dmtviewer to handle ecp cookie files now required for authentication. The user setup scripts will be modified to add an environment variable to specify the location of the ecp cookie file that would be generated by a user. | This version 2.17.9 is for control room software, version 2.17.10 is for dmt-gds. |
| 6222.html | 2016-10-06 16:10 | (late WP) Move CPs and ITMs to confirm the sled reflection from the ITMY CP. Swap sleds (790nm and 840nm) on the HWS table. Repeat the process to see whether the reflection off the CP is wavelength depended. | done |
| 6221.html | 2016-10-06 13:52 | Coordinate test running of pumps connected to RGA at BSC5 with Robert S. so as to measure potential intrusiveness into commissioning activities. | pending, pump isolated but not running |
| 6220.html | 2016-10-06 10:16 | Add jitter measuring signals of DBB to frame. | 30287 |
| 6219.html | 2016-10-05 14:34 | Place a new photodiode in the EOM pickoff path and use this as PD_A sensor to close the ISS 1st loop. PD_B will remain untouched and therefore remain functional. | done |
| 6218.html | 2016-10-05 13:26 | Replace the 16 Batteries in the Aux cabinet of the UPS. This work will be done when we are out of lock but not necessarily when we are in maintenance. The design allows for this work to be done while the output is energized. | Replaced 15 batteries, the 16th was damaged and we are waiting for its replacement |
| 6217.html | 2016-10-05 09:06 | Complete ECR E1600042 FRS 4703: Remove final traces of DACKILL from HAM ISI model: Make changes, recompile, etc restart. Cleanup HAM & BSC medms of dead widgets. Remove RESET ALL from medms. | 30408, 30373, & 30429 |
| 6216.html | 2016-10-05 08:14 | As part of debugging the cooling problem with the laser, at the next window of opportunity I want to do a test where we replace the front end and power meter circuit flow sensors with a current source that mimics the output from the flow sensor. This check the flow rate readout electronics. | done, electronics chain appeared to be ok |
12:35 NLN
14:55 Gabriele in to do some commissioning
WP 6223 On Tuesday, a new version of GDS software, branches/gds-2.17.9, was installed for the control room. This version has one minor bug fix to diaggui (Bugzilla 1040) for the reference trace dialog box, and code to allow dmtviewer to use cookies generated by ecp-cookie-init for authorization. The script ecp-cookie-init was also installed. The dmtviewer change allows us to display both LHO and LLO range again. The standard environment setup script was modified to set a new environment variable telling dmtviewer where to find the cookie file for a particular user. To use dmtviewer to view LLO data, do the following three commands: kinit albert.einstein (enter password) ecp-cookie-init -k https://llodmt.ligo-la.caltech.edu/dmtview/LLO dmtviewer It is highly recommended that you do this when logged in as yourself, not as user controls. If you need to clear the authorization, perform the following two commands: kdestroy ecp-cookie-init -X
11:26UTC I'm still increasing power manually. PI mode 26 seems pretty buried at this point.
11:27 OMC DCPD Saturation - lockloss; SUS OMC and HAM6 ISI WD tripped.
A few other things tonight:
A little bit of ASC work:
Cleared ST1 and ST2 BS accumulators.
Thanks Ed. Couple things. Not sure where St1 and St2 come in to play for HEPI, that sounds like ISI. Plus, with the upgrade done to HEPI yesterday, no seismic system should need the Watchdog saturations clearing anymore. I'll remove the FAMIS task associated here for HEPI.
Possibly after some changes made durring maintence, the lockloss tool stopped working. I can use lockloss plot, but not select.
sheila.dwyer@opsws4:~/Desktop/Locklosses$ lockloss -c channels_to_look_at_TR_CARM.txt select
After noticing LLO alog 28710 I tried to svn up the lockloss script (we're at rev 14462 now), but I still get the same error when I try to use select
The problem at LLO is totally different and unrelated.
The exception you're seeing is from an NDS access failure. The daq NDS1 server is saying that it can't find the data that is being requested. This can happen if you request data too recent in the past. It also used to happen because of gaps in the NDS1 lookback buffer, but those should have been mostly fixed.
Right now the lockloss tool is looking for all lock loss events from 36 hours ago to 1 second ago. The 1 second ago part could be the problem, if that's too soon for the NDS1 server to handle. But my testing has indicated that 1 second in the past should be sufficient for the data to be available. In other words I've not been able to recreate the problem.
In any event, I changed the look-back to go up to only two seconds in the past. Hopefully that fixes the issue.
Trouble locking DRMI improved after turning TCSY back on. Handing over to Ed and Sheila. 23:15 UTC Cheryl started initial alignment. Taking over. 23:35 UTC Initial alignment done. 00:13 UTC Changed phase to damp PI mode 26 00:15 UTC NLN, RF looks good 00:17 UTC Sheila running A2L, Kiwamu to LVEA to turn on TCSY laser 00:23 UTC Kiwamu back 00:45 UTC Lock loss. TCSY laser turned off. Kiwamu to LVEA to turn it back on. 01:01 UTC Kiwamu back 01:26 UTC NLN 01:46 UTC Jeff K. starting calibration measurements 02:24 UTC Jeff K. done measurements 03:40 UTC Sheila to LVEA to check ISC racks 03:43 UTC Sheila back 03:45 UTC Sheila starting frequency noise coupling measurement 06:08 UTC Lock loss (Sheila) 07:17 UTC Sheila and Ed to mezzanine to check TCS chiller. TCSY laser has been off since around the beginning of the last lock. 07:28 UTC Sheila and Ed back. TCSY laser back on.
Ed, Sheila and Patrick
The "Gate" indicator LED was off on the TCSY LASER controller. This condition was reset by Sheila by pushing the red button on the front panel of the controller. I added 250ml of water to the Y-chiller to bring the level back to the top mark. This was most likely the reason that PRMI wouldn't stay locked.
J. Kissel, D. Tuyenbayev,
We turned on two calibration lines using ETMY coil drivers on stages L1 and L2. The SNRs of these lines are roughtly 1/3 of the regular calibration lines (regular cal. lines have SNR of ~100 with 10s FFT).
_FREQ (Hz) _CLKGAIN (ct)H1:SUS-ETMY_L1_CAL_LINE 33.7 60.0 O2-scheme synched oscillator for kappa_U
H1:SUS-ETMY_L2_CAL_LINE 34.7 27.0 O2-scheme synched oscillator for kappa_P
These lines will be used to better quantify calibration of the PUM and UIM actuators.
A related report: LHO alog 29291.
κU, κP and κT using these additional lines at ~6am on Wed., Oct. 12 are:
κU = 0.9828 - 0.0637i
κP = 0.9499 - 0.0380i
κT = 0.9784 - 0.0440i
These are preliminary values calculated manually for transfer functions taken at a selected time (no trends or averaging except for 10avg. in DTT), and the DARM model for ER9 (H1params_2016-07-01.conf). We will use SLM tool data to look at the parameter trends.
Greg M, Darkhan T,
We calculated kappa values using SLM data (10s FFTs) generated over 10 days between Oct 10 and Oct 21 with ER9 parameter file
'${CalSVN}/Runs/PreER9/H1/params/H1params_2016-07-01.conf'
The plots show raw (unaveraged) values. SNRs of the L1 and L2 lines (used for calculation of κU and κP respectively) were set to give approximately 1/3 SNR compared to the L3 line (with the ER9 noise floor).
The data was taken from an additional SLM tool instance which was setup by Greg to calculate 33.7 Hz, 34.7 Hz, 35.9 Hz and 36.7 Hz line FFTs.
J. Kissel for S. Karki I've changed the > 1 kHz PCALX calibration line frequency, a.k.a. the "long duration sweep" line, to 2501.3 Hz. Recall this started moving again on Oct 6th (see LHO aLOG 30269) I report the progress towards completing the sweep below. Frequency Planned Amplitude Planned Duration Actual Amplitude Start Time Stop Time Achieved Duration (Hz) (ct) (hh:mm) (ct) (UTC) (UTC) (hh:mm) --------------------------------------------------------------------------------------------------------------------------------------------------------- 1001.3 35k 02:00 1501.3 35k 02:00 2001.3 35k 02:00 2501.3 35k 05:00 39322.0 Oct 12 2016 03:20:41 UTC 3001.3 35k 05:00 39322.0 Oct 06 2016 18:39:26 UTC Oct 12 2016 03:20:41 UTC days 3501.3 35k 05:00 39322.0 Jul 06 2016 18:56:13 UTC Oct 06 2016 18:39:26 UTC months 4001.3 40k 10:00 4301.3 40k 10:00 4501.3 40k 10:00 4801.3 40k 10:00 5001.3 40k 10:00
J. Kissel, D. Tuyenbayev We've grabbed another set of calibration measurements of the IFO's sensing function in order to build confidence in our newly commissioned front-end tracking of time dependent model parameters, and to confirm the discrepancy seen yesterday (LHO aLOG 30391) was not something funny about that lock stretch. Indeed the discrepancy remains. We've found bugs in our code that compares our DARM model against these measurements, so we can't yet confirm exact numbers like optical gain, DARM coupled cavity pole frequency, or SRC detuning spring frequency to offer a proposed change to the CAL-CS front-end parameters to fix it. We'll hopefully have something by tomorrow. Attached are screenshots of the measurements and the DARM loop parameters during the measurement. Timeline: (in UTC) 2016-10-12 01:30:00 -- IFO in stable Nominal Low Noise (PCALY calibration lines are ON); IFO undisturbed 01:46:00 -- IFO sufficiently thermalized to start measurements; PCALY lines turned OFF 01:47:48 -- PCAL2DARM measurement begins 02:05:48 -- DARM OLGTF measurement begins 02:24:00 -- measurements done; PCALY lines turned back ON; IFO undisturbed 02:40:00 -- Official Undisturbed period ends (but no one has done anything with the IFO since, up to 03:06 UTC) Data files (which are exported and committed to the SVN): /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/ DARMOLGTFs/2016-10-12_H1_DARM_OLGTF_4to1200Hz.xml PCAL/2016-10-12_H1_PCAL2DARMTF_4to1200Hz.xml
J. Kissel, D. Tuyenbayev,
These are kappas calculated in the front-end after the TF measurements have been completed.
The optical gain is still ~15% lower w.r.t. the value in the DARM model parameters and the coupled-cavity pole frequency is ~ 340-350 Hz, which is higher compared to the yesterday's value (LHO alog 30391).
There's still more noise in the calculated values of fC. The SNR of the 331.9 Hz line is affected by a slightly increased noise in the [0.2, 1.0] kHz band.
Doing the same thing as was done in LHO aLOG 30475, I've grabbed similar undisturbed data from the times quoted in the original entry, and replotted them in matlab after doing some rudimentary math. The 15 minute (900 sec) average value (starting at Oct 12 2016 02:39:00 UTC) for all of the time dependent parameters just after the sweeps are: Param Units Mean Std kappa_{C} [ ] 0.868 pm 0.01 f_{cc} [Hz] 325 pm 5.5 Re: kappa_{PU} [ ] 1.01 pm 0.0089 Im: kappa_{PU} [ ] 0.0007 pm 0.015 Re: kappa_{TST} [ ] 0.998 pm 0.011 Im: kappa_{TST} [ ] -0.010 pm 0.0091 Input Power [W] 51.8 pm 0.029 The script to generate these values lives in /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/CAL_EPICS/get_fe_tdep_params.m
J. Kissel I've used Kiwamu's templates (LHO aLOG 29860) to gather new DARM OLG and PCAL2DARM transfer functions, to help increase the number of data points for darm coupled cavity pole and SRC detuning spring frequencies. In doing so, I've found that PCAL suggests that CAL-DELTAL_EXTERNAL is wrong low by ~20% above 50 Hz, in a frequency dependent fashion (confirmed by the phase and ridiculously high coherence). We will analyze the data in-full, and report what the measured pole and spring frequencies are in the morning. We'll also show trends of calibration line heights, such that eventually we can confirm the frequencies over time. This frequency dependent error in CAL-DELTAL_EXTERNAL may be because the DARM coupled cavity pole frequency programmed into the CAL CS fron end is 342 Hz, and that's just not correct for this lock stretch. We have to turn OFF the PCALY calibration lines during the measurement due to range issues, but the front end calculation of the DARM cavity pole, after the measurement, suggests anywhere for 315 Hz to 340 Hz. Unclear whether we can trust the online calculation just yet, so we're leaving the IFO alone for ~30 minutes after the measurement to be able to confirm offline later. Recall that we're still not controlling the cavity waist angle/translation of the SRC entirely: the SRC1 loop (nominally controlling SRM alone) is OFF, but the SRC2 loop (controlling SRM and SR2) is ON. Undisturbed time post-sweeps: Start Oct 11 2016 02:36:00 UTC Oct 10 2016 19:36:00 PDT 1160188577 Stop Oct 11 2016 03:07:00 UTC Oct 10 2016 20:07:00 PDT 1160190437 The new measurements have not yet been exported, but have been committed to the CalSVN here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/ DARMOLGTFs/2016-10-10_H1_DARM_OLGTF_4to1200Hz.xml PCAL/2016-10-10_H1_PCAL2DARMTF_4to1200Hz.xml EDIT: I've added two screenshots showing the digital settings relevant to the DARM loop parameters. Unfortunately, the production conlog is down for maintenance/upgrades, but thankfully Patrick setup a test bed a few nights ago (goto http://conlog-test-replica/), I was able to pull the list of channels I needed. FAlso for the record, some of those channels have changed since O1, so I quote the new list here for easier copy and paste in the future: H1:LSC-DARM1_SWSTAT H1:LSC-DARM1_GAIN H1:LSC-DARM2_SWSTAT H1:LSC-DARM2_GAIN H1:SUS-ETMY_L1_LOCK_L_SWSTAT H1:SUS-ETMY_L1_LOCK_L_GAIN H1:SUS-ETMY_L1_DRIVEALIGN_L2L_SWSTAT H1:SUS-ETMY_L1_DRIVEALIGN_L2L_GAIN H1:SUS-ETMY_L2_LOCK_L_SWSTAT H1:SUS-ETMY_L2_LOCK_L_GAIN H1:SUS-ETMY_L2_DRIVEALIGN_L2L_SWSTAT H1:SUS-ETMY_L2_DRIVEALIGN_L2L_GAIN H1:SUS-ETMY_L3_ISCINF_L_SWSTAT H1:SUS-ETMY_L3_ISCINF_L_GAIN H1:SUS-ETMY_L3_LOCK_L_SWSTAT H1:SUS-ETMY_L3_LOCK_L_GAIN H1:SUS-ETMY_L3_DRIVEALIGN_L2L_SWSTAT H1:SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN H1:SUS-ETMY_L3_LOCK_INBIAS H1:SUS-ETMY_L3_ESDOUTF_LIN_BYPASS_SW H1:SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF H1:SUS-ETMY_BIO_M0_STATEREQ H1:SUS-ETMY_BIO_L1_STATEREQ H1:SUS-ETMY_BIO_L2_UL_STATEREQ H1:SUS-ETMY_BIO_L2_LL_STATEREQ H1:SUS-ETMY_BIO_L2_UR_STATEREQ H1:SUS-ETMY_BIO_L2_LR_STATEREQ H1:SUS-ETMY_BIO_L3_UL_STATEREQ H1:SUS-ETMY_BIO_L3_UR_STATEREQ H1:SUS-ETMY_BIO_L3_LL_STATEREQ H1:SUS-ETMY_BIO_L3_LR_STATEREQ
J. Kissel, D. Tuyenbayev,
Kappas calculated in the front-end suggest that an optical gain was lower compared to the reference time (optical gain in the DARM model) by ~15% and the coupled-cavity pole frequency was ~325 Hz at the TF measurement time.
Also it seems that the SNR of 331.9 Hz line is not sufficient - higher statistical noise in the calculated κC and fC.
A little bit more quantitative assessment if the time dependent correction factors as computed by the front end (or "kappas"):
I've grabbed similar undisturbed data from the times quoted in the original entry, and replotted them in matlab after doing some rudimentary math. The 15 minute (900 sec) average value (starting at Oct 11 2016 02:51:00 UTC) for all of the time dependent parameters just after the sweeps are:
Param Units Mean Std
kappa_{C} [ ] 0.866 pm 0.011
f_{cc} [Hz] 323 pm 4.5
Re: kappa_{PU} [ ] 1.01 pm 0.011
Im: kappa_{PU} [ ] -0.007 pm 0.012
Re: kappa_{TST} [ ] 0.998 pm 0.0085
Im: kappa_{TST} [ ] 0.0095 pm 0.0065
Input Power [W] 50.5 pm 0.031
The script to generate these values lives in
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/CAL_EPICS/get_fe_tdep_params.m
And for ease of copy and paste for someone in the future, I'm gathering the following channels (which correspond to the parameters in the same order as the table above)
H1:CAL-CS_TDEP_KAPPA_C_OUTPUT
H1:CAL-CS_TDEP_F_C_OUTPUT
H1:CAL-CS_TDEP_KAPPA_PU_REAL_OUTPUT
H1:CAL-CS_TDEP_KAPPA_PU_IMAG_OUTPUT
H1:CAL-CS_TDEP_KAPPA_TST_REAL_OUTPUT
H1:CAL-CS_TDEP_KAPPA_TST_IMAG_OUTPUT
H1:IMC-PWR_IN_OUTPUT
WP6232 Upgrade frame writers
Jonathan, Jim B, Dave:
h1fw2 was running with close to the new code, it was upgraded to add the md5 filename change only. Quickly following h1fw0 and h1fw1 were upgraded to the latest code. I am updating the DAQ MEDM to show the new diagnostic md5 check sum data.
WP6217 ISI frontend code upgrade
Hugh, Jim B
All ISI models were restarted with new code
WP6227 HEPI frontend code upgrade
Hugh, Jim B
All HEPI models were restarted with new code.
WP6235 PSL-DBB jitter feed-forward to LSC
Daniel, Gabrielle, Dave:
New code on the h1psldbb exports the jitter signal as a 64kHz Dolphin channel. The h1lsc model uses this feed-forward data. Change added a 16kHz LSC DQ channel to the commissioning frame.
WP6242 Migration of virtual machines to proxmox
Carlos
Old vmware virtual hosts were migrated to the new Proxmox system.
WP6236 SUS ITMX.ETMX model changes for HWWD install
Fil, Richard, Jim B, Dave
sister wp to 6234. The ITMX and ETMX hardware watchdogs were install. The h1susitmx, h1susetmx models were modified to read the HWWD status via the binary input feed from these chassis. Since we are not controlling these units, I did not put in the binary output logic.
WP6229 h1tcscs model change for SIM parts
Kiwamu, Dave
A new h1tcscs model was installed. We verified that the TCS CO2 chillers behaved correctly on loss of temperature control voltage.
WP6231 GDS-DMT upgrade
team-GDS
Code was upgraded, no impact was seen from the control room
WP6239 PSL-ISS model change
Daniel, Dave
New h1psliss model was installed. This was done at the same time as the h1psldbb change.
WP6240 Beckhoff Slow Controls change
Daniel, Dave
Daniel installed new PLC code. I updated the DAQ INI files, the target autoBurt.req files and the Beckhoff SDF monitor files.
WP6238 CAL-CS model change
Darkhan, Jeff K, Dave
a new h1calcs model was installed.
DAQ restarts
Dave:
The DAQ was restarted several times today to support the above work.
(note we did not get to removing h1ldasgw2 WP#6237, will defer this to later in the week)
Regarding the following:
WP6217 ISI frontend code upgrade
Hugh, Jim B
All ISI models were restarted with new code
Only the HAM ISIs models were updated. I might have implied to DaveB that I was going to do something to the BSC ISIs but in the end I do no changes there.
That's a bit concerning and not something that I believe we've seen (other than on this one system recently). Certainly possible that it's an air bubble. We'll need to watch this because if the flow sensor causes it to trip out then we will start having down time on the laser. Are there any bubbles visible in any of the tubing or do you think these are getting trapped at some high point in the system? The highest point overall should be up at the chillers, but there will be other local high points such as on the table.
The trend suggests that the flow rate only went to 0 for 3 seconds then made its way back up. Bubble does sound reasonable.
There look to be some regular dips in flowrate, perhaps also bubble related. Might be easier to see in non-trended data how long and deep these dips are.
I took a 30 second full data trend from the trip, also including the interlock signal. As can be seen the flow rate is not at its usual value of ~3.0 gpm for approximately 10 seconds. Interestingly, the interlock does not trip until the flow has been below nominal for ~3 seconds. Is this the expected behavior of this interlock?
There is a low pass filter on the input, so yes that's expected behavior. I am surprised that it goes negative though - this should be linear in current from the flowmeter which makes me think it can't go negative without the flowmeter running backwards.