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
number counts test updates #158
Comments
Note, issue posted too early, so I edited to complete it (please read online). |
Thanks for suggestions, @rmandelb. They are all good suggestions. 1, 2, 4 are all very easy to implement. 3 should be straightforward too but does require compiling those data points. @duncandc are you up to help with this? I'm asking you first because you implemented the original test, but no worries if not. I can also do it myself and/or find someone else to do it. |
For (3) I was referring specifically to the numbers I gave in the first post, so no more compiling should be needed. (I could write an explanatory comment in the code about where they come from.) |
@rmandelb @yymao Thanks for the suggestions. I think we should make it standard to have a text file output of the points in the plots for as many tests as possible. I have had a couple of other people comment on how useful they are. The output should also include any cuts that were made and any other relevant information such as the area above. Output columns should be labeled. |
Just chiming in to confirm that it is extremely useful when the tests come with tabulated data points. When available, I use these all the time in local calibrations. |
I think I can take care of this rather easily. For reference, the points for HSC are available as tabulated data. |
Based on some work I just did with the test of the cumulative number counts, e.g., with outputs like this:
https://portal.nersc.gov/project/lsst/descqa/v2/?run=2018-09-10_10&test=ApparentMagFuncTest_HSCz
I have a few suggestions to make:
The text was updated successfully, but these errors were encountered: