Maintenance will be performed on git.ligo.org, containers.ligo.org, and docs.ligo.org on Tuesday 29 April 2025 starting at approximately 9am PDT. It is expected to take around 30 minutes and there will be several periods of downtime throughout the maintenance. We will be switching the authentication mechanism to use the system that we will be using with the new instance, it will still be utilizing the Federation Proxy but the underlying communication method will be changing. From the user perspective this should be the same as it currently is and you should not notice any differences. However there may be issues that we have not anticipated nor encountered during testing. If you have any comments, questions, or concerns please add them to the helpdesk. In addition we will also be installing the latest security update.
1708708.0 gstlalcbc 7/28 22:02 5+09:05:21 R 0 0.0 gstlal_inspiral_ma
1708711.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 7324.2 gstlal_inspiral --
1708712.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 9765.6 gstlal_inspiral --
1708713.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 7324.2 gstlal_inspiral --
1708714.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 9765.6 gstlal_inspiral --
1708715.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 7324.2 gstlal_inspiral --
1708716.0 gstlalcbc 7/28 22:02 5+09:05:06 R 0 9765.6 gstlal_inspiral --
1708717.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 7324.2 gstlal_inspiral --
1708719.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 7324.2 gstlal_inspiral --
1708721.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 7324.2 gstlal_inspiral --
1708722.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 9765.6 gstlal_inspiral --
1708723.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 9765.6 gstlal_inspiral --
1708725.0 gstlalcbc 7/28 22:03 5+09:05:05 R 0 9765.6 gstlal_inspiral --
1708727.0 gstlalcbc 7/28 22:03 5+09:04:40 R 0 9765.6 gstlal_inspiral --
1708729.0 gstlalcbc 7/28 22:03 5+09:04:40 R 0 9765.6 gstlal_inspiral --
1708731.0 gstlalcbc 7/28 22:03 5+09:04:39 R 0 9765.6 gstlal_inspiral --
1708733.0 gstlalcbc 7/28 22:03 5+09:04:39 R 0 9765.6 gstlal_inspiral --
1708735.0 gstlalcbc 7/28 22:03 5+09:04:50 R 0 0.0 lvalert_listen --u
1714098.0 gstlalcbc 7/30 08:27 3+22:41:14 R 0 0.0 gstlal_ll_inspiral
1717602.0 gstlalcbc 7/31 20:43 2+10:24:48 R 0 0.0 gstlal_ll_inspiral
1717610.0 gstlalcbc 7/31 22:02 2+09:06:00 R 0 7324.2 gstlal_inspiral --
1717643.0 gstlalcbc 8/1 03:00 2+04:07:52 R 0 9765.6 gstlal_inspiral --
1717652.0 gstlalcbc 8/1 04:57 2+02:11:08 R 0 9765.6 gstlal_inspiral --
1717653.0 gstlalcbc 8/1 04:58 2+02:09:38 R 0 9765.6 gstlal_inspiral --
1717669.0 gstlalcbc 8/1 07:37 1+23:31:13 R 0 7324.2 gstlal_inspiral --
1717671.0 gstlalcbc 8/1 07:37 1+23:30:28 R 0 9765.6 gstlal_inspiral --
1717820.0 gstlalcbc 8/1 16:08 1+14:59:47 R 0 7324.2 gstlal_inspiral --
1717823.0 gstlalcbc 8/1 16:23 1+14:44:48 R 0 9765.6 gstlal_inspiral --
\section Review Review
\subsection day1 July 29, 2015
In attendance: Chad, Edward Maros, Gareth Tomas, Jolien Creighton, Kent Blackburn, Laleh Sadeghian, Les Wade, Maddie Wade, Sathyaprakash, Sarah Caudill, Tjonnie Li
\subsubsection day1news News
\subsubsection day1actions Actions
...
...
@@ -134,7 +159,7 @@ In attendance: Chad, Edward Maros, Gareth Tomas, Jolien Creighton, Kent Blackbur
- If possible label on the contours on the background plots
- Money plot here looks strange (dominated by priors, insufficient data, ...);
it would be good if release versions can fix this:
it would be good if release versions can fix this:
One issue is that the clustering used in gstlal_inspiral internally in online
running is set by the parameter "thinca-interval", which we usually set to 1
...
...
@@ -145,8 +170,8 @@ approximate the gstlal_inspiral internal clustering well enough. See:
88cebe1656e267fd9d6579db83e4cdfff00c804e. This was not however sufficient to
fix the IFAR plot. I still think that this is simply due to the fact that there
has not been sufficient data to overwhelm the very conservative prior. Lets
see if the situation improves as we go forward.
see if the situation improves as we go forward. For more information on our
KDE see: https://dcc.ligo.org/G1500589
\subsubsection day1completed Completed Actions
...
...
@@ -161,11 +186,15 @@ see if the situation improves as we go forward.
- Use a smoothing kernel with a larger (try 2, 4) scale to smoothen the likelihood and probability plots. This has been investigated and is documented here: https://bugs.ligo.org/redmine/issues/2339
\subsection day2 July 30, 2015
In attendance: Chad, Jolien and Sathya
\subsubsection day2news News
-*Big Dog was detected the night before*
\subsubsection day2actions Actions
- Look at missed close-by injections (there are not many but it is puzzling why ~8 Mpc injections are missed; could be due to injections being on lock-loss boundary but should be investigated).
...
...
@@ -174,5 +203,93 @@ In attendance: Chad, Jolien and Sathya
- The SNR heat plot and the SNR-Chisquare trigger plots do not appear in SIM-DB page; it would be good to have them there too to compare with the Big Dog event and to see if the anatomy of the triggers is similar when there is a loud event.
\subsubsection day2completed Completed Actions
\subsection day3 July 31, 2015
In attendance: Chad, Sathya
from Sathya:
- We discussed the result of applying a kernel that uses a larger scale and you
found that using a uniformly large scale degrades the sensitivity even in
regions where you already have enough triggers to measure the ranking statistic
accurately. Showed how a trigger density-dependent (I think you called
it dynamic) scaling would work and I am happy with the outcome.
- I would like to invite the other reviewers to look the results of applying the two different kernels and see if they are happy. We should review your patch to make sure there is nothing obviously wrong and we can do that when there are at least two reviewers present.
- You also pointed out that the online webpage IFAR plots were actually still "biased" with respect to the prediction (as opposed to what you erroneously showed us yesterday, which seemed to show them to have converged); but it is now less biased than two days ago, hopefully the measured IFAR will converge to the predicted one soon.
\subsubsection day3news News
\subsubsection day3actions Actions
- The only action item is for the BBH group to use your patch for the ranking statistic and rerun to see if the new kernel causes any problem. We both agreed that you would need to test the kernel for a while before pushing the change to O1 release.
- There is an action item also on me to come up with a checklist for us to go through everyday during an online run. I will circulate this before our call tomorrow (BTW when do we meet tomorrow, 10 am Eastern).
\subsubsection day3completed Completed Actions
\subsection day4 August 1, 2015
\subsubsection day4news News
Unfortunately there was a simdb outage causing several injection jobs to fail and currently they are in a flopping state awaiting response from the simdb team. An open question is, should we trap failures such as these?
