Hi,
I’m having some difficulties with loading my demand profiles. When examining the PCM full-year scenario, I noticed a “demand shape” profile with values ranging between 0 and 1. Could you please explain how you determined these values? I attempted to extract data from the ISO New England website, where I found hourly profiles for the entire zone, but not on a per-node basis. The zone codes resemble the names you used for individual demand profiles, though the values appear significantly different.
Additionally, I noticed that in the events section, the same “ME demand shape” profile is applied to two nodes (Augusta and Portland). However, when I inspected the editor for these two externals, I saw that the DefActivePowerSetPoint values differed between them. Could you clarify how I should determine the correct DefActivePowerSetPoint for each node?
In summary, I would appreciate any guidance on how you derived the demand shape and the appropriate DefActivePowerSetPoint values.
Great question! The demand profiles for the ENET39 were obtained for each state in New England from data made publicly available by NREL (specifically, these data came from the ReEDS capacity expansion model). To apply these profiles to the ENET39, these state-level demand profiles needed to be distributed amongst the various nodes in the network. This was done by “normalizing” the profiles (dividing every value by the peak such that the maximum is 1) and then scaling each profile according to the relative demand at each node in the ENET39.
How did we determine how much the demand should be scaled at each node? Since this dataset is based on the IEEE 39-bus test system, we just used the power withdrawal for each demand in that test system to scale these demands, and matched each demand with the corresponding load profile according to the state it was in. For more information about the dataset, check out the ENET39 Documentation.
At this point you might be thinking: “Wait a second, these are just assumptions encoord made when building the dataset based on the data that was publicly available? Does this mean there is no ‘correct’ way to determine active power setpoints in the absence of actual SCADA data?” You would be correct! We did our best to document our assumptions as clearly and succinctly as we could in the ENET39 documenation, which I highly recommend you take a look at. If you have any further questions, please post them here! We’ll do our best to help.