Building on , I added a copper cold finger to conductively cool the inner shield, instead of holding the inner shield fixed at 77K. The cold finger draws cooling power from a cyro cooler or "cold bath" held at 60K, for simplicity. I added an outer shield and set its temperature to 100K. The outer shield supplies some radiative heating to the inner shield, but blocks out 295K heating, which is what we want. The expanded diagram can be seen in Attachment 1.
I wanted to find the optimal choice of inner shield area (AIS) to maximize the radiative cooling to the test mass. I chose 5 values for AIS (from ATM to AOS) and plotted the test mass cooldown for each in Attachment 2. The radiative coupling between the inner shield and test mass is maximized when the ratio of the areas, ATM/AIS, is minimized. Therefore, the larger AIS, the colder the test mass can be cooled. Even though choosing AIS close to AOS increases the coupling between the 2 shields, the resulting heating from the outer shield is negligible compared to the enhancement in cooling.
I chose AIS = 0.22 m2 to model the inner shield and test mass cooldown in Attachment 3. The test mass reaches 123 K at ~ 125 hours, or a little over 5 days. I have pushed the updated script which can be found under mariner40/CryoEngineering/MarinerCooldownEstimation.ipynb.
I used the same model in  to consider how test mass length affects the cooldown. Attachment 1 plots the curves for TM length=100mm and 150mm. The coupling between the test mass and inner shield is proportional to the area of the test mass, and therefore increases with increasing length. Choosing l=100mm (compared to 150mm) thus reduces the radiative cooling of the test mass. The cooldown time to 123K is ~125 hrs or over 5 days for TM length=150mm (unchanged from ), but choosing TM length=100m increases this time to ~170 hrs or ~7 days. (Note that these times/curves are derived from choosing an arbitrary inner shield area of 0.22 m2, but the relative times should stay roughly consistent with different IS area choices.)
I reran the cooldown model, setting the emissivity of the inner surface of the inner shield to 0.7 (coating), and the emissivity of the outer surface to 0.03 (polished Al). Previously, the value for both surfaces was set to 0.3 (rough aluminum).
Attachment 1: TM cooldown, varying area of the inner shield. Now, the marginal improvement in cooldown once the IS area reaches 0.22 m2 is negligible. Cooldown time to 123K is ~100 hrs, just over 4 days. I've kept IS area set to 0.22 m2 moving forward.
Attachment 2: TM/IS cooldown, considering 2 lengths for the test mass. Choosing l=100m instead of 150mm increases cooldown time from ~100 hrs to ~145 hrs, or 6 days.
Here I describe the current radiative cooldown model for a Mariner test mass, using parameters from the most recent CAD model. A diagram of all conductive and radiative links can be seen in Attachment 1. Below are some distilled key points:
All parameters have been taken from CAD, with the exception of:
Attachment 2 contains the cooldown curves for the system components. With the above assumptions, the test mass takes ~59hrs to reach 123K, and the final steady-state temperature is 96K. (*This was edited - found a bug in previous iteration of code that underestimated the TM cooldown time constant and incorrectly concluded ~36hrs to reach 123K. The figures have been updated accordingly.)
Attachment 3-6 are power budgets for major components: TM, IS, Cage, OS (can produce for UM if there's interest). For each, the top plot shows the total heating and cooling power delivered to the component, and the bottom plot separates the heating into individual heat loads. I'll discuss these below:
The next post will describe optimization of the snout length/radius for cooldown.
Here is a more detailed analysis of varying the length and radius of the snout.
Attachment 1 plots the heat load (W) from the snout opening as a function of temperature, for different combinations of snout length and radius. The model using the CAD snout parameters (length=0.67m end-to-end; radius=5.08cm) results in ~0.3W of heat load at steady state. The plot shows that the largest marginal reduction in heat load is achieved by doubling the length of the snout (green curve), which cuts the heat load by over a factor of 2/3. This validates the choice in snout length used in the previous ELOG entry analysis. The bottom line is that the end-to-end snout length should be on the order of 1 meter, if physically possible.
The next marginal improvement comes from reducing the radius of the snout. Attachment 1 considers reducing the radius by a half in addition to doubling the length (red curve). A snout radius of an inch is quite small and might not be feasible within system constraints, but it would reduce the snout heat load to only 25mW at steady state (along with length doubling).
The cooldown model resulting from optimizing parameters of the snout (length=1.33m, radius=2.54cm) is shown in Attachment 2. The test mass reaches 123K in ~57hrs - only 2 hours faster than the case where only the snout length is doubled (see previous ELOG entry) - and the test mass reaches steady state at 92K - only 6K colder than in the previous case. This could discourage efforts to reduce the radius of the snout at all, since increasing the length provides the most marginal gains.
The attached plot (upper) compares the heat load delivered to the test mass from various snout lengths (end to end), as a function of test mass temperature. (At steady state, our point of interest is 123K.) Note that these curves use the original CAD snout radius of 5.08cm (2").
The greatest marginal reduction in heat load comes from increasing the end-to-end snout length to 1m, as concluded in the prevous ELOG. This drops the heat load from just under 0.5W (from snout length 0.5m) to 0.15W. Further increase in snout length to 1.5m drops the heat load to well under 0.1W. After this point, we get diminishing marginal benefit for increase in snout length.
The effect on the TM cooldown curve can be seen in the lower plot. A snout length of 1m drops the steady-state TM temperature to under 100K. Then, like above, increasing the length to 1.5m makes the next non-negligible impact.
Attached is a cartoon partial view into the heat load experienced by the Mariner assembly.
The omnigraffle file with more explicit arrow labelling in the 'layers' tab is available here. The dashed red lines along to top represent vacuum chamber radiation incident on all sides of the OS/IS, not just from the top. Off picture to the right is the BS, left is the beam tube/ETM chamber -- hence the lower absored laser power (solid line) absorbtion (PR power + no HR coating absorption).
Missing or wrong
I am getting started on building the arduino circuit as well as setting up my computer so I can communicate between jupyter notebook and the arduino. I will need a USB adapter for my computer before I can make much more progress.
I was able to get a USB adapter for my computer so I could test my code. The Arduino can read the temperature of the room and output the values with a tenth of a second time delay. Jupyter Notebook recognizes the Arduino and can receive temperature data from it.
Ongoing points of updates/content (list to be maintained and added)
Mariner Chat Channel
Mariner Git Repository
Mariner 40m Timeline [2020-2021] Google Spreadsheet
6" vs 4" optic size comparison using CAD - worth hopping into the 3D geometry using the link below, but also posting a couple of images below.
1) We can adjust all parameters relating to the suspension frame except the beam height. Is there enough clearance under the optic for the internal shield?
--> Using the representation of the MOS structure as-is, there is about 1" of clearance between the bottom panel of the first/internal shield under the 6" case, compared with 2" of clearance in the 4" case. This is not very scary, and suggests that we could use a 6" optic size.
2) Any other concerns at this point?
--> Not really, there are degrees of freedom to absorb other issues that arise from the simple 4" --> 6" parameter shift
EASM posted at https://caltech.app.box.com/folder/132918404089
Putting together Koji's design work with Stephen's CAD, we consider the size of a test chamber for the Mariner suspension.
Koji's design uses a 6" x 6" Si optic, with an overall height of about 21.5".
Stephen's offsets suggest a true shield footprint of 14" x 14" with an overall height of 24".
With generous clearances on all sides, a test chamber with a rectangular footprint internally of about 38" x 32" with an internal height of 34" would be suitable. This scale seems similar to the Thomas Vacuum Chamber in Downs, and suggests feasibility. It will be interesting to kick off conversations with a fabricator to get a sense for this.
This exercise generated a few questions worth considering; feel welcome to add to this list!
WIP - check layout of 60 cm suspension in chamber at 40m, will report here
WIP - also communicate the
WIP - Stephen to check on new suspension dimensions and fit into 40m chamber
Kind of a silly post, and not very scientific, but we are sticking to it. During our check in today we discussed Mariner suspension frame design concept, and we chose to proceed with MOS-style (4 posts, rectangular footprint).
- We looked at a scaled-up SOS (WIP, lots of things broke, just notice the larger side plates and base - see Attachment 1) and we were not super excited by the aspect ratio of the larger side plates - didn't look super stiff - or the mass of the base.
- We noted that the intermediate mass will need OSEMs, and accommodating those will be easier if there is a larger footprint (as afforded by MOS).
MOS-style it is, moving forward!
Also, Checked In to PDM (see Attachment 2 - filename 40mETMsuspension_small-shields.SLDASM and filepath \llpdmpro\Voyager\mariner 40m cryo upgrade ) the current state of the Mariner suspension concept assembly (using MOS). Other than updating the test mass to the 6" configuration, I didn't do any tidying up, so I'm not perfectly satisfied with the state of the model. This at least puts the assembly in a place where anyone can access and work on it. Progress!
Following our discussion at the Friday JC meeting, I gathered several resources and made a small simulation to show how frequency combs might be generated on platforms other than microcombs or mode-locked lasers.
Indeed, frequency combs generated directly from a mode-locked laser are expensive as they require ultra-broadband operation (emitting few fs pulses) to allow for f-2f interferometry.
Microcombs are a fancy way of generating combs. They are low-power-consuming, chip-scale, have a high repetition rate, and are highly compatible with Silicon technology. While these are huge advantages for industry, they might be disadvantageous for our purpose. Low-power means that the output comb will be weak (on the order of uW of average power). Microscopic/chip-scale means that they suffer from thermal fluctuations. High rep-rate means we will have to worry about tuning our lasers/comb to get beat notes with frequencies smaller than 1GHz.
Alternatively, and this is what companies like Menlo are selling as full-solution frequency combs, we could use much less fancy mode-locked lasers emitting 50fs - 1ps pulses and broaden their spectrum in a highly nonlinear waveguide, either on a chip or a fiber, either in a cavity or linear topologies. This has all the advantages:
1. High-power (typically 100mW)
2. Low rep-rate (typically 100MHz)
3. Relatively cheap
4. "Narrowband" mode-locked lasers are diverse and can come as a fiber laser which offers high stability.
As a proof of concept, I used this generalized Schrodinger equation solver python package to simulate 1d light propagation in a nonlinear waveguide. I simulated pulses coming out of this "pocket" laser (specs in attachment 1) using 50mW average power out of the available 180mW propagating in a 20cm long piece of this highly nonlinear fiber (specs in attachment 2).
The results are shown in attachments 3-4:
Attachment 3 shows the spectrum of the pulse as a function of propagation distance.
Attachment 4 shows the spectrum and the temporal shape of the pulse at the input and output of the fiber.
It can be seen that the spectrum is octave-spanning and reaches 2um at moderate powers.
One important thing to consider in choosing the parameters of the laser and fiber is the coherence of the generated supercontinuum. According to this paper and others, >100fs pulses and/or too much power (100mW average is roughly the limit for 50fs pulses) result in incoherent spectra which is useless in laser locking or 1f-2f interferometry. These limitations apply only when pumping in the anomalous dispersion regime as traditionally have been done. Pumping in an all-normal (but low) dispersion (like in this fiber) can generate coherent spectra even for 1ps pulses according to this paper and others. So even cheaper lasers can be used. ps pulses will require few meter-long fibers though.
I guess you have tried it already - but does enforcing the stacks to be repeating bilayer pairs of the same thickness fail miserably? When doing this for the PR3 optic @1064nm, I found that the performance of a coating in which the layers are repeating bilayers (so only 2 thicknesses + the cap and end are allowed to vary) was not that much worse than the one in which all 38 thicknesses were allowed to vary arbitrarily. Although you are aiming for T=50ppm at the second wavelength (which isn't the harmonic) which is different from the PR3 reqs. This kind of repetitive structure with fewer arbitrary thicknesses may be easier to manufacture (and the optimizer may also converge faster since the dimensionality of the space to be searched is smaller).
Cool starfish 🌟 . What is the interpretation of the area enclosed by the vertices? Is that the (reciprocal) cost? So the better solution maximizes the area enclosed?
How about a diagram so that we can understand what this model includes?
For our optical contacting, Jennifer and I are starting out with glass (microscope slides), with the setup in the EE shop next to the drill press (photos from Jennifer to follow).
Some interesting links:
The Arduino / AC PWM interface looks good. I recommend that you maintain the code in GitHub and post a link to the repo whenever you update the code. Use detailed commit messages so that it makes sense.
For the plotting, it would be good if you can use grid lines and markers for the data points. Then we can see the difference between the data and the fits, etc.
And to avoid the hysteresis, etc. you can record the temperature in your Arduino and use feedback to make the heater just go to whatever temperature you specify. So you would have a prescribed T(t) and the PID feedback loop would just make the heater take you there. Can your Arduino read the thermocouple?