Repository class is used to store the model 'bricks' such as commodity, technology, supply, demand, trade, import, export, trade, storage, etc. Calendars, settings, and configurations cannot be stored in the repository, they have separate slots in model or scenario objects.
Usage
newRepository(
name = "base_repository",
...,
desc = NA_character_,
misc = list()
)Arguments
- name
character. Name of the repository.
- ...
list. Model objects ("bricks"), e.g., technologies, constraints, costs, etc., stored in with their names as keys, or gropped in named lists.
- desc
character. Description of the repository.
- misc
list. Any additional data or information to store in the object.
See also
Other repository model data:
class-repository
Examples
repo <- newRepository(
"my_repo",
newCommodity("ELC", unit = "MWh"),
newCommodity("COA", unit = "MMBtu"),
desc = "Two commodities and nothing else"
)
repo
#> repository 'my_repo': 2 objects.
#> Two commodities and nothing else
# objects can be added afterwards; `add()` returns the updated repository
repo <- add(repo, newSupply("SUP_COA", commodity = "COA",
supply = data.frame(cost = 2)))
repo
#> repository 'my_repo': 3 objects.
#> Two commodities and nothing else