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
Master issue for GUI feature requests that come up as developers work to expand GUI library. These requests aren't required for implementation of new flowsheets, but either ease the development of adding new flowsheets to the UI or are enhanced visualization and interaction tools from the user side.
Stream tables for UI output: Posed in Stream table reporting for the UI watertap#1231, remove the need for developers to define each individual state variable for all streams, and instead point to state blocks and variables in which the UI can construct a stream table doing the combination of all state blocks (streams) and desired output variables.
User input based build_options: Posed in Input based build_options in UI validated by class watertap#1239, currently users may build flowsheets by selecting from predefined options in a developer specified list. For generalizable flowsheets, input based build_options as a str, float, or int (able to be validated by class instead of within list) may be useful for flowsheet robustness and customization.
LCOW and SEC breakdown functionality and display in UI: Posed in LCOW and SEC breakdown functionality and display in UI watertap#1256, Streamline the breakdown of LCOW and SEC calculations in the costing package and quickly displaying them (e.g., stacked bar charts) in the UI.
These feature requests may be prioritized by the GUI team, but are not required for the implementation of new flowsheets. However, these features would to advance the GUI ease of use.
The text was updated successfully, but these errors were encountered:
Description
Master issue for GUI feature requests that come up as developers work to expand GUI library. These requests aren't required for implementation of new flowsheets, but either ease the development of adding new flowsheets to the UI or are enhanced visualization and interaction tools from the user side.
build_options
: Posed in Input basedbuild_options
in UI validated byclass
watertap#1239, currently users may build flowsheets by selecting from predefined options in a developer specified list. For generalizable flowsheets, input basedbuild_options
as astr
,float
, orint
(able to be validated byclass
instead of within list) may be useful for flowsheet robustness and customization.Motivation
These feature requests may be prioritized by the GUI team, but are not required for the implementation of new flowsheets. However, these features would to advance the GUI ease of use.
The text was updated successfully, but these errors were encountered: