Make sure that inactive assets (and their flows) are removed from the model

[abelsiqueira]

When inactive (false in the active column from assets-data.csv), the asset and related flows should not be present in the model.
This needs a test that changes the solution.

[clizbe]

Is this something we should program specifically, or is this something more general that'll happen when reading in and processing the data? Seems like there might be other reasons to filter things out as well.

[abelsiqueira]

At the time, the idea was that if an asset is inactive, then it should not be included in the graph. That implies that flows that go to and from that asset are not included in the graph.
We were thinking about reading the CSV, but indeed it could happen in more general places.
I imagine active is part of the scenario, so it might be that this option is better processed separately from the CSV reading.
That being said, we can always move the logic elsewhere.

[clizbe]

Would this now be a sub-issue of #461?

[abelsiqueira]

It might be related, but I think active will be moved to the "default scenario" specification or something like that, because it is not part of the input data, right?

[clizbe]

It's a parameter in ESDL... but is also something we might want to change between scenarios...

[datejada]

with #1027 we don't need this issue anymore