lalsuite merge requestshttps://git.ligo.org/lscsoft/lalsuite/-/merge_requests2024-03-29T04:13:58Zhttps://git.ligo.org/lscsoft/lalsuite/-/merge_requests/2262LALPulsar: pretty-format more C code2024-03-29T04:13:58ZKarl WetteLALPulsar: pretty-format more C code### Description
Pretty-format all C code in LALPulsar _apart from_ the following files, where there is ongoing development:
```
bin/HoughFstat/HierarchicalSearch.c
bin/HoughFstat/HierarchicalSearch.h
bin/HoughFstat/LocalComputeFstatHoug...### Description
Pretty-format all C code in LALPulsar _apart from_ the following files, where there is ongoing development:
```
bin/HoughFstat/HierarchicalSearch.c
bin/HoughFstat/HierarchicalSearch.h
bin/HoughFstat/LocalComputeFstatHoughMap.c
lib/DriveHough.c
lib/HoughMap.c
lib/HoughMap.h
lib/LALHough.h
lib/PHMD.h
lib/Peak2PHMD.c
```
The above files are listed in a file `lalpulsar/.pretty.exclude` which is used to (temporarily) exclude files from pretty-formatting.
### API Changes and Justification
#### Backwards Compatible Changes
- [x] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python class/function definitions
- [ ] This change adds new classes/functions/structs/types
to a public C header file or Python module
#### Backwards Incompatible Changes
- [ ] This change modifies an existing class/function/struct/type definition
in a public C header file or Python module
- [ ] This change removes an existing class/function/struct/type
from a public C header file or Python module
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
#### Review Status
Please provide details on any reviews related to this change and
and the associated reviewers.Karl WetteKarl Wettehttps://git.ligo.org/lscsoft/lalsuite/-/merge_requests/2260lalpulsar_CopyPublicSFTs.py: write a README.md describing the SFT file/direct...2024-03-19T00:34:12ZKarl Wettelalpulsar_CopyPublicSFTs.py: write a README.md describing the SFT file/directory naming scheme### Description
Modify `lalpulsar_CopyPublicSFTs` to write a `README.md` file describing the SFT file/directory naming scheme into the destination directory.
The SFT directory naming scheme generates top-level directories which are a ...### Description
Modify `lalpulsar_CopyPublicSFTs` to write a `README.md` file describing the SFT file/directory naming scheme into the destination directory.
The SFT directory naming scheme generates top-level directories which are a little hard to parse, e.g.:
```
H1_1800SFT_O4RUN+R1+CGDSCALIBSTRAINCLEANGATEDG01+WTKEY5_BROADBAND/...
```
The `README.md` is intended to fully describe the top-level naming scheme, and in addition how the SFTs are named and organised into subdirectories.
### API Changes and Justification
#### Backwards Compatible Changes
- [ ] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python class/function definitions
- [x] This change adds new classes/functions/structs/types
to a public C header file or Python module
#### Backwards Incompatible Changes
- [ ] This change modifies an existing class/function/struct/type definition
in a public C header file or Python module
- [ ] This change removes an existing class/function/struct/type
from a public C header file or Python module
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
#### Review Status
cc @keith-riles @david-keitelKarl WetteKarl Wettehttps://git.ligo.org/lscsoft/lalsuite/-/merge_requests/2165Adding updated LIGO-India (Aundha) coordinates into LAL2023-06-23T10:19:17ZAditya Vijaykumaraditya.vijaykumar@ligo.orgAdding updated LIGO-India (Aundha) coordinates into LAL### Description
Now that the LIGO-India (Aundha) project is approved and the [coordinates are public](https://dcc.ligo.org/LIGO-T2000158), I wanted to implement these in LAL.
### API Changes and Justification
#### Backwards Compatible...### Description
Now that the LIGO-India (Aundha) project is approved and the [coordinates are public](https://dcc.ligo.org/LIGO-T2000158), I wanted to implement these in LAL.
### API Changes and Justification
#### Backwards Compatible Changes
- [ ] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python class/function definitions
- [x] This change adds new classes/functions/structs/types
to a public C header file or Python module
#### Backwards Incompatible Changes
- [x] This change modifies an existing class/function/struct/type definition
in a public C header file or Python module
- [ ] This change removes an existing class/function/struct/type
from a public C header file or Python module
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
- Currently, LIGO India (old coordinates) are implemented in LAL as I1, whereas the new name is supposed to be A1. However A1 is already in use for the (defunct, AFAIK) ALLEGRO detector, and hence there is duplication. What would be the right thing to do in this case? Should I assign a different name to ALLEGRO, or do away with it altogether, or something else entirely?
#### Review Status
Please provide details on any reviews related to this change and
and the associated reviewers.https://git.ligo.org/lscsoft/lalsuite/-/merge_requests/2140Draft: Add TaylorF2Plus and TaylorF2Quasi2023-04-20T09:14:21ZGeraint PrattenDraft: Add TaylorF2Plus and TaylorF2Quasi### Description
This merge implements TaylorF2+ and TaylorF2Quasi, both are improved point-particle baselines for the TaylorF2 model. TaylorF2+ extends TaylorF2 by incorporating higher-order PN terms up to 6PN over a range of 10-1500Hz....### Description
This merge implements TaylorF2+ and TaylorF2Quasi, both are improved point-particle baselines for the TaylorF2 model. TaylorF2+ extends TaylorF2 by incorporating higher-order PN terms up to 6PN over a range of 10-1500Hz. TaylorF2Quasi implements corrections up to 5.5PN based on Taylor expanding the factorised and resummed EOB energy fluxes and taking the SPA.
### API Changes and Justification
#### Backwards Compatible Changes
- [ ] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python class/function definitions
- [x] This change adds new classes/functions/structs/types
to a public C header file or Python module
#### Backwards Incompatible Changes
- [ ] This change modifies an existing class/function/struct/type definition
in a public C header file or Python module
- [ ] This change removes an existing class/function/struct/type
from a public C header file or Python module
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
#### Review Status
Awaiting final review sign-off.https://git.ligo.org/lscsoft/lalsuite/-/merge_requests/2067Draft: Use Sphinx to render LALSuite documentation2023-04-17T15:43:34ZDuncan Macleodduncan.macleod@ligo.orgDraft: Use Sphinx to render LALSuite documentation### Description
This MR implements #618+.
### API Changes and Justification
#### Backwards Compatible Changes
- [x] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python ...### Description
This MR implements #618+.
### API Changes and Justification
#### Backwards Compatible Changes
- [x] This change does not modify any class/function/struct/type definitions
in a public C header file or any Python class/function definitions
- [ ] This change adds new classes/functions/structs/types
to a public C header file or Python module
#### Backwards Incompatible Changes
- [ ] This change modifies an existing class/function/struct/type definition
in a public C header file or Python module
- [ ] This change removes an existing class/function/struct/type
from a public C header file or Python module
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
#### Review Status
Please provide details on any reviews related to this change and
and the associated reviewers.Duncan Macleodduncan.macleod@ligo.orgDuncan Macleodduncan.macleod@ligo.orghttps://git.ligo.org/lscsoft/lalsuite/-/merge_requests/1776Draft: Add EL8 CI pipeline2022-11-22T15:28:14ZDuncan Macleodduncan.macleod@ligo.orgDraft: Add EL8 CI pipeline### Description
LALSuite 7.3 was built for EL8, this MR adds a CI pipeline to formalise those builds in testing.
### API Changes and Justification
#### Backwards Compatible Changes
- [x] This change introduces no API changes
- [ ] Th...### Description
LALSuite 7.3 was built for EL8, this MR adds a CI pipeline to formalise those builds in testing.
### API Changes and Justification
#### Backwards Compatible Changes
- [x] This change introduces no API changes
- [ ] This change adds new API calls
#### Backwards Incompatible Changes
- [ ] This change modifies an existing API
- [ ] This change removes an existing API
If any of the Backwards Incompatible check boxes are ticked please
provide a justification why this change is necessary and why it needs
to be done in a backwards incompatible way.
#### Review Status
Please provide details on any reviews related to this change and
and the associated reviewers.