Duncan Macleod
Duncan Macleod
Migrated to https://gitlab.com/gwpy/gwpy/-/merge_requests/1565.
Migrated to https://gitlab.com/gwpy/gwpy/-/merge_requests/1574.
The CI has moved to github actions, which natively supports running in a container, so while this can't be merged as is, the spirit of this PR should be preserved...
@GregoryAshton, can you comment on how disruptive this change would be for, e.g, the Bilby (pipe) workflows? Do other parts of the workflow presume hardcoded `.submit` file extensions?
@jodergrosse, if this change is still useful, please rebase against the updated upstream/master branch to pick up the new CI.
@ibsafa, this project has been revived, so if you're still interested in this change, please rebase your branch against the upstream `master` branch, which should trigger the new CI. Thanks.
> No, if people notice, we may want to add docs on how to re-add `I`, I guess. But I guess we hope that nobody really notices anyway. > >...
@rgommers, thanks for following up. The header block for the [relevant module](https://git.ligo.org/lscsoft/gstlal/-/blob/gstlal-inspiral-1.10.0-v1/gstlal-inspiral/python/_spawaveform.c?ref_type=tags#L1-L25) looks like this: ```c #include /* standard includes */ #include #include #include #include /* LAL Includes */ #include...
> I have one question here: is `miniconda3` the same as `miniforge3`? if they are the same, should we only keep support for `miniconda3`? if they are different, what are...
@humitos the only caveat to your statement comes when users use an `environment.yaml` and _don't_ specify the `channels` key. In that case the install will use whatever channels are configured...