diff --git a/docs/user-guide/2-variant_manager.md b/docs/user-guide/2-variant_manager.md index 892a57b524..4a7b6dbcfc 100644 --- a/docs/user-guide/2-variant_manager.md +++ b/docs/user-guide/2-variant_manager.md @@ -53,31 +53,9 @@ The example provided bellow demonstrates the creation of two areas and a link be ## Command list -### Base commands - -| Action Name | Arguments | Description | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| -| update_config |
{| Update arbitrary config | -| replace_matrix |
target: <INI_TARGET>
data: <INI_MODEL>
}
{| Replace arbitrary matrix | -| create_area |
target: <INPUT_SERIES_MATRIX>
matrix: <MATRIX>
}
{| Create a new area | -| remove_area |
area_name: <STRING>
}
{| Remove an existing area | -| create_cluster |
id: <AREA_ID>
}
{| Create a new thermal cluster | -| remove_cluster |
area_id: <AREA_ID>
cluster_name: <STRING>
prepro?: <STRING>
modulation?: <MATRIX>
parameters?: <INI_MODEL>
}
{| Remove an existing thermal cluster | -| create_renewables_cluster |
area_id: <AREA_ID>
cluster_id: <CLUSTER_ID>
}
{| Create a new renewable cluster | -| remove_renewables_cluster |
area_id: <AREA_ID>
cluster_name: <STRING>
parameters?: <INI_MODEL>
}
{| Remove an existing renewable cluster | -| create_link |
area_id: <AREA_ID>
cluster_id: <CLUSTER_ID>
}
{| Create a new link | -| remove_link |
area1: <AREA_ID>
area2: <AREA_ID>
parameters?: <INI_MODEL>
series?: <MATRIX>
}
{| Remove an existing link | -| create_district |
area1: <AREA_ID>
area2: <AREA_ID>
}
{| Create a new district (set of areas) | -| remove_district |
name: <STRING>
base_filter?: "add-all" | "remove-all"
filter_items?: <LIST[AREA_ID]>
output?: <BOOLEAN> (default: True)
comments?: <STRING>
}
{| Remove an existing district | -| create_binding_constraint |
id: <DISTRICT_ID>
}
{
name: <STRING>
enabled?: <BOOLEAN> (default: True)
time_step: "hourly" | "weekly" | "daily"
operator: "equal" | "both" | "greater" | "less"
coeffs: <LIST[CONSTRAINT_COEFF]>
values?: <MATRIX>
comments?: <STRING>
}
{| Create a new binding constraint | -| update_binding_constraint |
type: <"cluster" | "link" (choosing one or the other imply filling the right corresponding parameter below)>
link: <AREA_ID>%<AREA_ID> (link)
cluster: <AREA_ID>.<CLUSTER_ID>
coeff: <NUMBER>
offset?: <NUMBER>
}
{| Update an existing binding constraint | -| remove_binding_constraint |
id: <BINDING_CONSTRAINT_ID>
enabled?: <BOOLEAN> (default: True)
time_step: "hourly" | "weekly" | "daily"
operator: "equal" | "both" | "greater" | "less"
coeffs: <LIST[CONSTRAINT_COEFF]>
values?: <MATRIX>
comments?: <STRING>
}
{| Remove an existing binding constraint | -| update_playlist |
id: <BINDING_CONSTRAINT_ID>
}
{| Update the playlist with provided active (or inactive) years (starting from year 1) | -| update_scenario_builder |
active: <BOOLEAN> (default: True)
reverse: <BOOLEAN> (default: False)
items: <LIST[NUMBER]> (default: None)
}
{| Update scenario builder with partial configuration | -| update_district |
data: <RULESETS_MODEL>
}
{| Update a district (set of areas) | -| update_raw_file |
id: <STRING>
base_filter?: "add-all" | "remove-all"
filter_items?: <LIST[AREA_ID]>
output?: <BOOLEAN> (default: True)
comments?: <STRING>
}
{| Replace arbitrary data file (must not be a matrix or ini target) with a base64 encoded data | - -#### Base types +### Base types + +The following table describes the data types used in the commands: | Type | Description | |----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -89,11 +67,289 @@ The example provided bellow demonstrates the creation of two areas and a link be | RULESETS_MODEL | like `INI_MODEL` with some specifications: an empty string allows to remove a key (ruleset or cell value) and a ruleset "A" with for value the name of an another ruleset "B" allows to clone the content of "B" in "A" | | INPUT_RAW_FILE_TARGET | a valid antares raw data file relative path (without extension). The path can be found when browsing the study in detailed view | | INPUT_SERIES_MATRIX_TARGET | a valid antares matrix data file relative path (without extension). The path can be found when browsing the study in detailed view | -| MATRIX | a matrix id or a list of list of values (eg. [[0,1,2],[4,5,6]] where each sub list is a row of the matrix). Matrix id can be found in the Matrix Data manager tab. | -| AREA_ID | the id of an area (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | -| CLUSTER_ID | the id of a cluster (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | -| DISTRICT_ID | the id of a district (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | -| BINDING_CONSTRAINT_ID | the id of a binding constraint (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | +| MATRIX | a matrix id or a list of list of values (eg. [[0,1,2],[4,5,6]] where each sub list is a row of the matrix). Matrix ID can be found in the Matrix Data manager tab. | +| AREA_ID | the ID of an area (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | +| CLUSTER_ID | the ID of a cluster (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | +| STORAGE_ID | the ID of a short-term storage (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | +| DISTRICT_ID | the ID of a district (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | +| BINDING_CONSTRAINT_ID | the ID of a binding constraint (same as name, but lower cased and only with the following characters: [a-z],[0-9]_,(,),-,&,",". Other characters will be transformed into a single space.) | + +### `update_config` + +Update arbitrary config + +```json +{ + "target": "
target: <INPUT_RAW_FILE_TARGET>
b64Data: <STRING>
}