1605 - 1620 hrs. local -> To and from Y-mid Opened exhaust check-valve bypass-valve, opened LLCV bypass-valve 1/2 turn -> LN2 at exhaust in 45 seconds -> Restored valves to as found configuration. Next overfill to be Friday, July 29th.
Lowered CP3 LLCV from 19% to 18% open. Interesting change in exhaust pressure trend going from 20% to 19% this morning.
And a different trend pattern yet lowering from 19% to 18%.
| Name | WP Date | Description | Alog reference |
| 6008.html |
2016-07-25 12:48 |
Activity: i. Replace water filters. ii. Replace flow sensor in the crystal chiller. The laser needs to be taken down in order to perform this task. |
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28652 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28657 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28675 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28637 |
| 6009.html | 2016-07-25 13:49 | Activity: Install a gutter on the back side of the Carpenters shop. | |
| 6010.html | 2016-07-25 13:57 | Activity: Perform 5 year inspection of the fire water holding tank. The divers will enter the tank, clean the bottom, inspect the intake & discharge piping, and the tank. | |
| 6011.html | 2016-07-25 14:11 | Activity: Perform quarterly lubrication of Axivane Supply Fans and semi-annual lubrication of those fan motors at Corner Station and both Mid & End Stations. | |
| 6012.html | 2016-07-25 15:25 | Activity: Install new version of GDS software to address bugzilla bugs 1027 (diag), 961 (diaggui), 1017 (foton), 628 awggui. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28658 |
| 6013.html | 2016-07-25 15:55 | Activity: Swap the ETMy optical lever laser with a new one to hopefully address complaints about oplev performance. The cooler will need to be opened, so after the swap the new laser will need 4-6 hours to come to thermal equilibrium. No view ports will be exposed during this work. |
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28645 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28641 |
| 6014.html | 2016-07-25 15:59 | Activity: Run network and power cables to ITM cameras at X&Y spool end. | |
| 6015.html | 2016-07-25 16:34 | Activity: Replacing annulus ion pump on BCS8 will require relocating single-person Genie man lift from receiving area to BCS8, next to TCS table. This will require moving the TCS table partitions. A turbo aux cart will run all day or until the IP can pump alone. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28648 |
| 6016.html | 2016-07-25 16:54 | Activity: Install new framewriter h1fw2. Will be used to investigate frame writer instabilities, may be used as a separate trend frame writer. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28659 |
| 6017.html | 2016-07-25 17:10 | Activity: Check output of Stage2 H2 Coil Driver: Make platform safe, disconnect output of Coil Driver, drive ISO Loop with increasing amp sine. Monitor output of CD in CER. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28649 |
| 6018.html | 2016-07-25 18:19 | Activity: Fix slow channel name bugs in code for h1omc, h1susitmpi, h1susetmxpi and h1susetmypi. DAQ restart and MEDM changes also needed. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28659 |
| 6019.html | 2016-07-25 20:31 | Activity: Escort film crew around LVEA. | delayed to Wednesday, 2016 July 27 |
| 6020.html | 2016-07-26 15:19 | Activity: Change whitening gain and filters for the ITMx, ITMy and ETMx optical levers per LHO alog 28615. This only involves changing dip switch states on the relevant Output Configuration Switches. The following changes will be made: ITMx whitening gain to 21 dB, ITMy whitening gain to 15 dB and add 2 whitening filters, ETMx add 1 whitening filter. No view ports will be exposed during this work. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28645 |
| 6021.html | 2016-07-26 15:26 | Activity: Placing additional sensors in the LVEA for the Newtonian noise array. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28660 |
| 6022.html | 2016-07-26 16:46 | Activity: To be able to do the beacon dither alignment, we will place (1)an IPC receiver in h1omc, (2) add digital filters to h1omc, (3) set up an amplitude stabilization loop in h1omcpi, h1omcprocpi and h1etmx(y)pi models. DAQ restart required. | |
| 6023.html | 2016-07-26 16:56 | Activity: Minor bug fix to CAL-CS front end model. See LLO aLOG 27214. | https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28640 |
| 6024.html | 2016-07-26 18:39 | Activity: Remove Pcal camera housing at X-beam manifold spool viewport which was installed last week. Housing does not clear vacuum bellows wall by 1 cm. |
discussed in System’s Meeting, 2016 Juy 27 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28650 |
| 6025.html | 2016-07-26 21:51 | Activity: Add PRCL FF path. Add FF outputs to commissioning frames. |
Topped off the Crystal Chiller with 110mL of water. (Peter added 100mL the day before).
Diode Chiller had a green light (no action taken/needed).
Closed FAMIS#6481.
lowered CP3 LLCV from 20% to 19% to reduce exhaust pressure to below 1 psi.
[Jenne, Terra]
We need to go back tomorrow to see how much we were actually moving the spot on the PRM (which we should be able to calculate based on angles of optics), but I didn't see any qualitative change in the interferometer while I was moving things.
Terra had moved the PRC1 pit offset to recover much of our lost recycling gain. Then we started moving IM3 in pitch, using Stefan's script (alog 28627) to have other optics follow us around. After moving the PRC1 offset, we noticed that the buildups of carrier power were noticably more "ratty" and raggety than before we introduced the offset. We were hoping that moving the spot on the PRM would help, but it did not. Since we had lost lock once earlier this evening due to moving the spot on PR2, I didn't try that again. Note to self: started moving IM3 around 00:21:00 local. Look at camera IR positions, baffle PDs, etc.
Since this ratty-ness of the carrier buildups is also seen in the transmon QPDs, and the ISS 3rd loop was closed, the power injected into the vacuum was also moving around a lot. We solved this by switching from the 3rd loop to the 2nd loop.
ETMY's L3 state is currently 1: lowpass off. We will need to turn them back to 2: lowpass on in the future. I tried increasing the power from 2W with ETMY on the low voltage driver, but had forgotten to turn off the lowpass, and this blew the lock. I haven't retried with the lowpass off, or starting from higher power.
Since we moved sliders for IM3, IM4, PRM and PR2, if the daytime operator has any trouble locking, go back to the witness / oplev positions for these optics from the time just before I started moving IM3's sliders.
PI damping was successful after the model changes today. MEDM screens have been updated as well.
We are continuing to see gain phase flips every so often even when using the TransMon QPDs for error signal (some opposite at the start of a new lock, some changing mid lock). Two occured while Jenne was moving the spot position on PRM (15522 ITMX, 15541 ETMX); will investigate more tomorrow.
[Jenne, Terra, Koji]
We are leaving the IFO in Observing mode (intent bit set), so that the analysis teams can check their pipelines. Should be Undisturbed since about 07:48:00UTC. We did not do the Coil Drivers state, but that isn't our current noise limit (it's the usual ASC and A2L at low freqs, and then what looks like intensity noise at higher freqs).
OMC whitening cannot be turned on - I speculate that it's the too-high 2nd order violin modes causing the saturations. We are not currently damping any 2nd order modes.
Checking coherence of some LSC/ASC channels with regard to DARM.
LSC:
- PRCL has high coherence around the peak structure at 350Hz.
- MICH has several freqs below 40Hz to have 0.4~0.5 coherence.
ASC:
- DHARD_P is dominant between 27 to 40Hz. It also has high coherence (~0.7) between 8~13Hz
- CHARD_Y is dominant between 10 to 27Hz.
- SRC2_Y has coherence of ~0.5 between 8~13Hz.
- INP1_P is dominant at 15-20Hz.
TITLE: 07/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY: Finished initial alignment at beginning of shift. Other than a pause to let Keita and Evan work on POPX, we have been locking well all night.
LOG:
23:15 Kyle to EY VEA
23:41 Kyle back
Keita and Evan to LVEA POP X work
NOTE FOR OPERATORS: At one point, I attempted to do a quick MICH_DARK alignment after a lockloss since the AS spot looked bad. I set ISC_LOCK directly to INITIAL_ALIGNMENT, which caused the IMC to lose lock. It would not relock and while looking for the culprit, I found a large input value going to MC2 L3 LOCK bank. Jenne and I could not find the source of the input, and Jenne decided to put ISC_LOCK into DOWN. This immediately fixed the issue and the IMC locked back up. TAKE AWAY: Always go through DOWN in ISC_LOCK when going back to do any initial alignement work.
Since POPX PZT rails quite often, we relocated the pzt to the upstream of the second lens which is a -172mm diverging lens. The beam now hits the PZT mirror after POP-BS1, the beam travels to +Y direction (toward the ISCT1 door), passes POP-L2 lens, is reflected by a fixed steering mirror, travels to +X-Y direction and hits POP-X.
This allowed us to make the distance between the lenses and the distance between the last lens and WFS closer to LLO configuration.
| Used to be (inches) | Is now | LLO (D1201103) | |
| POP-L1 to POP-L2 | 16 | 20 | 20 + 1/4 |
| POP-L2 to POP-X | 11 + 1/2 | 12 | 12 |
I flipped the sign of YAW centering for POPX because we now one steering mirror between the PZT mirror and the WFS. I also told Jenne to flip the sign of ASC YAW input matrix element for POP_X.
I decreased the overall gain for YAW and PIT due to the increased effective lever arm due to physical length plus a diverging lens, otherwise the centering oscillated badly.
| Old | New | |
| H1:ASC-POP_X_PZT_PIT_GAIN | 100000 | 50000 |
| H1:ASC-POP_X_PZT_YAW_GAIN | 100000 | -50000 |
Table photo attached.
I measured the PRC2 ASC loops, and increased their gain significantly. I also measured the POPX centering loop and decreased its gain even more than Keita had already done.
The first and second attachments are the PRC2 pitch and yaw loops. Blue is a reference from mid-May, green is what the loop looked like with the old digital gain value but new POPX position, and red is the loop after the increase in gain. Both loops started with a digital gain of -21. Pitch is now -5,000 and yaw is now -10,000.
The final attachment is the pitch centering loop for POPX. I adjusted the gain until the bandwidth was 10 Hz, which is what it had been set to when Keita originally commissioned that loop (alog 27280). I assumed that yaw was pretty similar to pitch, although I didn't explicitly measure it. I changed the DC6 gains to 0.15 for pit and -0.15 for yaw, from 1 and -1 respectively.
These new values are all accepted in the ASC down SDF.
David.M, Jenne.D
Today I set up a further 13 L4Cs in the LVEA, this time they are much more spread out than last week so watch out for them around the LVEA. This means that now all of the sensors in the array except for one have been fixed on the floor. (This last L4C is right in the middle of the path on the first corner near the beam splitter chamber). All of the L4Cs have the foam box coolers taped down on top of them which should make it obvious that they are there. I'm going to finish the cables and neaten everything up one morning this week so hopefully there wont be any problematic tripping hazards. The numbering scheme has been updated so now the previous scheme is invalid. Once I finish connecting all of the sensors I will make a new post with the updated scheme and an updated map.
SUS PI code change WP6018
Carl, Terra, Jim, Dave:
New code was installed for h1susitmpi, h1omc, h1susprocpi, h1susetmxpi, h1susetmypi. The model changes went in normally, but the DAQ restart was problematic. The data concentrator error'ed on duplicate channels for H1:SUS-PI_PROC_COMPUTE_MODE9_PLL_SIG_OUT. This was surprising as I had ran my script to check for duplicates prior to the DAQ restart. We reconfigured the DAQ sans h1susprocpi to get the DAQ running again while we investigated the problem. Jim found the problem, in the sys/common/models/PLL_MASTER.mdl file, a testpoint part was named SIG_OUT in addition to a filter module at that level which was named SIG, and the filtermodule has a testpoint also called SIG_OUT. This common part had 32 such duplicates, MODE9 was just the first to be reported.
Terra fixed the models, we restarted h1susprocpi, reintroduced it to the DAQ and restarted the DAQ.
I extended the script check_daq_channel_list_for_duplications.bsh to check both INI files and PAR files.
DAQ Restarts
Jim, Dave:
h1tw0 has become fragile lately (not so h1tw1). We discovered that if we restart the DAQ while h1tw0 is in the midst of writing the raw minute files, this can corrupt the file system requiring an fsck to fix. Today we were careful to only restart the DAQ while h1tw1 was inbetween file writes. This has worked and h1tw0 has not crashed.
In two of today's DAQ restarts we needed to restart the mx-stream on a handfull of frontends.
GDS code upgrade WP6012
Jim:
New GDS code was installed, details in Jim's alog.
New LSC code
Jenne, Dave:
Jenne's new h1lsc code was installed. This added some channels to the commissioning frame (eight channels at 2048Hz).
Radio receiver spectrum analyser work
Carlos, Jordan:
The RF analyser was attached to the FLIR camera windows server, code was installed and tested.
New DAQ frame writer WP6016
Carlos, Dave, Jonathan, Jim:
we installed a new frame writer called h1fw2. It is a standard front end computer using a spare Myricom 10GE card. New SFP and RAM (48GB) were purchased for the unit. This is a dual boot machine (Ubuntu 12 and Debian 8). It has a 1TB internal HDD which we are using for testing. Jim and Jonathan did some Deb8 work on it. We determined 48GB is not sufficient for it to write all the frame types.
As the system is currently configured:
h1fw0 is writing commissioning and science frames (no trends). It is now 100% stable, has been running for 6 days.
h1fw1 is writing all frames. It is unstable, restarting on average every 2 hours.
h1fw2 is writing commissioning and science frames (no trends) to its local disk.
All three have been running for about two hours now. I've extended the DAQ overview MEDM to show all three and check their frames are identical. It would be good to run three writers for O2, if the frames were not identical a trio of writers could indicate which is the incorrect frame.
JimW, JeffK, HughR
Around 1900 utc, the pressure dropped and the servo drive went to max; from afar, this looks like a fluid level trip. Jeff went to the end station and found that the front panel red light was still on indicating it was not a fluid level trip. Opening the controller panel to access the VFD revealed the OU3 error indicator. Last aLog with this problem found with quick search was at EndY July 2015. Maybe it is a warmer weather problem. Brought control servo output to 0, reset VFD to clear the error and then brought things back under servo control, around 2200utc. Jeff noted the fluid levels were same as before--no fluid problems.
Pictures from the investigation attached. First: The front of the fluid level indicator of the HEPI pump fluid reservoir. Second: The "iso" view of the fluid level indicator, showing that the fluid level with the pump servo OFF (or "stopped" or tripped like it was when we found itp) is at 9 2/16 inches, which matches the level in early June when the level was last checked without the pump running. Third: a look inside the Variable Frequency Driver (VFD) enclosure taking a picture of the VPD while in its "OU3" (for Output Voltage 3) error. The "reset" button to which Hugh refers is in the bottom left corner.
According to the manual OU3 is an "over voltage error while at constant speed". - see attached page.
Other VFDs on site have similar issues which we think is due to spikes on the 3 phase supply.
Richard can tell you more.
In response to Keita's alog (here) I changed the whitening gain and number of active filters on the ITMx, ITMy, and ETMx optical levers. They are now set as outlined in the 2nd table in Keita's alog. I also enabled the corresponding de-whitening filters in the oplev filter medm screens (ITMy and ETMx only, as these were the only ones that had additional whitening filters enabled) and accepted the changes in SDF.
I took spectra of each segement of the QPD for each TM oplev, both before and after the de-whitening filters (channels labeled IN1 are before de-whitening, channels labeled OUT are after de-whitening) as well as spectra of the pitch and yaw signals of each oplev.. To my knowledge, ETMx and ETMy look as they are supposed to. On the other had, the ITMx and ITMy QPD spectra do not look right to me. When I took the spectra there were ongoing investigations into ITMx ISI coil driver issues and ITM charge measurements (ie, the optics were moving); also, the oplev lasers for both ITMx and ITMy oplevs are unstabilized lasers, sitting on the LVEA floor. All of these could be causing issues with the measurements; they should be re-taken once things have quieted down and see if there are differences. If there are no differences, I fear we may have made things worse for the ITMs. There also appears to be a comb in all of the ITMy spectra. I think this is caused by the laser glitching; as soon as I have a stabilized laser ready for install this laser is getting replaced.
This completes WP #6020.
ITMX looks good to me. All quadrants look similar to each other and the PIT plot looks better than before (e.g. https://alog.ligo-wa.caltech.edu/aLOG/uploads/28615_20160725101947_Screenshotfrom2016-07-2510%3A01%3A12.png).
ITMY looks OK-ish to me except at high kHz for segment 1 and 3, which need to be investigated further. But the thing is that ITMY used to be without any whitening gain and filter that there was no way this kind of oddness could have been revealed before. See the attached plot of the current ITMY oplev signals with the pink line showing the old noise floor, and compare with the above mentioned old plot.
Koji, Evan
We removed the unmodified BBPD S1200242 from ISCT6, and replaced it with S1200236, which has the modifications described in G1500595.
Evan already compensated 12dB (x4). This is indeed consistent with the transimpedance difference betwen the old (1800Ohm@90MHz) and new (450Ohm) BBPD.
The attached plot shows the difference of the normalized RF90 before and after the swap. The gain is matched within 3%.
The goal of yesterdays firmware upgrade was to change the behavior of the blinking LED lights and to allow for additional diagnostics of the problem. In the past the LED typically had three states: (i) Off, (ii) Blinking and (iii) On. This upgrade interchanged the states (ii) and (iii). For a typical link light this means: Off indicates no fiber signal, Blinking indicates a fiber signal is present, and On means the timing signal is received and synchronized. Operating without error now means all LEDs are On.
Furthermore, it is possible with the Altium JTAG port to change the behavior of the LED state while running and without disrupting the timing signal. LEDs which are on can be made to blink in rates of 0.5Hz, 1Hz, 2Hz, 4Hz, etc. This should allow us to isolate the coupling site.
The upgrade was successful for all timing slaves, but failed for the timing master/fanouts. Strangely, it failed due to bogus code in svn on how to calculated the CRC-32 (ethernet) checksum. Baffling. More investigations are ongoing.
A new version 3 of the master fanout firmware is ready for test and available here. This version cleans up some timing closure issues during synthesis/translation and gerenates a correct CRC-32.
Upgrade of Timing Firmware
Daniel, Ansel, Jim, Dave
Most of today was spent upgrading the entire timing system to the new V3 firmware. This did not go as smootly as planned, and took from 9am to 6pm to complete. By the end of the day we had reverted the timing master and the two CER fanouts to the orginal code (the end station fanouts were not upgraded). We did upgrade all the IRIG-B fanouts, all the IOChassis timing slaves, all the comparators and all the RF Amplifiers.
The general order was: stop all front end models and power down all front end computers, upgrade the MSR units, upgrade the CER fanouts, upgrade PSL IO Chassis (h1psl0 was restarted, followed by a DAQ restart), upgrade all CER slaves (at this point the master was reverted to V2), at EY we upgraded IRIG-B and slaves (skipping fanout), at MY we upgraded the PEM IO Chassis, at EX we did the same as EY and at MX the same as MY.
All remaining front ends were now powered up. The DAQ was running correctly but the NDS were slow to complete their startup. Addiional master work in the MSR required a second round to restarts, at this point comparators which had been skipped were upgraded and the CER fanouts were downgraded. Finally after h1iopsush56 cleared a long negative irig-b error all systems were operational.
During these rounds of upgrades FEC and DAQ were restarted several times.
Addition of Beam Splitter Digital Camera
Richard, Carlos, Jim
An analog camera was replaced with a digital video GIGE-POE camera at the Beam Splitter.
New ASC code
Sheila:
new h1asc code was installed and the DAQ was restarted.
Reconfigured RAID for ldas-h1-frames file system
Dan:
The ldas-h1-frames QFS file system was reconfigured for faster disk access. This is the file system exported by h1ldasgw0 for h1fw0's use. After the system was upgraded, we reconfigured h1fw0 to write all four frame types (science, commissioning, second and minute). As expected, h1fw0 was still unstable at the 10 minute mark, similar to the test when h1fw0 wrote to its own file system. h1fw0 was returned to its science-frames-only configuration.
Just curious -- it's my impression that the point of "upgrading the timing system to the new V3 firmware" was to reprogram all timing system hardware's LED lights so as to not blink every second or two, because we suspect that those LEDs are somehow coupling into the IFO and causing 1 to 2 Hz combs in the interferometer response. The I/O chassis, IRIG-B, comparators, and RF amplifiers are a huge chunk of the timing system. Do we think that this majority will be enough to reduce the problem to negligible, or do we think that because the timing master and fanouts -- which are the primary and secondary distributors of the timing signal -- are still at the previous version that we'll still have problems?
With the I/O chassis timing upgrade we removed the separate power supply form the timing slaves on the LSC in the corner and both EX and EY ISC chassis. Hopefully the timing work will eliminate the need for the separate supplies.
Could you clarify that last comment? Was yesterday's test of changing the LED blinking pattern done in parallel with removal of separate power supplies for timing and other nearby electronics?
Ansel has been working with Richard and Robert of the past few months testing out separate power supplies for the LEDs in several I/O chassis (regrettably, there are no findable aLOGs showing results about this). Those investigations were apparently enough to push us over the edge of going forward with this upgrade of the timing system. Indeed, as Richard says, those separate power supplies were removed yesterday, in addition to upgrading the firmware (to keep the LEDs constantly ON instead of blinking) on the majority of the timing system.
To clarify Jeff's comment: testing on separate power supplies was done by Brynley Pearlstone, and information on that can be found in his alog entries. Per his work, there was significant evidence that the blinking LEDs were related to the DARM comb, but changing power supplies on individual timing cards did not remove the comb. This motivated changing the LED logic overall to remove blinking. I'm not sure whether the upgrades done so far will be sufficient to fix the problem. Maybe Robert or others have a better sense of this? Notable alog entries from Bryn: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=25772 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=25861 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=27202
I have gone through and manually compared FScan spectrograms and normalized spectra for the 27 magnetocometer channels that are processed daily: https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H1_DUAL_ARM/H1_PEM/fscanNavigation.html, to look for changes following Tuesday's timing system intervention, focusing on the lowest 100 Hz, where DARM 1-Hz (etc.) combs are worst. Because of substantial non-stationarity that seems to be typical, it's not as straightforward as I hoped it would be to spot a change in the character of the spectra. I compared today's generated FScans (July 20-21) to an arbitrary choice two weeks ago (July 6-7). But these six channels seemed to improve w.r.t. narrow line proliferation: H1_PEM-CS_MAG_EBAY_LSCRACK_X_DQ H1_PEM-EX_MAG_EBAY_SUSRACK_X_DQ H1_PEM-EX_MAG_EBAY_SUSRACK_Y_DQ H1_PEM-EX_MAG_EBAY_SUSRACK_Z_DQ H1_PEM-EY_MAG_EBAY_SUSRACK_X_DQ H1_PEM-EY_MAG_VEA_FLOOR_X_DQ (before & after figures attached) while these four channels seemed to get worse w.r.t. narrow lines: H1_PEM-EX_MAG_VEA_FLOOR_Z_DQ H1_PEM-EY_MAG_EBAY_SEIRACK_X_DQ H1_PEM-EY_MAG_EBAY_SEIRACK_Y_DQ H1_PEM-EY_MAG_EBAY_SEIRACK_Z_DQ In addition, many of today's spectrograms show evidence of broad wandering lines and a broad disturbance in the 40-70 Hz band (including in the 2nd attached figure).
Weigang Liu has results in for folded magnetometer channels for UTC days July 18 (before changes), July 19-20 (overlapping with changes) and July 21 (after changes): Compare 1st and 4th columns of plots for each link below. CS_MAG_EBAY_SUSRACK_X - looks slightly worse than before the changes CS_MAG_EBAY_SUSRACK_Y - periodic glitches higher than before CS_MAG_EBAY_SUSRACK_Z - periodicity more pronounced as than before CS_MAG_LVEA_VERTEX_X - periodic glitches higher than before CS_MAG_LVEA_VERTEX_Y - periodic glitches higher than before CS_MAG_LVEA_VERTEX_Z - periodic glitches higher than before EX_MAG_EBAY_SUSRACK_X - looks better than before EX_MAG_EBAY_SUSRACK_Y - looks better than before EX_MAG_EBAY_SUSRACK_Z - looks slightly worse than before EY_MAG_EBAY_SUSRACK_Y - looks slightly better after changes EY_MAG_EBAY_SUSRACK_Z - looks the same after changes (Weigang ran into a technical problem reading July 21 data for EY_MAG_EBAY_SUSRACK_X) A summary of links for these channels from ER9 and from this July 18-21 period can be found here.
