Using the Ramp Up/Down Rates in the ED Model. I’ve attempted to reinstate this one, since such an important technical constraint of the generators shouldn’t be left out of the modelling of a system. However, since for the case I’ve worked on the ramp rates were high enough to be modelled as Inf, no extensive testing was done to check if the reintegration was working properly; Using Hot Start Cost. As of right now, the toolbox only uses the Cold Start Cost, however the Hot Start Cost was still an input in some functions so, when developing the GUI, it was left as a customizable field when adding an entry. The original code had three options: Using only the Cold Start Cost (similarly to what the toolbox is currently doing); Using the Hot Start Cost (there would only be a start cost if the generator had been working previously and was shut down for a short period; A cost curve between the two values (that started in the Cold Start Cost and would tend to the Hot Start Cost), depending on the previous usage of the generator when it was started. This represented the best modelling option and reinstating it would probably improve modelling accuracy. Other types of fuel consumption curves, namely, a second degree polynomial or an exponential curve. The slots correspondents to these values are still available in the gen_data matrix. Implementing these (and more types of curves if necessary) would also probably improve modelling accuracy and the range of thermal generators that can be modelled. It would, however, require severe modifications to the Fuel Characteristics Window, as well as to the ED Model optimization (currently done using “fmincon”, inside the “production_ED.m” and “production.m” functions); Adding new features As mentioned, over the course of my work on this toolbox, there were ideas for implementing some features that were eventually left aside. This is obvious looking at some fields that are not used in the model, or buttons that do nothing at all (the dreaded N.I.). Here I will attempt to convey the ideas that were originally going to be put in practice in those places, in the hope that someday they are. There are also some suggestions that not got past the “idea” phase.
Using the Ramp Up/Down Rates in the ED Model. I’ve attempted to reinstate this one, since such an important technical constraint of the generators shouldn’t be left out of the modelling of a system. However, since for the case I’ve worked on the ramp rates were high enough to be modelled as Inf, no extensive testing was done to check if the reintegration was working properly; Using Hot Start Cost. As of right now, the toolbox only uses the Cold Start Cost, however the Hot Start Cost was still an input in some functions so, when developing the GUI, it was left as a customizable field when adding an entry. The original code had three options: Using only the Cold Start Cost (similarly to what the toolbox is currently doing); Using the Hot Start Cost (there would only be a start cost if the generator had been working previously and was shut down for a short period; A cost curve between the two values (that started in the Cold Start Cost and would tend to the Hot Start Cost), depending on the previous usage of the generator when it was started. This represented the best modelling option and reinstating it would probably improve modelling accuracy. Other types of fuel consumption curves, namely, a second degree polynomial or an exponential curve. The slots correspondents to these values are still available in the gen_data matrix. Implementing these (and more types of curves if necessary) would also probably improve modelling accuracy and the range of thermal generators that can be modelled. It would, however, require severe modifications to the Fuel Characteristics Window, as well as to the ED Model optimization (currently done using “fmincon”, inside the “production_ED.m” and “production.m” functions); Adding new features As mentioned, over the course of my work on this toolbox, there were ideas for implementing some features that were eventually left aside. This is obvious looking at some fields that are not used in the model, or buttons that do nothing at all (the dreaded N.I.). Here I will attempt to convey the ideas that were originally going to be put in practice in those places, in the hope that someday they are. There are also some suggestions that not got past the “idea” phase.