LSC Algorithm Library
Project Librarian
Jolien Creighton. Email: jolien at gravity.phys.uwm.edu
README Files
The first file you should read is the LAL README file. This contains instructions on checking LAL out of CVS, obtaining a distribution and getting install instructions.
The other README files are:
- Instructions for reporting bugs can be found in the file README.bugs
- Instructions for building LAL can be found in the file README.install but see the How to install LAL and LALApps software for complete instructions.
- Instructions for contributors to LAL can be found in the file README.contrib
- Instructions on obtaining a python wrapping of parts of LAL (PyLAL) can be found in the PyLAL README.
Documentation
The LAL Software Documentation (LSD) is the original LAL documentation. Newer functions are documented using doxygen. Unfortunately, not all of the original documentation has been moved over to doxygen yet.
- Doxygenated LAL from nightly build [ HTML ]
- New Doxygenated LAL from nightly build (testing) [ HTML ]
- Latest LAL Software Documentation from nightly build [ PDF ]
- LAL Software Documentation from release 5.2 [ PDF ]
The "Numerical Algorithms Library Specification and Style Guide" document (commonly known as the LAL Spec) contains the software specifications that code written for LAL should conform to.
- LIGO Scientific Collaboration Algorithm Library Specification and Style Guide (superceeds LIGO-T990030-E) [ PDF ]
Download
The latest development version of the package is available from CVS. See the LAL HOWTO for instructions on retrieving the source.
Released versions of LAL are available from the releases section
below.
CVS Archive
The LAL source is located in the LSCSoft CVS archive. The CVS can be accessed read-only using the anonymous account (no password is needed):
:pserver:anonymous@gravity.phys.uwm.edu:2402/usr/local/cvs/lscsoft
or you may contact the LAL librarian to obtain your own CVS account for read/write access. See How to use the LSCSoft CVS archive for more information.
You may also
browse the LAL CVS archive
using the web interface.
Releases
LAL Version 5.2 released on 23 February 2007 [ lal-5.2.tar.gz ]
Directory of previous releases
Bug Reporting
Before you file a bug, please read through the list of
current and previous bugs
for LAL to determine if your bug has already been
filed. If your bug does not exist,
enter a bug report using the gnats bug entry page.
If your bug exists and has not been fixed, add additional information to the
existing bug. If your bug exists and has been fixed, upgrade to the version in
the bug report to determine if the bug was properly fixed. If it was not,
reopen the bug.
The LAL Bug Report Entry Page contains instructions for using the LAL bug reporting system.
Enter the LAL Bug Report Gnats Database
Nightly Test Build
The nightly test build page provides information about the status of the code in CVS and how well it builds on a variety of platforms.
Mailing Lists
- lal-announce General LAL announcements including releases
- lal-discuss Discussions of modifying/using LAL
Links
Links to required and optional software used by LAL.
- Source code of required software and instructions to install software from source.
- Repositories containing required software binaries.
Links to homepages of software relevant to LAL.
- GSL - The GNU Scientific Library Home Page
- FFTW Home Page
- LAM Home Page
- MPICH Home Page
- FrameL Home Page
Development
LAL developers should subscribe to the lal-discuss mail list.
Development directions:XLALification
LAL functions are slowly being replaced with XLAL functions.Strategy: New functions should be XLAL functions. Whenever possible, an old LAL function should be replaced with a XLAL function. To do this, take the code from the LAL function, massage it into an XLAL function, and then have the LAL function call the XLAL function. Programs calling the LAL function can then be changed to use the XLAL functions.
Doxygenation
The old LAL Software Documentation, generated by laldoc, is being replaced with doxygen-generated documentation.Strategy: As new XLAL functions are written, they should be documented using doxygen. As LAL functions are replaced by XLAL functions, the documentation should be converted to doxygen. At some point someone will have to sit down and do a large-scale conversion.
Separate Libraries
LAL currently is a package that produces several libraries: liblal, liblalsupport, liblalmetaio, liblalframe. The library liblal should not depend on any of the others; liblalsupport, liblalmetaio, and liblalframe can depend on liblal but not on each other.Goal: Package the libraries separately to make this division explicit. Perhaps also have separate libraries for each search group: liblalburst, liblalinspiral, liblalpulsar, liblalstochastic.
Contributors
Allen, B.
Anderson, W. G.
Ausmus, D.
Balasubramanian, R
Berukoff, S. J.
Bose, S.
Brady, P. R.
Brown, D. A.
Cameron, P. B.
Cannon, K. C.
Casquette, M.
Charlton, P. R.
Chassande-Mottin, E.
Chin, D.
Churches, D. K.
Cokelaer, T.
Creighton, J. D. E.
Creighton, T. D.
Cutler, C. J.
Daw, E. J.
Diaz, M. C.
Dietz, A.
Drasco, S.
Dupuis, R. J.
Dwyer, S. J.
Edlund, J.
Essinger-Hileman, T.
Fairhurst, S.
Finn, L. S.
Flanagan, E. E.
Hanna, C. R.
Itoh, Y.
Jones, D. I.
Jones, G.
Khurana, D.
Klimenko, S.
Krishnan, B.
Trejo, R.
Machenschalk, B.
McKechan, D. J. A.
Mendell, G. A.
Mercer, A.
Messaritaki, E.
Messenger, C. J.
Mohanty, S. D.
Noel, J.
Owen, B. J.
Papa, M. A.
Prix, R.
Rakhmanov, M.
Ray Majumder, S.
Read, J. S.
Regimbau, T.
Romano, J. D.
Santamaria, L.
Sathyaprakash, B. S.
Seader, S. E.
Sengupta, A.
Siemens, X.
Sintes, A. M.
Sorensen, S.
Sylvestre, J.
Tibbits, M. M.
Torres, C. W.
Vallisneri, M.
Whelan, J. T.
Whitbeck, D. M.
Williamsen, M. S.
Wiseman, A. G.
Woods, D.
Yakushin, I.