Code Monkey home page Code Monkey logo

rts-gmlc's Issues

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

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.

Reactive load

Is there any information regarding reactive load?

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?

commitment cost

I found the costs for startup, shutdown, and generation. Do we have a cost for operating a generator (i.e., cost for a generator being on)?

how to use the reserve data?

Could you please explain how the reserve data can be used in the model? Is this the system-wide reserve amount? What is the value of the data?

Fuel prices

Please clarify the UOM for the values in fuel_prices.csv. 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?

make reserves.csv

Columns:

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

VOIR?

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

Unit Expansion Analysis

From the perspective of unit expansion analysis, could you clarify whether the gen_id file defines a) the set of existing units in the system or b) the set of candidate units in the system. Thanks!

generator cost unit

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

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.

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

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.

RT hydro

There is no hydro data for RT.

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?

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.

gen costs: 4th load/cost point and convexity

In the RTS.m file, three load/cost points are provided. Could the 4th point for Pmax load and its cost also be provided for the piecewise linear cost function?

Also, is the slightly non-convexity of the slope of the three load/cost points really intended to be or is it emanating from the RTS_96 heat rates itself?

Zone Mapping

Could you please confirm that the proper mapping of units to service territories and load zones is as follows:

Region 1 = 100 units = APS
Region 2 = 200 units = NV Energy
Region 3 = 300 units = LADWP

reorganize RTS_Data

Reorganize RTS_Data to house the SourceData in accessible CSV files instead of MATPOWER format.

Provide FormattedData folder with formatting specific to different PCM tools.

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!

vg generators and hydro

Are vg generators and hydro (defined in vg_gens_DA.csv and hydro_profiles.csv, respectively) considered in addition to the generation capacity defined in RTS.m?

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".

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.

Question about hydro and solar data

  1. 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.

  2. What’s the difference between “pv” and “rtpv”?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.