Skip to content
Snippets Groups Projects
Select Git revision
  • improved-heterodyne-fisher
  • BW+QuickCBC
  • master default protected
  • polarization
  • 42-changed-file-names-of-psd-asd-files-used-by-bwp
  • 42-changed-file-names-of-psd-asd-files-used-by-bwp-2
  • revert-78852f8f
  • cleanup-files
  • stable
  • testing
  • O3_dev
  • stochastic
  • PostMergerBursts
  • mics
  • O2_dev
  • O2_online_altpol_skyfix
  • O2_online_vector_modes
  • O2_online_scalar_mode
  • skyfix
  • review
  • v1.0.5
  • v1.0.4
  • v1.0.3
  • v1.0.2
  • v1.0.1
  • v1.0.0
  • O2_cleaning
  • O2_offline
  • O2_online
  • PostMergerBursts
  • bwb-0.1
  • bwb-0.2
  • bwb-0.3
  • bwb-0.4
  • bwb-er7
  • GW170817_CBCgroup_SourceProperties
  • O1_offline
  • O1_online
  • O2
39 results
Compare
Forked from lscsoft / bayeswave
1277 commits behind, 3 commits ahead of the upstream repository.
James Clark's avatar
Merge branch 'stable' into 'stable'
James Clark authored 
Updating container names for publication in CI script

See merge request lscsoft/bayeswave!29
e989dd36
History
James Clark's avatar e989dd36
History
Name Last commit Last update
BayesWaveUtils
doc
etc
src
test
.gitlab-ci.yml
CONTRIBUTING.md
Dockerfile
README.md
install.sh
README.md

BayesWave

Welcome to the BayesWave software repository. This wiki provides instructions for:

Please see the BayesWave wiki for further information

Quick Start

See here for quick start instructions to installing and running a simple GW150914 analysis

Contributing

Procedures for developing and contributing to this repository match those for lalsuite. The contribution guide for lalsuite can be found here

Documentation is most conveniently provided via markdown (.md) files in the repository itself. The page you are now reading is the README.md at the root of the master branch. All other documentation should live in doc.

TLDR

  • We use the fork/merge development model
  • Development projects should take place on feature branches (NOT adhoc sub-directories!)

This eliminates conflicts, ensures the master branch is always useable (no one breaks the build etc) and means different features/branches are easily found, used and contributed to.

So:

  1. create your own fork of this repository
  2. create a branch to develop some feature on the fork
  3. make and commit changes
  4. push that branch upstream
  5. when development is complete, merge that branch's changes back into master

Full details of how to do this can be found in the lalsuite contribution guide

This is, first and foremost, a source repository. To reduce bloat and simplify development, data products and analysis-specific scripts/configuration files should really be hosted in separate repositories or archives which document those analyses.

Repository Structure

This repository has been cloned from the original svn repository at https://svn.ligo.caltech.edu/svn/bayeswave. Commit history, branches and tags have been preserved and non-source directories have been excised from the history. Some details of the svn->git transition can be found here.

The git master branch looks like:

  • src: The main source directory. Includes all C code, header files and build tools
  • test: Test scripts to check successful compilation and linking.
  • utils: Python and bash utility scripts.
  • postprocess: Python and bash post-processing (e.g., plots, webpages) scripts
  • BayesWavePipe: A standalone python module for HTCondor workflow generation

Note that different branches in the original svn do not share a uniform structure; if you cannot find the directory or file you're looking for, check you're on the correct branch.