Skip to content
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

Add support for Virgo FFL files #748

Closed
basswinkels opened this issue Apr 30, 2018 · 1 comment
Closed

Add support for Virgo FFL files #748

basswinkels opened this issue Apr 30, 2018 · 1 comment
Assignees

Comments

@basswinkels
Copy link

At Virgo, the way for the end user to find off-line data is by pointing your Matlab/Python/dataDisplay to a "FFL file" (raw.ffl, trend.ffl, ...). This is a pretty basic text format, where every line lists a file name, gps_start and duration. Reading data via an FFL files is built natively into the FrameL library. As far as I know this doesn't work with gwpy yet. It would be good to implement this, to make gwpy work at the Virgo site.

I will later attach some sample ffl file and possibly some small gwf files.

@basswinkels
Copy link
Author

basswinkels commented Apr 30, 2018

Attached the last 10 lines of raw.ffl and trend.ffl (with .txt added for github). Note that in case of trend, there are frames with mixed length.

The files contain 5 columns, which are: gwf_filename, gps_start, duration, unknown, unknown. The last 2 are usually 0, this might be something related to files containing triggers, I will ask.

trend_sample.ffl.txt
raw_sample.ffl.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants