48 mitigator summary #58
Conversation
…age tables, updates the heatmaps panel with tooltip guidance.
… mitigator and scheme coverage
There was a problem hiding this comment.
Thank you for enacting what was a fairly vague request!
Re the 'Mitigator coverage' table: don't worry about this now, but we may want to include a mitigator code column and maybe some other filterable/sortable columns like the mitigator type (i.e. 'activity avoidance' or 'efficiencies'), but I think this is a bigger question that's actually part of #43. And the mitigator lookup in the 'Data' section is always there if people want more info.
Re the 'Scheme coverage' table: your idea to embolden the selected schemes is a nice touch. There's still part of me that wonders if we should automatically filter these coverage tables to the schemes selected in global settings. But I think this is the right place to start.
I've added a couple of comments and suggestions below; could you make a couple of adjustments and I'll re-review?
| make_mitigator_uptake_dt <- function(dat, selected_schemes) { | ||
|
|
||
| dat |> | ||
| # remove ampersand from mitigator names - causes issues with DT filters |
There was a problem hiding this comment.
Curious! Added issue #60. Ultimately we probably want to maintain the ampersands, if possible.
Close #48
Includes:
Both views show comparisons between all (schemes/mitigators) and selected(schemes/mitigators).