Composite coupling functions can be produced directly after producing coupling functions via pemcoupling:

pemcoupling config.ini ACC -I injections.txt --composite

or from pre-existing coupling functions using the stand-alone pemcoupling-composite command:

pemcoupling-composite config.ini ACC

By default pemcoupling-composite searches the existing directory for subdirectories containing coupling functions. Results are saved to another subdirectory, name given by the composite_dir option in config.ini.

See Specifying channels for instructions on using a custom channel or channel list, or searching for channel string patterns.

Full command-line help menu

Traceback (most recent call last):
  File "/home/docs/checkouts/", line 4, in <module>
    __import__('pkg_resources').run_script('pemcoupling==0.0.11.dev2', 'pemcoupling-composite')
  File "/home/docs/checkouts/", line 666, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/home/docs/checkouts/", line 1469, in run_script
    exec(script_code, namespace, namespace)
  File "/home/docs/checkouts/", line 7, in <module>
  File "build/bdist.linux-x86_64/egg/pemcoupling/", line 10, in <module>
  File "build/bdist.linux-x86_64/egg/pemcoupling/", line 14, in <module>
  File "build/bdist.linux-x86_64/egg/pemcoupling/", line 6, in <module>
  File "/home/docs/checkouts/", line 22, in <module>
    from .core import (TimeSeriesBase, TimeSeriesBaseDict, TimeSeriesBaseList)
  File "/home/docs/checkouts/", line 54, in <module>
    from gwosc.api import DEFAULT_URL as GWOSC_DEFAULT_HOST
  File "/home/docs/checkouts/", line 29, in <module>
    from urllib.request import urlopen
ImportError: No module named request