Displaying reports 11561-11580 of 84672.Go to page Start 575 576 577 578 579 580 581 582 583 End
Reports until 16:14, Wednesday 10 January 2024
LHO General
austin.jennings@LIGO.ORG - posted 16:14, Wednesday 10 January 2024 (75310)
Ops Eve Shift Start

TITLE: 01/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.64 μm/s
QUICK SUMMARY:

- H1 just got back into observing (acquired @ 23:58)

- Secondary microseism is still high, but low enough where we can relock if H1 goes down

- CDS/DMs ok

LHO General
thomas.shaffer@LIGO.ORG - posted 16:09, Wednesday 10 January 2024 (75302)
Ops Day Shift Summary

TITLE: 01/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Austin
SHIFT SUMMARY: Two locks in the morning, then during commissioning time multiple locks and lock losses while testing a new DARM actuator. We are now back to observing, but violins are high and getting damped.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
16:22 PCAL Tony Pcal lab local Meas. 16:29
17:02 FAC Kim MX n Tech clean 18:05
17:03 VAC Janos, Travis MY, MX n Hetpa oil change 19:40
17:04 FAC Karen Vac prep, opt. lab n Tech clean 17:32
17:32 FAC Karen MY n Tech clean 18:37
17:55 VAC Jordan Vac prep n Assembly 20:05
18:20 FAC Tyler EY n Check on wind fence 20:13
23:19 VAC Jordan Vac prep n Assembly 23:38
LHO General
richard.mccarthy@LIGO.ORG - posted 15:01, Wednesday 10 January 2024 (75309)
NEW Site Electric Vehicle Charge Station

Our new Electric Vehicle charge station was installed Tuesday 1/9/2024.  This is a stand alone solar/battery charger for the site vehicles.

There are two charger ports you can use simultaniously.  You can park under the solar panels on the steel plate but the charger cables will reach the parking spots around the unit.

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 14:52, Wednesday 10 January 2024 - last comment - 15:12, Tuesday 30 January 2024(75308)
NEW DARM transition attempts

Louis, Jenne, TJ, Sheila

Today we continued to try to transition to the new Darm configuration, which we had suceeded in doing in December but weren't able to repeat last week (75204). 

In our first attempt today we tried a faster ramp time, 0.1 seconds.  This caused immediate saturation of ETMX ESD.  We struggled to relock because of the environment. 

Because Elenna pointed out that the problem at roughly 3 Hz with the earlier transition attempts might have been the soft loops, we thought of trying to do the transition before the soft loops are engaged, after the other ASC is on.  We tried this first before transitioning to DC readout which wouldn't work because of the DARM filter changes.  Then we made a second attempt at DC readout.  We also lost lock due to a 2 Hz oscialltion, even without the soft loops on. 

Some gps times of transitions and attempt:

Comments related to this report
sheila.dwyer@LIGO.ORG - 15:42, Friday 12 January 2024 (75348)

Adding two more times to this list:

  • 1386538350 transition from December 13th, with configuration shown in screenshot ( 5 second ramp time) (L2 LOCK FM2, 10 and L1 LOCK FM2,4,10) (L3 master out max = 1e6)
  • 1386621508 Decmeber 14th L2 LOCK FM1,2,10 L1 LOCK FM2,6 5 second ramp time, 30000 counts max on ESD
  • 1387034098 transition from Decmeber 19th, L2 LOCK FM10 then add FM1+2 2 seconds later, L1 LOCK L FM2,6 (L3 master out max = 6e6)
  • 1387140058 transition December 20th, L2 and L1 SWSTATS the same as on the 19th (used guardian NEW_DARM), ESD max just below 2e6
  • 1387237746 transition December 21st using guardian (same as 19th and 20th)
  •  1388444283 Jan 4th failure, SWSTATs the same as on the 14th.
  • 1389131192 today attempt to reproduce Dec 13th transition, except that L2 lock boost was on (FM1 L2 LOCKL) 5 second ramp time (screenshot)

