Version Updates ¶
Deprecated modules ¶
Below we list the modules that became deprecated over time:
Package |
Deprecated module |
New module location |
GDAS version |
---|---|---|---|
GWpy v0.1 |
|
|
v0.4.0 |
GWpy v0.1 |
|
|
v0.4.0 |
GWpy v0.1 |
|
|
v0.4.0 |
Trigger map’s reader ¶
In GWpy v0.1 and earlier versions, the
gwpy.table.lsctables
module was originally just a layer on top of the original (and still intact)
glue.ligolw.lsctables
module, and the excess power trigger maps were read using the
gwpy.table.lsctables.SnglBurstTable.read()
function:
from gwpy.table.lsctables import SnglBurstTable
events = SnglBurstTable.read('trigger_results.xml.gz')
In later GWpy versions, the use of
LIGO_LW
table classes in GWpy was removed in favour of the new
EventTable
object, which inherits directly from
astropy.table.Table
. One can now read and plot a trigger file in much the same way as before (
LIGO_LW
files are still supported, just not any extensions to the
glue.ligolw
objects):
from gwpy.table import EventTable
table = EventTable.read('trigger_results.xml.gz', format='ligolw.sngl_burst')
plot = table.plot(xcol, ycol)
plot.show()
Note that in the case of GNOME, we are using LIGO_LW XML files as inputs, we therefore need to specify the format as followed:
format='ligolw.sngl_burst'
Finally, if one wants to plot the time (as in the GPS time of an event), that column is not directly written into the files, and is not interpolated by the reader, so one needs to create it on the fly, as follows:
table.add_column(table['peak_time'] + table['peak_time_ns'] * 1e-9, name='time')