solutions

solutions copied to clipboard

See #227, this is the corollary for regions. Currently all regions are calculated every time. Instead, the scenario should be able to specify the regions to be included and the...

eethann

Adoption calculations should only calculate for years between start and end year of study. Implement variable filtering of adoption year calculation so it is possible to limit the years calculated...

eethann

In some parts of the model (particularly fuel consumption and emissions) the scenario inputs are in the form "how much more efficient is the solution than conventional technology?". The problem...

denised

The current implementation of adoptions is spread across the individual adoption classes, Helper Tables, the extractor, the code the extractor generates, and the customizations that get made in individual solutions....

denised

Make handling of CONVENTIONAL variables consistent

1

When multiple solutions have the same CONVENTIONAL alternative, they should use the same values for CONVENTIONAL variables. E.g. all the Energy solutions should use the same values for things like...

denised

Scenarios should declare whether they are Baseline, Conservative, etc.

1

There is no requirement that a scenario be in any specific camp, but most of them are. Adding explicit metadata would make it easier for any user interface to help...

denised

In some cases, integrations adjust adoptions of models to reflect the competition for common resources between them. This has the effect of muddying the derivation of the adoption, and also...

denised

Set global variables globally

3

A few of the parameters (VMAs) are not specific to an individual solution: fuel cost and discount rate are two and there may be more. Scenarios each have their own...

denised

colleenskemp

Documentation\Glossary.md

1

I'm a new contributor and in the process of reviewing documentation it took me much longer than it should have to find and discover what all the acronyms in various...

parenteaun