The second screenshot here shows the transitions from Dec 13th, 14th, and 19th. These are three slightly different configuration of the UIM filters and variations on which PUM boosts were on when we made the transition.  On the 14th the oscillation was particularly small, this was with our new UIM filter (FM 2 + 6) and with both PUM boosts on L2 LOCK FM1,2,10 already during the transition.  This is the same configuraition that failed mulitple times in the last two weeks.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 20:40, Wednesday 17 January 2024 (75451)

Today I went back to three of these transitions, December 14th (1386621508 sucsesful no oscillation) and Jan 4 (1388444283) + Jan 5th (1388520329) which were unsucsesfull attempts. It also seems as though the only change to the filter file since the Dec 14th transition is a change copy the Qprime filter into L1 drivealign, which has not been used in any of these attempts (this can't be used because tidal is routed through drivalign). 

In short, it doesn't seem that we made a mistaken change to any of these settings between December and January which caused the transition to stop working.

L1 DRIVEALIGN L2L 37888 no filters on  
L1 LOCK L 37922 FM2,6 (muBoostm, aL1L2)  
L2 DRIVEALIGN L2L 37968 FM5,7 (Q prime, vStopA)  
L2 LOCK L 38403 FM1,2,10 (boost, 3.5, 1.5:0^2, cross)  on the 5th FM1+ 2 were ramping while we did the transition  
L3 DRIVEALIGN L2L 37888 no filters on  
L3 LOCK L 268474240 FM8, FM9, FM10, gain ramping for 5 seconds (vStops 8+9, 4+5, 6+7)  
ETMX L3 ISCINF L 37888 no filters on  
DARM2 38142 FM2,3,4,5,6,7,8  
DARM1 40782 FM2,3,4,7,9,10  

 

louis.dartez@LIGO.ORG - 15:12, Tuesday 30 January 2024 (75634)
I added start and end time windows for the successful transitions in LHO:75631.
H1 CDS
david.barker@LIGO.ORG - posted 14:03, Wednesday 10 January 2024 - last comment - 14:18, Wednesday 10 January 2024(75306)
Camera issues on h1digivideo1

Erik, Dave, Patrick, TJ:

At 22:55 Tue PST the PR3 camera stopped updating. This morning I power cycled the camera and restarted the server process on h1digivideo1.

Soon after the AS AIR camera started blue-screen flashing on clients viewers. Each blue flash was short (less than a second),  the EPICS values did not show any flat-lining. The flash rate was random and about every 5 minutes.

We found nothing untoward on h1digivideo1.

For a first try at fixing this we restarted the server process on h1digivideo1 for this camer (h1cam16). This did not fix it.

For a second try we power cycled the camera via POE control and restarted the server process, again this did not fix it.

Then more cameras on h1digivideo1 started blue screen flashing, so at 13:37 we did a soft reboot of h1digivideo1.

Comments related to this report
david.barker@LIGO.ORG - 14:18, Wednesday 10 January 2024 (75307)

Did not fix it, flash rate is several per minute. Opened FRS30147

LHO FMCS
eric.otterman@LIGO.ORG - posted 13:15, Wednesday 10 January 2024 (75305)
AHU 3 hot deck temperature
There was concern regarding the temperatures of the areas around the control room. These spaces are supplied from AHU 3. The heaters which supply hot air for the hot deck operation were not running and have not been running for some time because the CFM set point of the AHU was below the duct pressure required to satisfy the flow switches. We increased the CFM from 12,000 to 14,000 CFM and this increased the duct pressure enough to satisfy the switches and enable the heaters. Bear in mind this will create a burning dust odor for a short time.
H1 General
thomas.shaffer@LIGO.ORG - posted 12:16, Wednesday 10 January 2024 (75304)
Out of Observing for Commissioning at 2008, Lock loss at 2012 UTC

Commissioning caused lock loss, tripped ETMX HEPI and ISIs. Recovering and relocking now.

H1 General
thomas.shaffer@LIGO.ORG - posted 10:54, Wednesday 10 January 2024 - last comment - 11:43, Wednesday 10 January 2024(75301)
Lock loss 1838 UTC

1388947149

No obvious cause. Ryan S noted that the LSC-DARM_IN1 channel seems to turn first like we have seen many times in the past.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 11:43, Wednesday 10 January 2024 (75303)

Back to Observing at 1942 UTC. A fairly fast relock.

LHO VE
david.barker@LIGO.ORG - posted 10:33, Wednesday 10 January 2024 (75299)
Wed CP1 Fill

Wed Jan 10 10:12:29 2024 INFO: Fill completed in 12min 25secs

Gerardo confirmed a good fill curbside.

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 09:39, Wednesday 10 January 2024 (75297)
Observing 1737 UTC

Back to Observing after some time out due to high useism and high wind.

H1 General
corey.gray@LIGO.ORG - posted 08:07, Wednesday 10 January 2024 - last comment - 08:07, Wednesday 10 January 2024(75293)
Owl Shift Status

H1 was left in a planned IDLE state overnight due to extreme weather conditions.

Environmental Status:

1) Microseism is well above the 95th percentile

2) Winds have atleast calmed down starting about 3.5hrs ago (2-3am local)

H1 Status:

Since H1 has been down for a long time, I immediately opted to go for an Initial Alignment (605am PT).  Unfortunately, green arms looked bad and way off (very minimal light in both arms).  As I type this alog, Y-arm has shown life via INCREASE FLASHES, but X-Arm is stuck in ENABLE WFS.  But my computer is slow, so I'm going to reboot & relog into NoMachine.

H1 Status Update (645am Local):

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 07:33, Wednesday 10 January 2024 (75294)

Reboot helped...only a little.  

ALSx has progressed from a sliver of light on its camera and 0.0 transmission on ndscope (when starting INCREASE FLASHES at 709am Local), to flashes of light and transmited light on ndscope of 0.25 via INCREASE FLASHES at 730am local.

Had a hand-off to TJ at 8am local.

(Slow) Baby Steps....

LHO General
thomas.shaffer@LIGO.ORG - posted 08:05, Wednesday 10 January 2024 (75295)
Ops Day Shift Start

TITLE: 01/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 11mph Gusts, 10mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.78 μm/s
QUICK SUMMARY: Corey has been getting green arms up and we will continue to try locking. Wind is now low but useism is still high, although trending down.

LHO FMCS
austin.jennings@LIGO.ORG - posted 23:57, Tuesday 09 January 2024 (75284)
Tuesday Eve Shift Summary

TITLE: 01/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

Tonight was a wash due to elevated secondary microseism and high winds that have started picking up again.

There have been intermittent MX temp alerts for the 202D channel, and trending it does show that there has been quite a swing in temperature throughout the night. I did see that there was a temperature related repair done at MX earlier today for a low temp alarm, so I'm not sure if this behaviour is expected, but Tagging FMCS just to be thorough
LOG:

No log for this shift.

Images attached to this report
H1 SQZ
camilla.compton@LIGO.ORG - posted 16:54, Tuesday 09 January 2024 - last comment - 10:47, Wednesday 10 January 2024(75285)
Seed and pump mode matching to OPO

Vicky, Camilla. Retaking OPO PZT modemattching scan from 66527 and 62691.

Set up: SQZ_MANAGER DOWN then NO_SQUEEZING, SQZ_FC to FC_MISALIGNED , SQZ_OPO_LR to DOWN, "! Toggle Seed/CLF" to let seed though, block CLF and block green pump. We turned up SEED power to 5mW, the polarization isn't good with 0.4mW rejected in HAM7 (but would need to go on table to adjust this).

Scanned OPO PZT1 with Sawtooth 400s period, plot attached for SEED.

Then reverted back to CLF, blocked CLF and looked at scan in green, decreased pump power from 22mW to 2.2mW using waveplate and H1:SQZ-OPO_ISS_DRIVEPOINT. Scan in plot attached.

Images attached to this report
Comments related to this report
victoriaa.xu@LIGO.ORG - 21:44, Tuesday 09 January 2024 (75290)

