LillyG901

Should we maybe add a separate issue for clarifying the defintion of `numerical computer model`?

We can add `technical model implementation` as a `model component` of `numerical computer model`, but only if we are sure that we never need to refer to uncertainties within code...

I propose these definitions depending on what you'd prefer: `numerical model` (should maybe be further discussed in it's own issue?) - _is a mathematical model that is calculated by a...

Maybe we are :) If I can summarize this discussion: We will leave `numerical computer model` as it currently is and we should not add `computer model` as a separate...

I agree with the assessment of the classes above, but I don't think anyone has discussed `system cost` yet. If my understanding of the term is correct, I wouldn't classify...

I also like the new definition. I think that it probably caputeres the idea better than what I was thinking of. I imagined that e.g. a computer would fulfill the...

I see, that makes sense. In that case I don't think it's possible to come up with an example that isn't reliant on processes. I still think the definition change...

To summarize: the following classes are process attributes and can therefore be moved as subclasses of cost: `delivery cost` `investment cost` (and all it's subclasses) `variable cost` (and all it's...

I moved `social cost of emission` alongside the other subclasses for now, because I assumed it would be easier to find as a part of the hierarchy it currently belongs...

I propose the following definitions for the new classes(and istances) given in the draft: `Uncertainty `- _Uncertainty is a qualtity of a model that represents any departure from the unachievable...