Figure 4
The flowchart starts at an oval labeled “START”, which leads down to a rectangular step “Topology Generation”; three curved arrows labeled “Repeat” loop from lower parts of the chart back to this box, indicating multiple iterations. To the left, a rectangle labeled “Extract Port Attributes” feeds into a circular node “Component Library”, which in turn connects horizontally into “Model Generation” in the main vertical chain. A separate circular node, “Specifications Data”, connects into “Parameterization”, and another circular node, “Drive Cycle”, connects into “Optimal control tuning”, both in the main column, supplying external inputs. After “Topology Generation”, a diamond decision box asks, “Is Topology distinct?” with “Yes” leading down to “Model Generation” and “No” leading right to a red rounded rectangle, “Discard Topology”, which then loops back up to “Topology Generation” through one of the repeat arrows. The main vertical path from top to bottom is “Topology Generation”, the decision “Is Topology distinct?”, “Model Generation”, “Parameterization”, “Optimal control tuning”, “Simulation”, decision “Is M A E acceptable?”, “Save Topology and Results”, decision “All required topologies?”, and finally “Plot Emissions versus Cost Graph”. At the “Is M A E acceptable?” decision, the “No” branch goes right to a red rounded rectangle, “Discard Topology and Model”, then back to “Topology Generation”, while the “Yes” branch continues downward. At the last decision, “All requred topologies?”, the “No” branch loops back up to “Topology Generation”, and the “Yes” branch proceeds to the endpoint “Plot Emissions versus Cost Graph”.Workflow of the Proposed Framework. Source: Authors’ own work