Attachment 1: This is a photo of the current X end table optical layout with the beampaths of the various sub-systems overlaid. For the labels, see Attachment #2.
Attachment 2: This is a summary of all the optical components that are currently being used. I've noted some things we may want to change when we effect the swap. The important ones are:
Have I missed anything important?
Attachment #3: I've made a CAD drawing of the proposed new layout and have overlaid the beampath in an amateur way because I couldn't figure OptoCad out - I figure this will suffice for now. I have adopted elements from the current Y-end layout, but have used Anders' mode-matching solution (same lenses, same positions of optics) to make sure we have good Guoy phase separation between the two PZT steering mirrors. Some notes:
Steve says the table is ready - so if we are happy with this layout, we can move forward...
Beam colors: 1064 nm red, 514 nm green and 633 nm yellow.
There should be room for lens in front of the pd at red3 and a mirror for alignment in the new layout.
This picture may help you how to improve the new ETMX 4' x 3' optical layout.
The major changes from the previous layout:
Does any part of this layout need a radical redesign?
I realized I had overlooked an important constraint in the layout, which is that the enclosure will have two supports that occupy some region of the table - these are denoted in blue in v3 of the layout (Attachment #1). I measured the dimensions for these from the existing Y-endtable. The main subsystem this has affected is the IR transmission monitors, but I've been able to move the photodiodes a little to accommodate this constraint.
I've also done the mode-matching calculations explicitly for the proposed new layout (Attachments #2 and #3, code in Attachment #4). While the layout was largely adopted from what Andres posted in this elog, I found that some of the parameters he used in his a la mode code were probably incorrect (e.g. distance between the 750mm lens and the ETM). More critically, I think the Gouy phase for the optimized solution in the same elog is more like 60 degrees. I found that I could get a (calculated) Gouy phase difference between the two PZT mirrors of ~81 degrees by changing the green path slightly, and making the two PZT mirrors Y7 and Y8 (instead of Y7 and Y11, for which the Gouy phase difference is more like 50 degrees). But this way the two steering mirrors are much closer to each other than they were before. Other misc. remarks about the mode matching calculations:
These changes also necessitated minor changes to the transmitted IR beampath and the Oplev system, but these changes are minor. I've also switched the positions of the AUX IR power monitoring PD and the fiber coupler as suggested by Koji. The shutter has also been included.
I'm planning to start removing components from the X endtable tomorrow morning at ~10AM - if anyone thinks I should hold off and do some further checks/planning, let me know before this so that I can do the needful.
There is currently no table at the X end!
We have moved the vast majority of the optics to a temporary storage breadbord, and moved the end table itself to the workbench at the end.
Steve says Transportation is coming at 1PM to put the new table in.
I've begun cleaning the optics that will eventually go back onto the newly installed X-endtable. We decided that First Contact was the way to go (as opposed to methanol drag wiping). Koji demonstrated the application of the (red) First Contact solution onto a 2" mirror - I then proceeded to work on the rest of the optics. We are broadly following the procedure in E1000079 - first one coat of First Contact solution is applied, then a small piece of PEEK is embedded by applying a second layer of solution over it (this will enable us to pull off the First Contact once we are ready - the plan is to do this after roughly placing the optic on the table. As of now, I've finished coating most of the optics that are part of the IR Transmon path - I will continue later in the evening.
The new endtable is almost ready for re-population. Steve just needs to shim the enclosure which will be done tomorrow morning. The game-plan as discussed at the meeting today is to first try and set up the IR Transmon path. This will allow us to verify that the endtable height is such that we can maintain a beam height of 4" everywhere on the table (I suspect we may have to compromise at some poing and do some fine adjustment of 1/4 to 1/2" somewhere though). It will also allow me to define the cavity axis relative to the table, which will be useful to place the green steering optics eventually. Doing this will be challenging though as right now, I can't see any of the arm flashes on the endtable using an IR card. Ideally, we want to somehow lock the X arm and then do the checks mentioned at the endtable, before beginning to put the endtable back together.
Steve has finished installing the enclosure on the new endtable. So Eric and I decided to try and lock the X arm and measure the beam height of the transmitted IR beam relative to the endtable. We initially thought of using POX DC as a the LSC trigger but this did not work as there was no significant change in it when the arm was flashing. Eric then tried misaligning the ITM and using AS110 as a trigger - this worked. We then recompiled the ASS model to take AS110 as an input, and ran the dither alignment. After doing so, I measured the beam height at two points on the new endtable.
So the beam is about 0.7" higher relative to the endtable than we'd like it to be. What do we do about this?
I've also placed two irides extending the cavity axis on the endtable. These should be helpful in aligning the green to the arm eventually.
The new TMC 4' x 3' x4" optical table and enclosure is installed - aligned- leveled.
Atm2, Picture is taken ~42" from the window at 3.75 camera height. The leveled table height is wthin 1/4 at the center of the window.
I think this is close enough to move on with the installation of the optics.
We can raise the loaded table in the future if it is needed.
Atm4, Optical table height to floor 33" at the south west corner
Atm3, Enclosure top cover transmission at 1064 nm, 1mm beam size, power level 157 mW, 0 degree incident angle, T 1.3% Metal shield is required above 100 mW hitting the wall of the enclosure!
Atm5, window to enclosure Kapton seal
X arm resonating after alignment, beam height on ETMX optical table ~4.75"
Over the last couple of days, I've been working on restoring the optical layout on the X-endtable. Some notes about the status as of today:
Lightwave NPRO output power
The output power from the lightwave NPRO is about 210mW (as measured with the calorimeter). This is significantly lower than the value of ~300mW reported in this elog. It may be that the laser crystal temperature has changed compared to that measurement, but the "ADJ" parameter is at 0, both today and in that measurement. The laser has also been on for more than a day now, that should be sufficient time for the crystal to equilibriate to its final operating state? Is such a large change in output power possible just because of a change in laser crystal temperature? Or did the laser really lose ~1/3rd of its output power over the last two months?
Alignment into IR Faraday, and changes to the planned layout
I've set up the layout until steering the beam through the IR faraday. The input power into the IR Faraday is ~210mW. The output power is ~186mW, after optimizing the angle of the HWP. These numbers seem consistent with what I had reported in this elog (although this was for the Innolight NPRO). The alignment looks reasonably good to the eye as well.
I've made one change to the planned layout (latest version here). Y1 is now a 2" 99% reflective for S polarization beam splitter, instead of a 1" HR mirror. I made this change because we want some light from the NPRO to be transmitted through this optic to couple into the fiber eventually, for the IR beat. I measured the transmitted power to be ~1.5mW, which is around what we were coupling into the fiber before, and should suffice now. The Lightwave NPRO datasheet (page 4) suggests that the polarization of the output of the laser is S, and the measured power before and after this optic suggests that it is working as advertised. This means that HWP 1 also has to be moved downstream (to rotate the polarization so as to maximize transmission through the IR faraday). Space constraints meant that I could not mount HWP 1 on the baseplate+3/4" OD post assembly which is what we want where possible on the new table, so for this optic, I used a 1" OD post and a fork. There may be a couple of other optics in the final layout where space constraints dictate we compromise in this way.
I've also installed beam dumps for the rejected light from the Faraday. For now, these are the old beam dumps. They looked reasonably intact. I believe we have a bunch of new beam dumps on hand as well, so these can be swapped out if deemed necessary.
Cleaning of optics
All the optics are being cleaned using first contact before being installed on the table.
As I found out the hard way, it is not a good idea to clean small optics like half-wave plates while in their mounts. The first contact tends to bond to the frame while drying, and doesn't come off cleanly. Koji helped me clean the offending pieces (he used tweezers to manually remove the residual first contact, and then some acetone to clean up any remaining residue). Subsequently, he re-cleaned these optics, again using first contact, but this time being careful not to extend all the way out to the edge of the optic. The idea is to cover as much area as possible with first contact, while staying clear of the edge. This approach worked reasonably well.
The next major step is to achieve optimal alignment into the doubler. I've placed the doubler on the table in it's approximate final position, I wanted to make sure the enclosure support wasn't in the way (it isn't). The cable from the oven won't run all the way to the Thorlabs temperature controller in it's usual place, we need to either extend the cable, or figure out a new place where we can keep the temperature controller.
ETMX optical table is grounded to ETMX chamber through 1 Mohms
The doubling oven temp controller is installed to reach its cable.
Lightwave NPRO information:
Serial Number: 337
Manufactured: December 1998!!
Details of checks performed:
Koji tuned the parameters on the laser controller and we observed the following:
Ericq has begun the characterization of the repaired Innolight. We checked that it outputs 1W of power. We will now have to perform the following measurements:
All of these will have to be done before installing this laser at the endtable.
I believe the consensus as of now is to go ahead with carrying out the above measurements. Meanwhile, we will keep the Lightwave NPRO on and see if there is some miraculous improvement. So the decision as to whether to use the Innolight is deferred for a day or two.
I re-measured the power levels today.
We have ~205mW out of the NPRO, and ~190mW after the Faraday. It doesn't look like the situation is going to improve dramatically. I'm going to work on a revised layout with the Innolight as soon as I've profiled the beam from it, and hopefully, by Monday, we can decide that we are going ahead with using the Innolight.
Summary of work done over the last two days
Immediate next steps:
I've made progress on the new layout up to the doubling oven. After doing the coarse alignment with the diode current to the NPRO at ~1A, I turned it back up to the nominal 2A. I then rotated the HWP before the IR Faraday such that only ~470mW of IR power is going into the doubler (the rest is being dumped on razor beam dumps). After tuning the alignment of the IR into the doubling oven using the steering mirror + 4 axis translation stage on which the doubling oven is mounted, I get ~3.2mW of green after the harmonic separator and a HR mirror for green. The mode looks pretty good to the eye (see attachment #1), and the conversion efficiency is ~1.45%/W - which is somewhat less than the expected 2%/W but in the ballpark. It may be that some fine tweaking of the alignment + polarization while monitoring the green power can improve the situation a little bit (I think it may go up to ~4mW, which would be pretty close to 2%/W conversion efficiency). The harmonic separator also seems to be reflecting quite a bit of green light along with IR (see attachment #2) - so I'm not sure how much of a correction that introduces to the conversion efficiency.
While doing the alignment, I noticed that some amount of IR light is actually transmitted through the HR mirrors. With ~500mW of incident light at ~45 degrees, this transmitted light amounts to ~2mW. Turns out that this is also polarization dependant (see attachment #3) - for S polarized light, as at the first two steering mirrors after the NPRO, there is no transmitted light, while for P-polarized light, which is what we want for the doubling crystal, the amount transmitted is ~0.5%. The point is, I think the measured levels are consistent with the CVI datasheet. We just have to take care find all these stray beams and dump them.
I will try and optimize the amount of green power we can get out of the doubler a little more (but anyway 3mW should still be plenty for ALS). Once I'm happy with that, I will proceed with laying out the optics for mode-matching the green to the arm.
Gautom is progressing with the layout nicely. The X-arm transmission window have not seen cleaning for decades. This should be the time to do it. Here is picture of dirtiness.
It is not that simple... How much effort should we put in it? The hole table with 1W inno laser plus... set up now about ~500 lbs We can pull it off carefully, but it is not risk free.
We should look at our other signal port windows! Gautom's long reach able him to do the first contact cleaning without moving anything. It is great!
Layout as of today. Most of the green path is done. The Green REFL PD + PZT mirrors have not been hooked up to their respective power sources yet (I wonder if it's okay to start laying cables through the feedthroughs on either end of the table already, or if we want to put whatever it is that makes it airtight eventually in first?). A rough power budget has been included (with no harmonic separator just before the window), though some optimization can be done once the table is completely repopulated.
A zoomed-in version of the REFL path.
Some general notes:
I am closing the PSL shutter and the EX laser shutters for the night as I have applied a layer of first contact to the window for cleaning purposes, and we don't want any laser light incident on it. It may be that the window is so dirty that we may need multiple F.C. cleaning rounds, we will see how the window looks tomorrow...
It looks very promising.
The IR Transmon system is almost completely laid out, only the QPD remains to be installed. Some notes:
I feel like once the above are resolved, the next step would be to PDH lock the green to the arm and see what sort of transmission we get on the PSL table. It may be the polarization or just alignment, but for some reason, the transmitted green light from the X arm is showing up at GTRY now (up to 0.5, which is the level we are used to when the Y arm has green locked!). So a rough plan of action:
Using the modulation frequency suggested here, I hooked up the PDH setup at the X-end and succeeded in locking the green to the X arm. I then rotated the HWP after the green Faraday to maximize TRX output, which after a cursory alignment optimization is ~0.2 (I believe we were used to seeing ~0.3 before the end laser went wonky). Obviously much optimization/characterization remains to be done. But for tonight, I am closing the PSL and EX laser shutters and applying first contact to the window once more courtesy more PEEK from Koji's lab in W Bridge. Once this is taken care of, I can install the Oplev tomorrow, and then set about optimizing various things in a systematic way.. MC autolocker has also been disabled...
Side note: for the IR Transmon QPD, we'd like a post that is ~0.75" taller given the difference in beam height from the arm cavity and on the endtable. I will put together a drawing for Steve tomorrow..
After a second round of F.C. application, I think the window is clean enough and there are no residual F.C. pieces anywhere near the central parts of the window (indeed I think we got most of it off). So I am going to go ahead and install the Oplev.
With Steve's help, I installed the Oplev earlier today. I adjusted the positions of the two lenses until I deemed the spot size on the QPD satisfactory by eye. As a quick check, I verified using the DTT template that the UGF is ~5Hz for both pitch and yaw. There is ~300uW of power incident on the QPD (out of ~2mW from the HeNe). In terms of ADC counts, this is ~13,000 counts which is about what we had prior to taking the endtable apart. There are a couple of spots from reflections off the black glass plate in the vacuum chamber, but in general, I think the overall setup is acceptable.
This completes the bulk of the optical layout. The only bits remaining are to couple the IR into the fiber and to install a power monitoring PD. Pictures to follow shortly.
Now that the layout is complete, it remains to optimize various things. My immediate plan is to do the following:
I will also need to upload the layout drawing to reflect the layout finally implemented.
Not directly related:
The ETMx oplev servo is now on. I then wanted to see if I could lock both arms to IR. I've managed to do this successfully - BUT I think there is something wrong with the X arm dither alignment servo. By manually tweaking the alignment sliders on the IFOalign MEDM screen, I can get the IR transmission up to ~0.95. But when I run the dither, it drives the transmission back down to ~0.6, where it plateaus. I will need to investigate further.
GV Edit: There was some confusion while aligning the Oplev input beam as to how the wedge of the ETM is oriented. We believe the wedge is horizontal, but its orientation (i.e. thicker side on the right or left?) was still ambiguous. I've made a roughly-to-scale sketch (attachment #1) of what I think is the correct orientation - which turns out to be in the opposite sense of the schematic pinned up in the office area.. Does this make sense? Is there some schematic/drawing where the wedge orientation is explicitly indicated? My search of the elog/wiki did not yield any..
Today we spent some time looking into the PDH situation at the X end. A summary of our findings.
All seems very fishy. Its not good to put attenuators and filters in nilly-willy.
I suggested in an earlier elog that after the repair of the NPRO, the PZT capacitance may have changed dramatically. This seems unlikely - I measured the PZT capacitance with the BK Precision LCR meter and found it to be 2.62 nF, which is in excellent agreement with the numbers from elogs 3640 and 4354 - but this makes me wonder how the old setup ever worked. If the PZT capacitance were indeed that value, then for the Pomona box design in elog 4354, and assuming the PM at ~216kHz which was the old modulation frequency was ~30rad/V as suggested by the data in this elog, we would have had a modulation depth of 0.75 if the Function Generator were set to output a Signal at 2Vpp (2Vpp * 0.5 * 0.05 * 30rad/V = 1.5rad pp)! Am I missing something here?
Instead of using an attenuator, we could instead change the capacitor in the pomona box from 47pF mica to 5pF mica to realize a modulation depth of ~0.2 at the new modulation frequency of 231.25 kHz. In any case, as elog 4354 suggests, the phase introduced by this high-pass filter is non-zero at the modulation frequency, so we may also want to install an all-pass filter which will allow us to control the demodulation phase. This should be easy enough to implement with an Op27 and passive components we have in hand...
Today we re-installed the fiber coupler on the X-endtable to couple some of the PSL light into a fiber that runs to the PSL table, where it is combined with a similar PSL pickoff to make an IR beat between the EX AUX laser and the PSL. The main motivation behind this was to make the process of finding the green beatnote easier. We used JAMMT (just another mode matching tool) to calculate a two lens solution to couple the light into the collimator - we use a +200mm and -200mm lens, I will upload a more detailed mode matching calculation + plot + picture soon. We wanted to have a beam waist of 350um at the collimator, a number calculated using the following formula from the Thorlabs website:
where d is the diameter of the output beam from the collimator, f is the collimating lens focal length and MFD is 6.6um for the fiber we use.
There is ~26mW of IR light coming through the BS after the EX AUX - after playing around with the 6 axis stage that the coupler is mounted on, Johannes got the IR transmission to the PSL table up to ~11.7mW. The mode matching efficiency of 45% is certainly not stellar, but we were more curious to find a beat and possibly measure the X arm loss so we decided to accept this for now - we could probably improve this by moving the lenses around. We then attenuated the input beam to the fiber by means of an ND filter such that the light incident on the coupler is now ~1.3mW, and the light arriving at the PSL table from the EX laser is ~550uW. Along with the PSL light, after the various couplers, we have ~500uW of light going to the IR beat PD - well below its 2mW threshold.
The IR beat was easily found with the frequency counter setup. However, there was no evidence of a green beat. So we went to the PSL table and did the near-field-far-field alignment onto the beat PD. After doing this, we were able to see a beat - but the amplitude was puny (~-60dBm, we are more used to seeing ~-20dBm on the network analyzer in the control room). Perhaps this can be improved by tweaking the alignment onto the PD while monitoring the RF output with an oscilloscope.
Moreover, the green PDH problems with the X end persist - even though the arm readily locks to a TEM00 mode, it frequently spontaneously drops lock. I twiddled around with the gain on the uPDH box while looking at the error signal while locked on a oscilloscope, but was unable to mitigate the situation. Perhaps the loop shape needs to be measured and that should tell us if the gain is too low or high. But ALS is getting closer to the nominal state...
Johannes is running his loss measurement script on the X arm - but this should be done by ~10pm tonight.
I installed a 10% BS to pick off some of the light going to the IR fiber, and have added a Thorlabs PDA55 PD to the EX table setup. The idea is to be able to monitor the power output of the EX NPRO over long time scales, and also to serve as an additional diagnostic tool for when ALS gets glitchy etc. There is about 0.4mW of IR power incident on the PD (as measured with the Ophir power meter), which translates to ~2500 ADC counts (~1.67V as measured with an Oscilloscope set to high impedance directly at the PD output). The output of the PD is presently going to Ch5 of the same board that receives the OL QPD voltages (which corresponds to ADC channel 28). Previously, I had borrowed the power and signal cables from the High-Gain Transmon PD to monitor this channel, but today I have laid out independent cabling and also restored the Transmon PD to its nominal state.
On the CDS side of things, I edited C1SCX to route the signal from ADC Ch28 to the ALS block. I also edited the ALS_END library part to have an additional input for the power monitor, to keep the naming conventions consistent. I have added a gain in the filter module to calibrate the readout into mW using these numbers. The channel is called C1:ALS-X_POWER_OUT, and is DQed for long-term trending purposes.
The main ALS screen is a bit cluttered so I have added this channel to the ALS overview MEDM screen for now..
1) Goto http://localhost:631/
2) Click on "Add Printer"
3) Choose HP JetDirect
4) Use the correct address (socket://220.127.116.11:9100)
5) Choose HP and the 5550 postscript driver as the options
6) Try to only print useful stuff and not kill too many trees.
We were stymied tonight by a problem which began late this afternoon. The MC would periodically go angularly unstable, breaking lock and tripping the MC2 watchdogs. Suspicion fell naturally upon McWFS.
Eventually I traced the problem to the MC3 SIDE damping, which appeared to not work--it wouldn't actually damp, and the Vmon values did not correspond to the SDSEN outputs. Suspicion fell on the coil driver.
Looking at the LEMO monitors on the MC3 coil driver, with the damping engaged, showed clear bit resolution at the 100mV level, indicating a digital/DAC problem. Rebooting c1sosvme, which acquires all the OSEM sensor signals and actually does the side damping, resolved the issue.
Lies! The problem was not resolved. The plot shows a 2-day trend, with the onset of the problem yesterday clearly visible as well as the ineffectiveness of the soft-reboot done yesterday. So we'll try a hard-reboot.
So, it appears that one doesn't even have to change the Marconi set frequency to alter the phase of the output signal. It appears that other front panel actions (turning external modulations on/off, changing the modulation type) can do it as well. At least that's what I conclude from earlier this morning, when after setting up the f2 Marconi (166MHz) for external AM, the double-demod handoff in the DRMI no longer worked. Luckily this isn't a real problem now that we have the setDDphases and senseDRM scripts.
The real problem is that we are using frequency synthesizers to make the beat signals (133 and 199) instead of mixers. Luckily, the future 40m will not use beat signals (?) or synthesizers.
I ran the armLoss script for both Xarm and Yarm. The results are confidential, pending the completion of Alberto's cavity pole/finesse measurement due to the 'bet' as to what the new losses are after the drag wiping.
If you're the kind of person who likes to look at their Chrismas presents, the log files with the results are in the usual place for this script: /scripts/LSC/loss-ARM-GPStime.log (loss-Y-944865071.log and loss-X-944865946.log)
I checked the situation from my home and the problem was solved.
The main problem was undefined state of the autolocker and the strange undefined switch states, being associated with the bootfest and burtrestore.
- MC UP/DOWN status shows it was up and down. So I ran scripts/MC/mcup and scripts/MC/mcdown. These cleared the MC autolocker status.
- I had a problem handling the FSS. After mcup/mcdown above, I randomly pushed the "enable/disable" buttons and others, and with some reason, it recovered the handling. Actually it acquired the lock autonomously. Kiwamu may have also been working on it at the same time???
- Then, I checked the PSL loop. I disconnected the loop by pushing the "test" button. The DC slider changes the PZT voltage only 0~+24V. This is totally strange and I started pushing the buttons randomly. As soon as I pushed the "BLANK"/"NORMAL" button, the PZT output got back under the control.
- Then I locked the PMC, MZ, and MC as usual.
Alberto: You must be careful as the modulations were restored.
It's been an iffy last few hours here at the 40m. Kiwamu, Koji and I were all sitting at our desks, and the computers / RFM network decided to crash. We brought all of the computers back, but now the RefCav and PMC don't want to lock. I'm a wee bit confused by this. Both Kiwamu and I have given it a shot, and we can each get the ref cav to sit and flash, but we can't catch it. Also, when I bring the PMC slider rail to rail, we see no change in the PMC refl camera. Since c1psl had been finicky coming back the first time, I tried soft rebooting, and then keying the crate again, but the symptoms remained the same. Also, I tried burt restoring to several different times in the last few days, to see if that helped. It didn't. I did notice that MC2 was unhappy, which was a result of the burtrestores setting the MCL filters as if the cavity were locked, so I manually ran mcdown. Also, the MC autolocker script had died, so Kiwamu brought it back to life.
Since we've spent an hour on trying to relock the PSL cavities (the descriptive word I'm going to suggest for us is persistent, not losers), we're giving up in favor of waiting for expert advice in the morning. I suppose there's something obvious that we're missing, but we haven't found it yet......
This is a (sort of) known problem with the EPICS computers: it's generally called the 'sticky slider' problem, but of course it applies to buttons as well. It happens after a reboot, when the MEDM control/readback values don't match the actual applied voltages. The solution (so far) is just to `twiddle' the problematic sliders/button. There's a script somewhere called slider_twiddle that does this, but I don't remember if it has PSL stuff in it. A better solution is probably to have an individual slider twiddle script for each target machine, and add the running of that script to the reboot ritual in the wiki.
Steve showed me how to send an international fax today:
Alberto is visiting us from Australia. He brought some terrific presents. It is going to be very demanding task to wait for the rest of the 40m team
to return from Wales to taste coffee: PNG Peaberry of Wagonga, Monsooned Malabar of Jindebah and Signature Blue Blend of Cosmorex.
We have placed some sweet giant strawberries in the fridge; free for eating for anyone working in the lab today or tomorrow:
Trying to take an image or movie of the ETMY Transmon cam, we got instead this attached image.
I think it is just some scattered green light, but others in the control room think that it is a message from somewhere or someone...
It is not an angel, it is clearly a four leaf clover (also known as "quadrifoglio"). It is very rare, it brings good luck!
Last week Rana and I struggled to figure out how to un-full-screen windows on the Ubuntu workstations that appeared to be stuck in some sort of full screen mode such that the "Titlebar" was not on the screen. Nothing seemed to work. We were in despair.
Well, there is now hope: it appears that this really is a "fullscreen" mode that can be activated by hitting F11. It can therefore easily be undone by hitting F11 again.
The summery pages are working at a slow motion speed. It's response time 12 minutes.