Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Calibration #2268

Closed
wants to merge 2 commits into from
Closed

Update Calibration #2268

wants to merge 2 commits into from

Conversation

ColmTalbot
Copy link

@cdcapano @ahnitz this PR is adding the calibration functionality previously introduced to gwin (gwastro/gwin#63).

This is basically a cut and paste from the code I added there.

I renamed the existing Recalibrate class to PhysicalModel to keep Recalibrate available for the base class.

If/when this is merged I'll open a PR in gwin to update the calibration functionality there to use this.

@duncan-brown
Copy link
Contributor

@ColmTalbot @dfinstad we might want to take this opportunity to rename "physical model" as that's rather generic. How about TimeDomainCalFactors since it really adjusts those?

@@ -0,0 +1,80 @@
import pytest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One issue here, is that we've been using the unittest module and not pytest for unit tests. This would pull in another build dependency. @ColmTalbot Any chance this can be converted to unittest, or a good reason we should move to pytest instead?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise, I think this is ready to go.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ahnitz We've been using pytest in gwin... @duncanmmacleod decided to use pytest instead of unittest, I think because it has some better features. Since @ColmTalbot originally wrote this in gwin, the tests he wrote were in pytest. Would it be so bad to support both?

@ahnitz
Copy link
Member

ahnitz commented Aug 3, 2018 via email

@ahnitz ahnitz mentioned this pull request Oct 19, 2018
@ahnitz
Copy link
Member

ahnitz commented Oct 19, 2018

@ColmTalbot This should be superseded now by #2393. I've gone ahead an updated the unit tests to use the unit test module. Thanks so much for adding this.

@ahnitz ahnitz closed this Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants