Update trigger reading syntax for gwpy>=0.7 #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
requires gwpy>=0.7.0
bumps trigfind version to 0.4.0
duncanmmacleod
force-pushed
the
gwpy-0.7
branch
from
2b41c1e
to
362e735
Compare
useful to have the tablename when writing immediately
- don't support python2.6 - updated python to python3.6 - use pypi:lalsuite to get lal (much faster)
duncanmmacleod
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings
hveto.triggersup-to-date withgwpy>=0.7.0, mainly to use the new formatting for reading event tables fromLIGO_LWfiles. Also I updated the trigfind usage.This PR has the following dependency consequences:
gwpy >= 0.7.0trigfind >= 0.4.0