Open redfrexx opened 2 years ago
Briefly discussed today at meeting: We should split this into 2 different scores. The completeness score should measure whether or not there exists data, and should be an issue for the main package. The uncertainty score should instead measure the use of default values in the calculator (ex. average instead of detailed occupancy, size, fuel type, etc).
Desgin an uncertainty score for the data put in by the users. Were average values used all the time or were more specific values (e.g., fuel type, size class, etc.) used?
Figure out which data should be retained in the database so that the score could be recalculated later. Right now we try to store as less data as possible so that we don't run into data privacy issues