Summary: OPO IR and Green cavity scans look bad due to misalignment. Mode-matching into OPO cavity looks good. From today, estimating IR_TEM00 ~ 71% (pitch misaligned), GR_TEM00 ~ 56% (yaw misaligned). 

- We noticed that OPO cavity scans looked bad when we translated the squeezer crystal across the cavity (many peaks, see Oct 17, 2023 73524)
- It worse now than we measured in Dec 2022 66527 ( IR <= 82%, GR < 73% )
- But it was great when we replaced the OPO IR fiber collimator in the September 2022 vent, 64949 - with the new CLF collimator, we measured >94% IR_TEM00 mode-matching before closing HAM7.
- Note: OPO IR and GR mode-matching both look pretty good. The difference in TEM00 efficiency is misalignment. For IR, today we measured IR_TEM20_JAN2024 = 6.4%, which is consistent with Sept 2022 in-chamber IR_TEM20_SEPT2022 = 0.304/(5.48+.304) = 5.3% mismatch (from scope image). That 5% mismatch we measured in-chamber was further consistent with optics lab beam profiles of the new collimator, 63400 "This gives us 95% overlap with the target beam". For opo green, I couldn't see the TEM20 mode on the camera to clearly identify which peak it was, suggests the GR_TEM20 mode mismatch is quite small (thanks team cds for getting the sqzt7 green trans camera online 75286).

See below for details of OPO cavity scans using PZT1, while PZT2 = 0V (clf cmb slow output). We did not try the mode-matching dependence with OPO PZT 2, though that is a thing (62856, this image).

------------------------------------------------------------------------------------------------------------------------------------

OPO IR,  4.9 mW into seed fiber:  200 second scan, starting around 1388880769

IR_TRANS  (OPO_IR_TRANS_PD has dark offset -20e-6, ignoring this)
- TRANS_TEM00 =  0.055
- TRANS_TEM01 =  0.01   (pitch misaligned)
- TRANS_TEM02 =  0.005
Camilla calculated the sum of visible peak heights, peaks_sum = 0.0776 (=0.055+0.01+0.005+0.0019+0.0013+0.0004+0.004)
0.055/(0.055+0.01+0.005+0.0019+0.0013+0.0004+0.004) = 71% matched into TEM00
0.01/(0.055+0.01+0.005+0.0019+0.0013+0.0004+0.004) = 12.8% mis-aligned into TEM01 pitch
0.005/(0.055+0.01+0.005+0.0019+0.0013+0.0004+0.004) = 6.4% mis-matched into TEM02 *** same as Sept 2022 in-chamber mismatch (>94% IR_TEM00 coupling)

IR_REFL (refl dark offset = 30e-6, ignoring this)
- REFL_OFF_RES = 1.195
- REFL_ON_RES_TEM00 = 1.152
- REFL_ON_TEM10 = 1.187
- REFL_ON_TEM20 = 1.191

------------------------------------------------------------------------------------------------------------------------------------
OPO GREEN,  2.9 mW into pump fiber:  200 second scan, starting around 1388886980. 

