-
Notifications
You must be signed in to change notification settings - Fork 7
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
Minor changes from big branch grd-failure #173
Conversation
* Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]>
* Do not cross metric day boundaries. * add log file arg delete empty directories when done * Tweak remove empty dir removal * Tweak remove empty dir removal again * Merge day boundary (gwpy#146) * Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]> * rebase agaist last approved PR * rebase against last approved PR * rebase against last approved PR again, fix flake8 * Fix a bug in remove empty directories. Co-authored-by: Joseph Areeda <[email protected]>
* Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]>
* Do not cross metric day boundaries. * Merge day boundary (gwpy#146) * Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]> * Check point merge (gwpy#147) * Do not cross metric day boundaries. * add log file arg delete empty directories when done * Tweak remove empty dir removal * Tweak remove empty dir removal again * Merge day boundary (gwpy#146) * Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]> * rebase agaist last approved PR * rebase against last approved PR * rebase against last approved PR again, fix flake8 * Fix a bug in remove empty directories. Co-authored-by: Joseph Areeda <[email protected]> * Merge day boundary (gwpy#146) * Address issue gwpy#126. Allow pyomicron to run from a frame cache without accessing dqsegdb. Add documentation for this * Do not merge files if they overlap "metric days" * Do not cross metric day boundaries. Co-authored-by: Joseph Areeda <[email protected]> * minor doc changes * Fix a bug where an xml.gz file could get compressed again in merge-with-gaps * Implement a periodic vacate to address permanent D-state (uninterupptible wait) causing jobs to fail to complete * Always create a log file. If not specified put one in the output directory * Fix a problem with periodic vacate. * Up the periodic vacate time to 3 hrs * Found a job killing typo * Add time limits to post processing also * Don't save segments.txt file if no sgments founds because we don't know if it's an issue of not finding them or a valid not analyzable state. * disable periodic vacate to demo the problem. * Fix reported version in some utilities. Only update segments.txt if omicron is actually run. * Clarify relative imports. and add details to a few log messages * Resolve flake8 issues --------- Co-authored-by: Joseph Areeda <[email protected]>
tweak logging to better underst guardian channel usage-
@areeda, I only see logging changes, and not anything related to concurrency or look back. Are there commits missing? |
…on segfaults if environment variable not set
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #173 +/- ##
==========================================
- Coverage 35.15% 33.97% -1.18%
==========================================
Files 30 30
Lines 2942 2938 -4
==========================================
- Hits 1034 998 -36
- Misses 1908 1940 +32
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Oops looks like the changes at line 744 in process have been previously merged |
omicron/parameters.py
Outdated
@@ -65,7 +65,7 @@ def __init__(self, version=None, defaults=dict(), **kwargs): | |||
if version is None: | |||
try: | |||
version = utils.get_omicron_version() | |||
except KeyError: | |||
except (KeyError, RuntimeError): |
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.
The get_omicron_version
function, as far as I can tell, cannot raise a KeyError
under any circumstances, so this should be a replacement rather than an append:
except (KeyError, RuntimeError): | |
except RuntimeError: |
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.
However, I'm not sure that we should be skipping this sort of error anyway.
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.
When omicron version
segfaults subprocess produces a runtime error.
Other omicron functions work.
# I disabled this test because the Omicron pfogram segfaults when | ||
# it is run from pytest | ||
# cp = ConfigParser() | ||
# section = 'test' | ||
# cp.add_section(section) | ||
# cp.set(section, 'channels', 'X1:TEST-CHANNEL\nX1:TEST-CHANNEL_2') | ||
# cp.set(section, 'flow', '10') | ||
# cp.set(section, 'fhigh', '100') | ||
# with tempfile.NamedTemporaryFile(suffix='.ini', mode='w') as f: | ||
# cp.write(f) | ||
# pars = OmicronParameters.from_channel_list_config(cp, section) | ||
# assert pars.getlist('DATA', 'CHANNELS') == ['X1:TEST-CHANNEL', | ||
# 'X1:TEST-CHANNEL_2'] | ||
# assert tuple(pars.getfloats('PARAMETER', 'FREQUENCYRANGE')) == (10., 100.) | ||
pass |
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.
Can you raise an issue about this, it really shouldn't be segfaulting under any circumstances.
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.
https://git.ligo.org/virgo/virgoapp/Omicron/-/issues/81 opened a while ago
We had a short discussion ib the Mattermost Omicron channel
This change inclued in other MR |
This PR :
With previously merged PRs we should be compatible with the latest dqsegdb2 release.