The runcomparison class was using a method for getting metric information that included a query against the display info (which was then not used). However, display info is only saved when metrics are plotted or summary stats calculated .. which was not the (direct) case for SSO metrics. So instead, I added a simple 'metric info' class to resultsDb to avoid those failures and am using that instead to get the metric information.
I also added a flag to suppress the warnings that were being issued when summary metrics were not found.
I hope these changes make your changes to the addSummaryStats easier .. OH wait, I'll just add the other extra thing you did (which was if mDict was None to addSummaryStats, it defaulted to getting everything).
The runcomparison class was using a method for getting metric information that included a query against the display info (which was then not used). However, display info is only saved when metrics are plotted or summary stats calculated .. which was not the (direct) case for SSO metrics. So instead, I added a simple 'metric info' class to resultsDb to avoid those failures and am using that instead to get the metric information. I also added a flag to suppress the warnings that were being issued when summary metrics were not found. I hope these changes make your changes to the addSummaryStats easier .. OH wait, I'll just add the other extra thing you did (which was if mDict was None to addSummaryStats, it defaulted to getting everything).