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

DM-30171: Define PTC tests for cp_verify #18

Merged
merged 19 commits into from Aug 5, 2022
Merged

DM-30171: Define PTC tests for cp_verify #18

merged 19 commits into from Aug 5, 2022

Conversation

plazas
Copy link
Contributor

@plazas plazas commented Jul 29, 2022

No description provided.

@plazas plazas requested a review from czwa July 29, 2022 20:48
Copy link
Collaborator

@czwa czwa left a comment

Choose a reason for hiding this comment

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

A few style notes, but I don't think there's any major issues.

@@ -86,15 +96,33 @@ class CpVerifyCalibTask(pipeBase.PipelineTask, pipeBase.CmdLineTask):
ConfigClass = CpVerifyCalibConfig
_DefaultName = 'cpVerifyCalib'

def run(self, inputCalib):
def runQuantum(self, butlerQC, inputRefs, outputRefs):
Copy link
Collaborator

Choose a reason for hiding this comment

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

This runQuantum doesn't do anything that the default wouldn't, so it doesn't need to be here.

@@ -73,7 +73,7 @@ def detectorStatistics(self, inputCalib):

return outputStatistics

def verify(self, calib, statisticsDict):
def verify(self, calib, statisticsDict, **kwargs):
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should match the signature as it is in verifyCalib.py.

if not testBool:
verifyDetStatsFinal[testName] = bool(np.all(list(verifyDetStats[testName])))

return verifyDetStatsFinal, bool(success)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Github is complaining about the cases of the booleans in the VerifyDefect.yaml pipeline definition, but doesn't let me put a comment there, so it's here instead.

outputStatistics : `dict` [`str`, scalar]
A dictionary of the statistics measured and their values.
"""
return {}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can this be used to store the values that are being tested? I know this duplicates information from the PTC dataset, but it will make it easier to migrate that information into a database in the future.

Copy link
Contributor Author

@plazas plazas Aug 4, 2022

Choose a reason for hiding this comment

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

Yes. Is there an example of this in other "verify" tests? Should they be called something like "PTC_GAIN", "PTC_NOISE", etc. ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm thinking about putting these in a new amplifierStatistics method since the relevant quantities are per amp (gain, turnoff, noise, a00).

@plazas plazas merged commit 4117516 into main Aug 5, 2022
@plazas plazas deleted the tickets/DM-30171 branch August 5, 2022 02:32
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.

None yet

2 participants