dhia-gharsallaoui / watervalues

Calculate water values for Antares simulator

Watervalues

The R package watervalues allows to :

1. Prepare the Antares study by creating the fictive area,
2. Launch the simulations by updating the coupling constraints,
3. Read the results
4. Calculate the water values

Install package

You can install the package from GitHub with:

# install.packages("devtools")
devtools::install_github("dhia-gharsallaoui/watervalues", build_vignettes = TRUE)

To install all the package dependencies you can run the script inst/dependencies.R

Load the package

library(watervalues)

Now we are ready to use our package.

shiny_water_values()

watervalues's Issues

MC year selection

When chosing to run on a subset of the total number of MC years (e.g. 1 of a total of 1015) then the information in the MC scenario builder is overwritten and lost. Would it be possible to only select the year in the MC year playlist instead and leave the number of MC years unchanged?

Reset inflows and keeping the reservoir make Antares keep using the reservoir as a closed STEP

Reset inflows and keeping the reservoir make Antares keep using the reservoir as a closed STEP .
the problem is when we have a lot of unsupplied energy Antares will use even the double of turbining max power.

Check for Simulation & Output settings

Hi Dhia, it would be nice if the script could check before launching the Antares simulation if the settings needed for the calculation of water values (e.g. "weekly year by year output", export mc scenarios,...) are set correctly in order to avoid running the simulation and only afterwards checking that it is missing the files.

Calculation problem in predicting the inaccessible states

MC years

When using shiny, the MC year number from the slider is not correctly given as a parameter to the simularion function. Problem does not exist when calling the simulation function directly.

Link to/from fictive node

In setupWaterValuesSimulation.R it would be nice to be able to have the from property of the link selected by the user and not have it automatically connected to the area.

Solver location

In Shiny, for each discretesation step the solver location has to be confirmed. Would be easier if the location could be set at the beginning of run for all steps.

Namespace

importFrom(antaresEditObject,filteringOptions) seems to be missing in the Namespace file

NAMESPACE file

export(waterValues) is causing undefined export error

Intra-model parameter

the generation of the fictive load need to have the same final size as the other nodes to avoid the error when intra-model option is activated for load.

Problem in elimination criteria

bug when elimination criteria equal to 100%.
When this criteria happens with all scenarios accessibles in a week, the scripts eliminate all and get unfeasible week.