Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
pygwinc
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
gwinc
pygwinc
Commits
20b38c29
Commit
20b38c29
authored
3 years ago
by
Christopher Wipf
Browse files
Options
Downloads
Plain Diff
Merge branch '94-incorrect-results-with-calibrations-in-sub-budgets' into 'master'
Resolve "Incorrect results with calibrations in sub-budgets" Closes
#94
See merge request
!131
parents
638bdfd5
7dc75f96
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!131
Resolve "Incorrect results with calibrations in sub-budgets"
Pipeline
#209727
passed
3 years ago
Stage: dist
Stage: test
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
gwinc/nb.py
+2
-0
2 additions, 0 deletions
gwinc/nb.py
with
2 additions
and
0 deletions
gwinc/nb.py
+
2
−
0
View file @
20b38c29
...
...
@@ -521,6 +521,8 @@ class Budget(Noise):
"""
if
_precomp
is
None
:
_precomp
=
dict
()
# must copy first if using mul-in-place or we clobber other cals
calibration
=
np
.
ones_like
(
self
.
freq
)
*
calibration
for
cal
in
self
.
_noise_cals
[
name
]:
if
_cals
:
calibration
*=
_cals
[
cal
]
...
...
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