Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
B
bilby_pipe
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
lscsoft
bilby_pipe
Commits
17785966
Commit
17785966
authored
2 years ago
by
Gregory Ashton
Browse files
Options
Downloads
Plain Diff
Merge branch '245-problems-running-bilby_pipe-with-custom-waveform-model' into 'master'
Resolve "Problems running bilby_pipe with custom waveform model" Closes
#245
See merge request
!466
parents
8fc29537
2ed72a5f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!466
Resolve "Problems running bilby_pipe with custom waveform model"
Pipeline
#443776
canceled
2 years ago
Stage: initial
Stage: test
Stage: docs
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/customisation.rst
+2
-1
2 additions, 1 deletion
docs/customisation.rst
with
2 additions
and
1 deletion
docs/customisation.rst
+
2
−
1
View file @
17785966
...
...
@@ -12,7 +12,8 @@ and source model from some external package the following should be included in
frequency-domain-source-model = my_package.submodule.custom_source_model
In order to be compatible with the :code:`bilby_pipe` analysis scripts, custom classes should take the same arguments
as their parent classes.
as their parent classes. If you do not want to hard code all such arguments, you can use :code:`**kwargs` to capture
(and ignore) additional arguments.
An exception to this is when passing custom likelihood classes.
In this case additional keyword arguments can be passed through the ini file, as below
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment