Changes the A+ test mass RoC's to those of aLIGO: 1934 m for the ITMs and 2245 m for the ETMs.
There was some discussion a year ago in #52 about not updating this, but these are the design values.
Evan Hall (ff98611b) at 27 Mar 22:43
Merge branch 'fix_Aplus_RoCs' into 'master'
... and 1 more commit
Changes the A+ test mass RoC's to those of aLIGO: 1934 m for the ITMs and 2245 m for the ETMs.
There was some discussion a year ago in #52 about not updating this, but these are the design values.
The trace name is now HorizTest mass
instead of HorizTM
, which is especially annoying because of the space. I think that got messed up in !153.
There was some question about references. Galaxy has the measurements https://galaxy.ligo.caltech.edu/optics/ which range from 1934 m to 1940 m for the ITMs and 2236 m to 2246 m for the ETMs. I changed it here to 1940 m for the ITMs and 2245 for the ETMs which is in line with the values commonly used modeling elsewhere, though the exact values for each test mass are often used instead. I don't think it matters that much as long as they're closer than the existing 1970 m for the ITMs and 2192 m for the ETMs.
Is there any reason not to just make this the standard thermoelastic calculation since it's valid at all frequencies? The function name is also a bit of a misnomer in any case.
Adds low frequency formula for thermoelastic noise from 10.1103/PhysRevD.63.082003.
Also fixes a typo in the infrasound label (no change to calculation).
Evan Hall (a938e1df) at 25 Mar 19:38
Merge branch 'acceleration-calibration' into 'master'
... and 4 more commits
Adds nb.Calibration
for calibrating into acceleration or velocity.
Adds nb.Calibration
for calibrating into acceleration or velocity.
And also added unit tests for all the calibrations.
I added the acceleration, velocity, and force calibrations to all of the canonical budgets along with the existing Displacement calibration. So now you can do
budget = gwinc.load_budget("CE2silica", bname="Acceleration")
or
python -m gwinc CE2silica -b Acceleration
and similarly for Velocity, Force, and Displacement.
Adds nb.Calibration
for calibrating into acceleration or velocity.
This may be more of a problem with pypi itself, but the ci to make a new release when a version tag is pushed is broken. See for example
https://git.ligo.org/gwinc/pygwinc/-/jobs/3192368
It looks like the failure has something to do with trying to push a version that already exists on pypi (0.5.1 in the above example, see here) even though it's trying to push 0.5.2 (see line 22 of the log). I tried pushing the tag for 0.5.1 last night, and it failed for the same reason. I tried rerunning the pipeline (there were a few instances last night where pipelines just had to be rerun) and it failed. Thinking that something may have gotten partially pushed somehow, I tried pushing 0.5.2 instead. The last release on pypi is also allegedly only 0.5.0.
I was able to make a new release manually. Unclear exactly what happened. But for future reference, you cannot make a release that has the same contents of any other release even if that release has been deleted and is no longer shown in the pypi history.
Kevin Kuns (f69ed11f) at 04 Mar 22:33
Merge branch 'fix-interactive-mode' into 'master'