geco-stat 0.2.4

Diagnostic tools for the advanced LIGO timing distribution system.

# GECo Statistics Reports

[](https://pypi.python.org/pypi/geco-stat)
[](https://pypi.python.org/pypi/geco-stat)
[](http://geco-statistics.readthedocs.org/en/latest/?badge=latest)

| Branch | Integration Tool | Status |
| ------ | ---------------- | ------ |
| Master | Travis CI | [](https://travis-ci.org/stefco/geco_stat) |
| Master | Codeship | [](https://codeship.com/projects/136547) |
| Dev | Travis CI | [](https://travis-ci.org/stefco/geco_stat) |
| Dev | Codeship | [](https://codeship.com/projects/136547) |

## Purpose

`geco_stat` can be used to easily generate histograms, statistics, and
anomaly reports for timing signals generated by LIGO interferometers. It is
meant to simplify the handling of massive amounts of diagnostic data by
providing a simple, organized interface to relevant statistics, easy
progress tracking for large jobs, effortless data visualization, and convenient
ways to combine reports, so that very long timeseries can be efficiently
analyzed in parallel and then recombined into single, monolithic reports
covering entire eras.

## Getting Started

If you just want to use the latest stable version, you can install it with `pip`:

```bash
pip install geco_stat
```

If you are on an environment without root privileges, you can do this by
creating a virtual environment using `virtualenv` in the folder where you
would like to work:

```bash
cd /path/to/working_directory
virtualenv env

# use the virtualenv version of python and pip
source env/bin/activate
pip install geco_stat
```

When finished with your virtual environment, you can exit it by simply running
`deactivate`.

To use the module from this repository for development, run:
```bash
git clone [e-mail]:stefco/geco_stat.git
```

There is a Makefile included for automating most tasks. To get started, run
`make env`, which will configure a virtual environment for development.

You can simply type `make` to see a list of targets for `make` (i.e. commands you
can have `make` execute).

You can run `make test` to run unit and doctests, `make build` to build a
package for upload to PyPI, `make upload` to upload it, `make check` to make
sure everything is set up (and to see whether you are in a virtual environment),
`make html` to generate documentation html files (though they will have a
different theme than those on Read The Docs), `make clean` to delete
autogenerated files, and `make distclean` to delete *all* autogenerated files
and folders (including the `env` directory).