#68 BinnedScatterPlotSysTest #73
Conversation
It is useful, but I wonder if you could put a keyword for an optional area that the user could provide to make a number density? For example, if the dataset corresponds to a single focal plane and we think the area lost due to bright stars is negligible, or that the mask plane could be used to properly calculate an area, then it might be useful to be able to pass that information in to the routine. |
stile/hsc/base_tasks.py
Outdated
| @@ -63,7 +63,8 @@ class CCDSingleEpochStileConfig(lsst.pex.config.Config): | |||
| "WhiskerPlotStar", "WhiskerPlotPSF", "WhiskerPlotResidual", | |||
| "ScatterPlotStarVsPSFG1", "ScatterPlotStarVsPSFG2", | |||
| "ScatterPlotStarVsPSFSigma", "ScatterPlotResidualVsPSFG1", | |||
| "ScatterPlotResidualVsPSFG2", "ScatterPlotResidualVsPSFSigma" | |||
| "ScatterPlotResidualVsPSFG2", "ScatterPlotResidualVsPSFSigma", | |||
| "RMSE1Sky", "RMSE2Sky", "RMSE1Chip", "RMSE2Chip", "CountPerMagnitude" | |||
There was a problem hiding this comment.
I'm not sure we need to keep these as separate per-component RMS's. Normally when I am doing this kind of calculation I'll combine the components, e.g., for a per-component RMS I would do 0.5*(sum(e1^2)+sum(e2^2)).
There was a problem hiding this comment.
Apparently, at some point, I added the RMSESky and RMSEChip options--thanks for the suggestion. Should we leave the e1, e2 versions as well (in case we need them as a diagnostic) or just remove them as dead weight in the code?
Conflicts: stile/hsc/base_tasks.py stile/hsc/sys_test_adapters.py stile/sys_tests.py
Conflicts: stile/__init__.py
Hi folks,
Here's a PR for branch #68, creating a new class of systematics test, the
BinnedScatterPlotSysTest. The class takes an array and produces a scatter plot whose y-values are some function of the data; builtin options aremean,median,rmsandcount(just the number of objects in each bin). It can also take a callable function to perform on the data. I had to make some choices on defaults and parameter names but they're mostly described in the docstring for theBinnedScatterPlotSysTest--please feel free to suggest any alterations.The
BinnedScatterPlotSysTestis actually a child class ofScatterPlotSysTest, and calls the main method of that object to generate the scatter plot once we've done the appropriate calculation.I also made some default choices for which of these we'd like in the HSC module and made adapters for those tests. (Eventually we should have a more flexible method of doing this, which will be part of branch #34.) Of particular note is the
CountPerMagnitudeadapter. Number density is hard because we'd have to know the area of each data set, but just counting objects is okay...do we think this is useful?