Closed MADNANTARRAR closed 2 weeks ago
This feature is not currently supported by GenX. The GenX code currently assumes an hourly resolution for each time step. This makes conversion from energy production/consumpion during each time step in MWh per hour to capacity in MW trivial, as they are equivalent.
To implement this feature, one would need to insert appropriate scaling factors at numerous locations in the code. If someone wants to tackle this enhancement, they are welcome to do so and submit a PR for review and possible consideration in the core GenX code base.
At this point, we do not plan to support this in the near-term. We will consider it at an appropriate future point, especially when implementing a planned parallelized Benders' decomposition solution method (described in this work https://doi.org/10.1287/ijoo.2023.0005) that will enable much higher number of operational time steps. At that point, it may make sense to enable sub-hourly resolution for some use cases.
In the meantime, we will remove this text in the documentation for demand.csv, as we do not provide user support for this use case:
"With some care and effort, finer (e.g. 15 minute) or courser (e.g. 2 hour) time steps can be modeled so long as all time-related parameters are scaled appropriately (e.g. time period weights, heat rates, ramp rates and minimum up and down times for generators, variable costs, etc)."
Thanks for explanation.
From: Jesse Jenkins @.> Sent: Friday, 21 June 2024 12:46 AM To: GenXProject/GenX.jl @.> Cc: Muhammad Adnan @.>; Author @.> Subject: Re: [GenXProject/GenX.jl] How to set different time resolution in GenX[Question]: (Issue #707)
This feature is not currently supported by GenX. The GenX code currently assumes an hourly resolution for each time step. This makes conversion from energy production/consumpion during each time step in MWh per hour to capacity in MW trivial, as they are equivalent.
To implement this feature, one would need to insert appropriate scaling factors at numerous locations in the code. If someone wants to tackle this enhancement, they are welcome to do so and submit a PR for review and possible consideration in the core GenX code base.
At this point, we do not plan to support this in the near-term. We will consider it at an appropriate future point, especially when implementing a planned parallelized Benders' decomposition solution method (described in this work https://doi.org/10.1287/ijoo.2023.0005) that will enable much higher number of operational time steps. At that point, it may make sense to enable sub-hourly resolution for some use cases.
— Reply to this email directly, view it on GitHubhttps://github.com/GenXProject/GenX.jl/issues/707#issuecomment-2180894531, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGURGR3U3OH7JBMM5367J43ZILTNVAVCNFSM6AAAAABJTJA62OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQHA4TINJTGE. You are receiving this because you authored the thread.Message ID: @.***>
Question
As mentioned in the User Guide/Model Inputs section of the GenX documentation, we can model our time steps for 15 minutes or 2 hours. What changes should we make in the settings or in the code to conduct a study with these time steps?
Additional context
No response