Set Objective
Change what Network Optimization optimizes for.
When to use this¶
The default objective is maximize profit — revenue minus supply cost minus transport cost. Use this node to switch to a different one: minimize cost, minimize emissions, or balance the two.
Settings¶
Pick the quantity; the direction comes with it. Every objective has one direction that means anything. You do not minimize profit, and you do not maximize emissions, so choosing Objective is the whole configuration.
| Setting | Default | What it does |
|---|---|---|
| Objective | Maximize Profit | The quantity to optimize, one of the four below. |
| Cost Weight | 0.5 |
Read only when the objective is Weighted (Cost + Emissions). |
| Emissions Weight | 0.5 |
Read only when the objective is Weighted (Cost + Emissions). |
| Objective | What the solve does |
|---|---|
| Maximize Profit | Maximizes revenue minus supply cost minus transport cost |
| Minimize Cost | Minimizes supply cost plus transport cost |
| Minimize Emissions | Minimizes total transport emissions. Needs emissions data on the lanes |
| Weighted (Cost + Emissions) | Minimizes Cost Weight × cost + Emissions Weight × emissions |
The node writes the objective onto the scenario, and the solve downstream reads it. It computes nothing itself, which is why a problem with the objective is reported against Network Optimization and not against this node.
Workflow wiring¶
flowchart LR
n1["Import Data (demand.csv)"] --> n2["Map Demand Policy"]
n2 --> n3["Create Scenario"]
n3 --> n4["Set Objective"]
n4 --> n5["Network Optimization"]
Common mistakes¶
- Choosing Minimize Cost on a scenario without demand. The cheapest plan is to ship nothing
- Choosing Minimize Emissions without emissions data on the lanes. The run stops and asks for the column