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
Throughout invest & workbench code, we need to refer to model names in various ways:
the module name (i.e. 'natcap.invest.carbon')
an identifier ('carbon')
an even shorter alias for the identifier, for some models ('cbc')
the official title ('Carbon Storage and Sequestration')
If we always use the same variable names when storing these values, it's easier to reason about the code.
@emlys is doing a bunch of this standardization already on the natcap.invest side in #1532 , which will merge into feature/plugins. The variable names used are:
pyname
model_id
model_alias
model_name
The Workbench (starting at payloads in ui_server.py, actually) should adopt these same conventions.
The text was updated successfully, but these errors were encountered:
davemfish
added
task
Something needs to be done
on hold
There's a reason we're not working on this yet
workbench
For issues relating to the workbench front-end of invest
labels
Mar 1, 2024
This a task for
feature/plugins
Throughout invest & workbench code, we need to refer to model names in various ways:
'natcap.invest.carbon'
)'carbon'
)'cbc'
)'Carbon Storage and Sequestration'
)If we always use the same variable names when storing these values, it's easier to reason about the code.
@emlys is doing a bunch of this standardization already on the
natcap.invest
side in #1532 , which will merge intofeature/plugins
. The variable names used are:pyname
model_id
model_alias
model_name
The Workbench (starting at payloads in
ui_server.py
, actually) should adopt these same conventions.The text was updated successfully, but these errors were encountered: