Thanks, Hsin-Fang Chiang!
Two follow-up comments, which do not directly affect this report:
I'm not sure filing tickets about the CCDs that fail processCcd...
I think that any failure which cannot be otherwise explained should be ticketed. If you know it will be fixed by (e.g.) a particular update to the matcher, then it doesn't need to be ticketed directly, but it should be added to the ticket capturing the matcher work and, when the matcher changes are merged, we need to confirm that they really do fix the problem.
About providing actionable feedback, I think I've been doing that throughout the reprocessing campaign. Many tickets have been filed and included in Section 6.
Among those tickets, it would be really great if
DM-11171 and DM-10624 can be fixed before the next large run...
It certainly wasn't my intention to imply that no tickets had resulted from this work; sorry if I gave that impression. I do think we should find a way to feed your results more directly into the development process, though. For example, I wasn't aware that you regarded the above tickets as particularly important. Making sure concerns like this are taken into account is what the T/CAM coordination meetings are for: perhaps you could encourage Joel Plutchak to represent your priorities to the rest of DM there?