Skip to content

Commit 0f39c81

Browse files
committed
Rename variable costs to valuecurve options
1 parent 0ae2f33 commit 0f39c81

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/make.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ pages = OrderedDict(
4545
"Internal API Reference" => "api/internal.md",
4646
"Glossary and Acronyms" => "api/glossary.md",
4747
"Type Hierarchy" => "api/type_tree.md",
48-
"Variable Cost Options" => "api/variable_costs.md",
48+
"`ValueCurve` Options" => "api/valuecurve_options.md",
4949
"Specifying the category of..." => "api/enumerated_types.md",
5050
"Developer Guidelines" => "api/developer_guidelines.md",
5151
"Citation" => "api/citation.md"

docs/src/api/variable_costs.md renamed to docs/src/api/valuecurve_options.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# [Variable Costs](@id curve_table)
1+
# [`ValueCurve` Options](@id curve_table)
22
Operating cost data typically includes both fixed and variable costs. See the how-to on [Adding an Operating Cost](@ref cost_how_to) for a demonstration of defining an operating cost.
33

44
In PowerSystems.jl, the *variable* portion of the operating cost can be represented as linear, quadratic, or piecewise input-output curves; potentially piecewise marginal heat rates; average heat rates; and more, as best fits the input data. This is done by constructing various subtypes of [`ValueCurve`](@ref).

0 commit comments

Comments
 (0)