You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
Richard just asked me if we are discussing terminology in our group.
After a short discussion, I am quite convinced that we should also make an effort to recommend a common nomenclature for variables commonly used in IndEcol. For example, currently L or B are used for the Leontief, S or F for the satellite accounts, ... I am not quite sure about the experiences in LCA/MFA but I suspect the same problems are present there.
We can not enforce a specific nomenclature (its not biology...), but we can give strong recommendations.
I know, that the whole matter is quite confusing for students and it would also help to quicker grasp algorithm in papers (and in code). Probably its also a good first starting point towards an ontology. Richard had/will also bring it up in the EEIO section of ISIE.
The text was updated successfully, but these errors were encountered:
Hi
Richard just asked me if we are discussing terminology in our group.
After a short discussion, I am quite convinced that we should also make an effort to recommend a common nomenclature for variables commonly used in IndEcol. For example, currently L or B are used for the Leontief, S or F for the satellite accounts, ... I am not quite sure about the experiences in LCA/MFA but I suspect the same problems are present there.
For MRIO, I tried to summarize my understanding of the variable names here
http://pymrio.readthedocs.io/en/latest/terminology.html
We can not enforce a specific nomenclature (its not biology...), but we can give strong recommendations.
I know, that the whole matter is quite confusing for students and it would also help to quicker grasp algorithm in papers (and in code). Probably its also a good first starting point towards an ontology. Richard had/will also bring it up in the EEIO section of ISIE.
The text was updated successfully, but these errors were encountered: