@gcperk I think this is ready for review. What I did was make a new class called indicator_score, which could have a with_subscores subclass. Each ecosystem function now wraps it output in as.indicator_score(), passing the score, and the subscores if it has them.
So the subscores are now also stored in the site object after calc_indicators() has been run. I don't include them in the table created by get_indicator_scores(), but you can see them if you print the indicators:
I'm not sure how much we want to expose the subscores, or if they're only useful if we want to go digging for them. Any thoughts on how else to incorporate them in outputs?
Closes #72
@gcperk I think this is ready for review. What I did was make a new class called
indicator_score
, which could have awith_subscores
subclass. Each ecosystem function now wraps it output inas.indicator_score()
, passing the score, and the subscores if it has them.So the subscores are now also stored in the
site
object aftercalc_indicators()
has been run. I don't include them in the table created byget_indicator_scores()
, but you can see them if you print the indicators:I'm not sure how much we want to expose the subscores, or if they're only useful if we want to go digging for them. Any thoughts on how else to incorporate them in outputs?