Skip to content

Commit

Permalink
extract seasonal rating period from forecast file
Browse files Browse the repository at this point in the history
  • Loading branch information
catkins-miso committed Aug 19, 2024
1 parent 5ea7c10 commit 98801dd
Show file tree
Hide file tree
Showing 4 changed files with 94 additions and 95 deletions.
8 changes: 4 additions & 4 deletions docs/_data/components/schemas/array-max-seasons.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ seasonal-proposals:
periods:
<<: *schedule
items:
$ref: ./forecast-limit-period.yaml#/seasonal-proposal
$ref: ./seasonal-rating-period.yaml#/proposal

missing-seasonal-obligation:
type: object
Expand Down Expand Up @@ -65,7 +65,7 @@ seasonal-proposals-slim:
to each season in the `default-seasonal-schedule`.
items:
$ref: ./forecast-limit-period.yaml#/seasonal-proposal-slim
$ref: ./seasonal-rating-period.yaml#/proposal-slim
example: [[50, 55, 60, 65], [70, 75, 80, 85], [90, 95, 100, 105],[90, 95, 100, 105]]

seasonal-rating-snapshot-item:
Expand All @@ -76,7 +76,7 @@ seasonal-rating-snapshot-item:
periods:
<<: *schedule
items:
$ref: ./forecast-limit-period.yaml#/seasonal-snapshot
$ref: ./seasonal-rating-period.yaml#/snapshot

seasonal-rating-snapshot-item-detailed:
type: object
Expand All @@ -86,4 +86,4 @@ seasonal-rating-snapshot-item-detailed:
periods:
<<: *schedule
items:
$ref: ./forecast-limit-period.yaml#/seasonal-snapshot-detailed
$ref: ./seasonal-rating-period.yaml#/snapshot-detailed
2 changes: 1 addition & 1 deletion docs/_data/components/schemas/day-night.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,4 @@ description: |
type: string
enum:
- DAY
- NIGHT
- NIGHT
90 changes: 0 additions & 90 deletions docs/_data/components/schemas/forecast-limit-period.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,50 +23,6 @@ proposal:
- $ref: '#/period'
- $ref: ./limit-proposal.yaml

seasonal-proposal:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: '#/proposal'
- type: object
properties:
season-name:
$ref: ./season-name.yaml
day-night:
$ref: ./day-night.yaml

seasonal-proposal-slim:
type: array
title: Seasonal Period Proposal slim
maxItems: 20 # (max continuous + emergency ratings) * max num fields in limit type, e.g. MW and p.f.
minItems: 1
items:
type: number
title: Continuous and Emergency Ratings values
description: |
Each number in this array corresponds to a value of the continuous and
emergency ratings for a particular period. The first values correspond to
the continuous (normal) rating and the subsequent values correspond to the
emergency ratings in order of decreasing duration. The durations are
defined in the `proposal-header.default-emergency-durations` field.
The exact number of values in this array is further determined by the
`proposal-header.limit-type` field. If the `limit-type` is a single value
like "Apparent Power", e.g., `{"mva":1}`, then the array will have a
single value for each rating. For example, if there was only one emergency
duration defined, then the array would have two values, e.g. `[50, 55]`,
corresponding to a 50MVA continuous rating and 55MVA emergency rating,
respectively.
However, if the `limit-type` is an "Active Power and Power Factor", e.g.,
`{"mw":1, "pf":1}`, then the array will have two values for each rating.
If we continue with the example of having only one emergency duration
defined, then the array would have four values. Thus, instead of
`[normal_MVA, emergency_MVA]`, we would have `[normal_MW, normal_pf,
emergency_MW, emergency_pf]`, e.g., `[300, 1.0, 350, 1.0]`.
proposal-considered:

description: Details a proposal that was considered by the Clearinghouse run.
Expand Down Expand Up @@ -106,49 +62,3 @@ snapshot-detailed:
allOf:
- $ref: '#/snapshot-slim'
- $ref: ./limit-provenance.yaml

seasonal-snapshot:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: '#/snapshot-slim'
- type: object
properties:
season-name:
$ref: ./season-name.yaml
day-night:
$ref: ./day-night.yaml

seasonal-snapshot-detailed:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: '#/seasonal-snapshot'
- type: object
properties:
proposals-considered:
description: |
The seasonal ratings proposals considered when determining the
seasonal ratings of a power system resource, e.g., a line or
transformer.
type: array
minItems: 1
maxItems: 10
items:
allOf:
- $ref: '#/seasonal-proposal'
- type: object
properties:
source:
$ref: ./data-provenance.yaml
resource-id:
$ref: ./resource-id.yaml
required:
- source
- resource-id
required:
- proposals-considered
89 changes: 89 additions & 0 deletions docs/_data/components/schemas/seasonal-rating-period.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
proposal:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: 'forecast-limit-period.yaml#/proposal'
- type: object
properties:
season-name:
$ref: ./season-name.yaml
day-night:
$ref: ./day-night.yaml

proposal-slim:
type: array
title: Seasonal Period Proposal slim
maxItems: 20 # (max continuous + emergency ratings) * max num fields in limit type, e.g. MW and p.f.
minItems: 1
items:
type: number
title: Continuous and Emergency Ratings values
description: |
Each number in this array corresponds to a value of the continuous and
emergency ratings for a particular period. The first values correspond to
the continuous (normal) rating and the subsequent values correspond to the
emergency ratings in order of decreasing duration. The durations are
defined in the `proposal-header.default-emergency-durations` field.
The exact number of values in this array is further determined by the
`proposal-header.limit-type` field. If the `limit-type` is a single value
like "Apparent Power", e.g., `{"mva":1}`, then the array will have a
single value for each rating. For example, if there was only one emergency
duration defined, then the array would have two values, e.g. `[50, 55]`,
corresponding to a 50MVA continuous rating and 55MVA emergency rating,
respectively.
However, if the `limit-type` is an "Active Power and Power Factor", e.g.,
`{"mw":1, "pf":1}`, then the array will have two values for each rating.
If we continue with the example of having only one emergency duration
defined, then the array would have four values. Thus, instead of
`[normal_MVA, emergency_MVA]`, we would have `[normal_MW, normal_pf,
emergency_MW, emergency_pf]`, e.g., `[300, 1.0, 350, 1.0]`.
snapshot:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: 'forecast-limit-period.yaml#/snapshot-slim'
- type: object
properties:
season-name:
$ref: ./season-name.yaml
day-night:
$ref: ./day-night.yaml

snapshot-detailed:
type: object
description: Proposes the continuous and emergency ratings for the specified Season.
title: Seasonal Rating Proposal
allOf:
- $ref: '#/snapshot'
- type: object
properties:
proposals-considered:
description: |
The seasonal ratings proposals considered when determining the
seasonal ratings of a power system resource, e.g., a line or
transformer.
type: array
minItems: 1
maxItems: 10
items:
allOf:
- $ref: '#/proposal'
- type: object
properties:
source:
$ref: ./data-provenance.yaml
resource-id:
$ref: ./resource-id.yaml
required:
- source
- resource-id
required:
- proposals-considered

0 comments on commit 98801dd

Please sign in to comment.