GR_TRANS (trans dark offset = 1 is already subtracted off the following)
- TRANS_TEM00 =  10.66 uW   (85 V PZT1, note PDH 80 MHz sidebands)
- TRANS_TEM01 =   7.4 uW   (90V PZT1, yaw misaligned)
- TRANS_TEM02 =   ??? (maybe 1.02?) uW   (couldn't find TEM20 on camera while scanning)
tem00/peaks_sum =  10.66/(10.66+7.4+1.02) = 56% matched into tem00
tem10/peaks_sum =  7.4/(10.66+7.4+1.02) = 39% misaligned into tem10

GR_REFL (refl dark offset = +0.004, not subtracted yet) (calibrated below into "mW")
- REFL_OFF_RES = 0.35
- REFL_ON_RES_TEM00 = 0.27 around 90V, 0.29 over 100V    different at diff FSR's
- REFL_ON_TEM10 = 0.30 around 90V, 0.31 over 100V    different at diff FSR's
- REFL_ON_TEM20 = ???

Images attached to this comment
victoriaa.xu@LIGO.ORG - 10:47, Wednesday 10 January 2024 (75300)

Unsure if any of this relates to the recent 5-6 Mpc DARM improvement after the OPO relocked from ~40V to ~95V, LHO:75281, but connecting alogs for reference.

H1 CDS
david.barker@LIGO.ORG - posted 16:52, Tuesday 09 January 2024 - last comment - 08:37, Wednesday 10 January 2024(75287)
Power glitch 16:27 PST, DAQ CRC errors on h1susey

We had a power glitch which caused light to flicker at work and at my home on the other side of Kennewick. The only thing we could find in CDS was a single DAQ CRC error from h1susey to DC1 (DC0's data was not impacted).

There were no IPC errors.

I have cleared the CRC error and emailed LDAS to use FW0's frames when frame mismatches are seen at this time.

Comments related to this report
david.barker@LIGO.ORG - 08:37, Wednesday 10 January 2024 (75296)

Neither UPS units reported any power issues at the time. Also I was unable to see any problems looking at the fast mains monitor signals in the corner and EX.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 15:52, Tuesday 19 December 2023 - last comment - 10:23, Wednesday 10 January 2024(74916)
comparison of darm with OM2 hot vs cold

Jenne, Naoki, Louis, Camilla, Sheila

Here is comparison of the DARM CLEAN spectrum with OM2 hot vs cold. The second screenshot shows a time series of OM2 cooling off.  The optical gain increased by 2%, as was seen in the past (for example 71087).  Thermistor 1 shows that the thermal transient takes much longer (12 + hours) than what thermistor 2 says (2 hours). 

Louis posted a comparison of the calibration between the two states, there are small differences in calibration ~1% (74913).  While the DARM spectrum is worse below 25Hz, it is similar at 70 Hz where we in the past thought that the sensitivity was worse with OM2 cold.  From 100-200 Hz the sensitivity seems slightly better with OM2 cold, some of the peaks are removed by Jenne's jitter subtraction (74879) but there also seems to be a lower level of noise between the peaks (which could be small enough to be a calibration issue).  At high frequency the cold OM2 noise seems worse, this could be because of the squeezing.  We plan to take data with some different squeezing angles tomorow and will check the squeezing angle as part of that.

So, it seems that this test gives us a different conculsion than the one we did in the spring/summer, and that now it seems that we should be able to run with OM2 cold to have better mode matching from the interferometer to the OMC.  We may have not had our feedforwards well tuned in the previous test, or perhaps some other changes in the noise mean that the result is different now. 

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 09:57, Wednesday 20 December 2023 (74933)

Is this additonal nosie at low frequency due to the same non-stationarity we oberved before and we believe is related to the ESD upconversion? Probably not, here's why.

First plot compares the strain spectrum from two times with cold and hot OM2. This confirms Sheila's observation.

The second and third plots are spectrograms of GDS-CALIB_STRAIN during the two periods. Both show non-stationry noise at low frequency. The third plot shows the strain spectrogram normalized to the median of the hot OM2 data: beside the non-stationariity, it looks like the background noise is higher below 30 Hz.

This is confirmed by looking at the BLRMS in the 16-60 Hz region for the two times, as shown in the fourth plot: its higher with cold OM2

Finally, the last plot shows the correlation between the ESD RMS and the strain BLRMS, normalized to the hot OM2 state. There is still a correlation, but it appear again that the cold OM2 state has an additional background noise: when the ESD RMS is att the lower end, the strain BLRMS setlles to higher values

Images attached to this comment
sheila.dwyer@LIGO.ORG - 15:57, Wednesday 20 December 2023 (74949)

Here is the same comparison, without squeezing.  Using times from  74935 and 74834

This suggests that where cold OM2 seems better than hot OM2 above that is due to the squeezing (and the jitter subtraction Jenne added, which is also on in this plot for cold OM2 but not for hot OM2).  And the additional noise with cold OM2 reaches up to about 45Hz. 

 

Images attached to this comment
naoki.aritomi@LIGO.ORG - 14:16, Friday 22 December 2023 (74997)SQZ

After we optimized ADF demod phase in 74972, the BNS range seems better and consistently 160-165Mpc. The attached plot shows the comparison of OM2 cold/hot with/without SQZ. The OM2 cold with SQZ is measured after optimization of ADF demod phase and other measurements are same as Sheila's previous plots.

This plot supports what Sheila says in the previous alogs.

  • The OM2 cold is worse below 40 Hz for both SQZ/no SQZ.  
  • Without SQZ, OM2 cold and hot are almost the same above 40 Hz.
  • With SQZ, OM2 cold is better between 100-600 Hz, but worse above 1 kHz. This difference could be due to SQZ and we could try to optimize SQZ around 100 Hz with OM2 hot
Images attached to this comment
victoriaa.xu@LIGO.ORG - 18:12, Thursday 04 January 2024 (75181)SQZ

Echo-ing the above, and summarizing a look at OM2 with sqz in both Sept 2023 and Dec 2023 (running gps times dictionary is attached here).

If we compare the effect of squeezing -- there is higher kHz squeezing efficiency with hot OM2. We can look at either just the darm residuals dB[sqz/unsqz] (top), or do subtraction of non-quantum noise (bottom) which shows that hot OM2 improved the kHz squeezing level by ~0.5 dB at 1.7 kHz (the blue sqz blrms 5). This is consistent with summary pages: SQZ has not reached 4.5 dB since cooling OM2 74861. Possibly suggests better SQZ-OMC mode-matching with hot OM2.

Without squeezing, cold om2 has more optical gain and more low-freq non-quantum noise. Better IFO-OMC mode-matching with cold OM2.

In total, it's almost a wash for kHz sensitivity: heating OM2 loses a few % optical gain, but recovers 0.2-0.5 dB of shot noise squeezing. 

It's worth noting the consistent range increases with SQZ tuning + improvements: even in FDS, there is a non-zero contribution of quantum noise down to almost 50 Hz. For example Naoki's adjustment of sqz angle setpoint on 12/21 74972 improved range, same for Camilla's Jan sqz tuning 75151. Looking at DARM (bottom green/purple traces), these sqz angle tunings reproducibly improved quantum noise between about 60-450 Hz.

Images attached to this comment
Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 11:20, Monday 08 January 2024 (75195)

Here are some more plots of the times that Vicky plotted above. 

The first attachment is just a DARM comparison with all 4 no sqz times, OM2 cold vs hot in December vs September. 

Comparing OM2 hot September vs December shows that our sensitivity at from 20-40 Hz has gotten worse since September, the MICH coherence seems lower while the jitter and SRCL coherence seem similar.  The same comparison for OM2 cold shows that with OM2 cold our sensitivity has also gotten worse from 15-30 Hz. 

Comparing cold vs hot, in September the MICH coherence did get worse from 60-80 Hz for cold OM2, which might explain the worse sensitivity in that region.  The MICH coherence got better from 20-30 Hz where the sensitivty was better for cold OM2.  The December test had better tuned MICH FF for both hot and cold OM2, so this is the better test of the impact of the curvature change. 

As Gabriele pointed out with his BRUCO, 74886 there is extra coherence with DHARD Y for cold OM2 at the right frequencies to help explain the extra noise.  There isn't much change in the HARD pitch coherence between these December times, but the last attachment here shows a comparison of the HARD Y coherences for hot and cold OM2 in December. 

 

 

Images attached to this comment
sheila.dwyer@LIGO.ORG - 10:23, Wednesday 10 January 2024 (75298)

Peter asked if the difference in coherence with the HARD Yaw ASC was due to a change in the coupling or the control signal. 

Here is a comparison of the control signals with OM2 hot and cold, they look very similar at the frequencies of the coherence.

Images attached to this comment
Displaying reports 11561-11580 of 84672.Go to page Start 575 576 577 578 579 580 581 582 583 End