-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
attempt to simplify and reduce memory for multiringbuffer #2523
Conversation
This is being tested. |
I immediately got this:
|
Can we just rename |
I've renamed it so it isn't len either, as it really was something else. It was supposed to be the number of time steps that have been added to the buffer. This maxes out at the max buffer size, but before this we need to know how many have been taken to correctly know the total background time. |
New error:
Apparently |
@ahnitz after the commits I just did, the analysis is running without errors. Could you double check that I did not mess anything up? |
@titodalcanton Nothing glaringly obvious at least. |
After several hours of running, the memory usage appears still limited to several Gb. Yay! |
@ahnitz is this still a work in progress or just needs to be tested? Is the result expected to be identical to the previous version? If so, that is an easy test. |
It just needs to be tested. Results should be identical.
…On Fri, Mar 1, 2019, 18:32 Tito Dal Canton ***@***.***> wrote:
@ahnitz <https://github.com/ahnitz> is this still a work in progress or
just needs to be tested? Is the result expected to be identical to the
previous version? If so, that is an easy test.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2523 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACGrRrqkGcU5bpr3mgIyM6xTmCpdgv39ks5vSWRKgaJpZM4bTSs3>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and tests are underway.
After running on my fake frames with injections, the exact same set of HDF and coinc XML files is generated, with identical file names, with respect to a run done with v1.13.4. However, I compared a few coinc XML files in detail and they are not identical. Most of the differences are tiny changes in the SNR time series and PSDs, which look like numerical rounding in the least significant digits. I was a bit surprised to see even such a tiny difference, but whatever. However in one case ( |
Hmmm.. hard to say. One issue is that pycbc live can be less numerically
stable or long running than a standard analysis. This is because it makes
choices to redo or reuse parts of the analysis (like the psd) depending on
ift it's changes sufficiently. This can mean that a different PSD could be
used for a stretch of data. One way to reduce this (for testing only) would
be to force it to always recalculate the psd, i.e. set the threshold very
low or to zero.
…On Sat, Mar 2, 2019 at 5:00 AM Tito Dal Canton ***@***.***> wrote:
After running on my fake frames with injections, the exact same set of HDF
and coinc XML files is generated, with identical file names, with respect
to a run done with v1.13.4. However, I compared a few coinc XML files in
detail and they are not identical.
Most of the differences are tiny changes in the SNR time series and PSDs,
which look like numerical rounding in the least significant digits. I was a
bit surprised to see even such a tiny difference, but whatever.
However in one case (coinc-1169265807.xml.gz for self reference) the
coinc_inspiral:combined_far value went from 3.491173665171772e-05 to
0.0001112754634923875. The coinc_inspiral:snr is equal to 6 significant
digits. I do not remember seeing this field change in a couple other coinc
files. What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2523 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACGrRvtTOqg9ol-4SK4-agBMsC4C9tN5ks5vSfdfgaJpZM4bTSs3>
.
--
Dr. Alexander Nitz
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Callinstrasse 38
D-30167 Hannover, Germany
Tel: +49 511 762-17097
|
@titodalcanton Yeah that's disconcerting. I think what I'll do is put together a test script with these two version and feed them random numbers to see what happens. One of them must have a bug, I think. |
@titodalcanton Based on my test (see pycbc chat for more details) I think this is the right implementation and fixes a bug in the current version that is hit when the buffer resizes. My suggestion is that we merge this patch. What do you think? |
Ok I think I get what the problem with the old class is. Let's merge and keep testing this, also given how much memory the old approach requires. |
No description provided.