gridmod / rts-gmlc Goto Github PK

View Code? Open in Web Editor NEW

146.0 21.0 80.0 247.69 MB

Reliability Test System - Grid Modernization Lab Consortium

R 0.62% MATLAB 0.74% Python 1.39% HTML 94.97% Jupyter Notebook 2.28%

rts energy-system energy-data power-systems power-systems-analysis matpower

rts-gmlc's Introduction

RTS-GMLC

Reliability Test System - Grid Modernization Lab Consortium

This repository is for the Reliability Test System Grid Modernization Lab Consortium (RTS-GMLC) which is an updated version of the RTS-96 test system. A summary of updates can be found in GMLC_updates.md.

This repository, and the associated data has been developed to facilitate Production Cost Modeling. Reliability calculations using the updated RTS-GMLC data in this repository amd the RTS3 program, provided by Gene Preston can be found here.

The RTS_Data folder contains data in an open `csv` format, and in grid modeling tool specific formats:

SourceData contains several csv files that describe all the RTS-GMLC data.
FormattedData contains folders for each tool specific data format. Each tool specific folder is also intended to contain a script that automates the conversion from SourceData in addition to solutions obtained from each tool in the FormattedData/*tool*/*tool*_Solution folder. Currently datasets are included in the following formats:

TODO and Identified Areas of Improvement:

Conventional Plant Data:
- Add information about different operating configuration for combined cycle plants
- Evaluate/address the realism of the relative sizes of units in different categories
Wind and Solar Data:
- Update to the state-of-the-art datasets (NSRDB and WindToolkit) and add raw weather data

Setup

git clone [email protected]:GridMod/RTS-GMLC.git
cd RTS-GMLC
git submodule init
git submodule update

Contributing

Contributions to the development and enahancement of RTS data is welcome. Please see CONTRIBUTING.md for contribution guidelines.

DATA USE DISCLAIMER AGREEMENT

(“Agreement”)

These data (“Data”) are provided by the National Renewable Energy Laboratory (“NREL”), which is operated by Alliance for Sustainable Energy, LLC (“ALLIANCE”) for the U.S. Department Of Energy (“DOE”).

Access to and use of these Data shall impose the following obligations on the user, as set forth in this Agreement. The user is granted the right, without any fee or cost, to use, copy, and distribute these Data for any purpose whatsoever, provided that this entire notice appears in all copies of the Data. Further, the user agrees to credit DOE/NREL/ALLIANCE in any publication that results from the use of these Data. The names DOE/NREL/ALLIANCE, however, may not be used in any advertising or publicity to endorse or promote any products or commercial entities unless specific written permission is obtained from DOE/NREL/ ALLIANCE. The user also understands that DOE/NREL/Alliance is not obligated to provide the user with any support, consulting, training or assistance of any kind with regard to the use of these Data or to provide the user with any updates, revisions or new versions of these Data.

YOU AGREE TO INDEMNIFY DOE/NREL/ALLIANCE, AND ITS SUBSIDIARIES, AFFILIATES, OFFICERS, AGENTS, AND EMPLOYEES AGAINST ANY CLAIM OR DEMAND, INCLUDING REASONABLE ATTORNEYS' FEES, RELATED TO YOUR USE OF THESE DATA. THESE DATA ARE PROVIDED BY DOE/NREL/Alliance "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL DOE/NREL/ALLIANCE BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER, INCLUDING BUT NOT LIMITED TO CLAIMS ASSOCIATED WITH THE LOSS OF DATA OR PROFITS, WHICH MAY RESULT FROM AN ACTION IN CONTRACT, NEGLIGENCE OR OTHER TORTIOUS CLAIM THAT ARISES OUT OF OR IN

rts-gmlc's People

Contributors

Stargazers

Watchers

Forkers

aliajder tom-nudell bennettmcbrendan fanlin-meng rockyepri rdzman harrysorensennrel wsxbjx gordstephen asjader oaansari florianshepherd astaid andreabragantini martyschwarz bluejuniper datejada daniel-thom xb00dx dldonaldson maov-epri cuihantao pprianto haoli9401 sourabhdalvi noahrhodes awig dlwoodruff fxw-fan arjunreddy07 jahanbani gridtechs mariegirod davidgg-kh aishwarya1602 scdhulipala dsehloff adyreson tcyuan373 shrivats-pu fjdhkyf3423 gkaransail prasangshag iitriigo biabuss catherineyeh rbolgaryn nongchao smart-ds josephmckinsey adowling2 stevenbroad willfrazr sf-snigdha zzllkk oibaf97 jda256 xinfang88 yang-hanbin xiangao1 rajaz254 bknueven tangx0201 gsaenzt erikfilias ec-jrc atribera dongweis rainsmileli mlr666666 akhi01673 etrieschman oriolraventos chrisyeh96 sebroad sablea boyuan276

rts-gmlc's Issues

GIS data for the generated relative node locations

The link (https://github.com/GridMod/RTS-GMLC/blob/master/RTS-GMLC_updates.md) mentions about having generated relative node locations i.e GIS data for a southwestern U.S. location. Is the GIS data for these node locations available in the repository?

info on VG data

a few questions:

what's the unit of measure for the values in the DA_wind and RT_wind files?
what's the unit of measure for the values in the DA_pv and RT_pv files?
what's the unit of measure for the values in the DA_rtpv and RT_rtpv files?
is there any document that contains the answer to the unit of measure questions above? (if not, I can volunteer to create one as I get questions answered)
for the wind generator 309_wind, is it correct to assume that 309 is the bus the generator is connected to?
Thanks

RT and DA load profiles do not agree

I noticed a quite few files in the load time series folder.
I actually used “DA_hourly” and “Rt_5min” files for each area; however, I noticed that the values are quite different.
Specifically, I was using the first week of June, and DA load is almost double the RT load.
Am I using the wrong files? And if so can you lead me to the correct time series data?

update the committed PLEXOS model

Buses 13, 14, 15, 19, 20 mentioned in the RTS-GLMC model updates do not exist in original RTS-96 data (.m file)

In the link https://github.com/GridMod/RTS-GMLC/blob/master/RTS-GMLC_updates.md, it is mentioned that the RTS-GMLC model was obtained by making updates to the RTS-96 data that uses buses 13, 14, 15, 19, 20. However the buses in the .m file are numbered from 101 to 325. Could you please elaborate what these buses (13, 14, 15, 19, 20 etc.) are?

gen costs

I'm trying to figure out how to map cost to generators. The file RTS.m contains a section mpc.gencost, but the data in this section doesn't appear to include an identifier that can be tied to generators. Also found that the file gen_params.csv contains fuel info, but only for a small subset of the generators. Can you help? Thanks!

MATPOWER file has start heat instead of start cost

remove fuel memberships for VG generators

also remove fuel objects that correspond to "fuels" that are not actually fuels (hydro, PV, wind, etc)

LMPs at buses for PLEXOS solution

For the UC and ED information that is available in the dataset, could (if can be made available) the LMP values obtained from PLEXOS at the buses also be provided. I am now able to use the UC information to commit the units using GLPK and the LMP values can provide to have a feel of the optimization where the generators are dispatched.

Reserves definition

The model includes 2 types of reserve (flex and reg) but I couldn't find their definition (eg response time). Please clarify. Thanks.

Same ramp rates in RTS.m?

ramp_10 and ramp_30 are same for all the generators. Are the values for 10 minutes or 30 minutes? I suppose that 5-minute ramp rates (for RT) are ramp_10/2 and 1-hour ramp rates are (for DT) are ramp_30 * 2. Is this correct?

Add RE units to RTS.m

in a new release...

fix heat rate units, make sure start/shutdown costs are calculated correctly

generator cost unit

What is the generator cost unit used in RTS.m? The numbers are very large.

add generator mix changes documentation

Add table that describes the RTS-96 generators removed and new generators replaced.

Why are there NaN values in the RTS-96 matfile (RTS.m)?

There are many values in the matfile (RTS.m) which are NaN.

Forecast data

Does the dataset include forecast data as well as the operation data?

Eg, if I wanted to model day ahead operations, I would want to use a renewable forecast,

and then model real-time operations to dispatch to the actual renewable production.

Thanks!
Ross

Reactive load

Is there any information regarding reactive load?

Same LMP values at all buses for DCOPF

When DC OPF is run on the RTS data (using the RTS.m file), the LMP values obtained at all the buses are the same. But AC OPF gives different LMPs at the buses. This might not be an issue but an observation regarding the data set.

Fuel prices

Please clarify the UOM for the values in fuel_prices.csv. Thanks

ACOPF not converging in MATPOWER

The RTS.m file fails in MATPOWER when running an AC optimal power flow. I can get the case to converge with Gurobi when running a DC optimal power flow, but for AC the MATPOWER MIPS solver fails to converge after 2 iterations with the error message "Numerically Failed".

rearrange so that the data is accessable to non-PLEXOS and PLEXOS users alike and is more visible within the repo

VOIR?

Is there a value of insufficient reserve associated with each reserve product in the PLEXOS simulations?

Unify the generator ID format

vg_gen_DA.csv is using a different format of generator IDs from hydro_profiles.csv. Can we generate common IDs for all the data files?

make reserves.csv

Columns:

product name
profile datafile
response time
direction
spin/non-spin

Generation dispatch output data/unit commitment data

Does the dataset also provide generation dispatch output for the whole year based on the published hourly load profiles? We are doing the transmission dispatch and want to understand how the power flows through existing transmission through the year.

For this, I was wondering if the generation dispatch output/ unit commitment data for the RTS model is already available. Any information in this regard without going through PLEXOS or other unit commitment formulation would be much appreciated.

Thanks!
Krishna.

Some generator heat rate increments are less than minimum stable level

A couple of the smaller generators have their first heat rate load point at a value that is less than their min gen. This means at min gen they are already in the second heat rate increment. May not be a problem though.

Pmin in RTS.m file doesn't use the UW min gen numbers

It appears to use the first load point increment value as the Pmin value in the RTS.m file. The correct min gen values are being used when the PLEXOS database is created though.

combine gen.csv gen_timeseries.csv and gencost.csv in SourceData

Add reserve requirements to RTS.m

see page 29 of this document

RT hydro

There is no hydro data for RT.

Question about hydro and solar data

I see there is only 1 hydro profile per region. Does that mean each hydro generator has that exact same schedule or is that schedule divided amongst all the hydro generators in a region.
What’s the difference between “pv” and “rtpv”?

README for non-PLEXOS users

I see #3 rearranging some files for non-PLEXOS users. But, I am still struggling to figure out how to use the RTS data for Argonne's work. Is there any plan for README for those who are like me? It would be great if one can formally define the formulation that is (supposed to be) used with the parameters defined in the data files.

I tried using the raw data files in Create_PLEXOS_database/1-parse-matpower/outputs. There are some files and fields in csv format that I do not know. For example, I do not know how to construct generation cost based on gen.cost.data.csv. And, some fuel types used in gen.fuel.csv are not defined in fuel.price.csv.