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
When solving a single column, the column’s solve() function is called at least twice. This is unnecessary for simple setups that don’t recycle. We could detect that, break the DAG (which otherwise is only a directed graph) up into parallel chunks and solve them from inlets to outlets.
The text was updated successfully, but these errors were encountered:
The behavior is controlled by /input/model/solver/LINEAR_SOLUTION_MODE.
A value of 1 requests parallel solution of the unit operation models in the ModelSystem. If 2 is specified, sequential solution mode is used if the network is acyclic.
By default (/input/model/solver/LINEAR_SOLUTION_MODE = 0), sequential mode is used if the system has less than 6 unit operations and no cycles. Otherwise, parallel mode is chosen.
The solution mode is applied per switch_XYZ. That is, if sequential mode is selected by the user (/input/model/solver/LINEAR_SOLUTION_MODE = 0) but some switch_XYZ configurations contain cycles, these configurations are solved in parallel.
The acyclic graph is not divided into parallelizable chunks that are solved in parallel. This still needs to be done.
When solving a single column, the column’s solve() function is called at least twice. This is unnecessary for simple setups that don’t recycle. We could detect that, break the DAG (which otherwise is only a directed graph) up into parallel chunks and solve them from inlets to outlets.
The text was updated successfully, but these errors were encountered: