Future possible extensions (new features)

[datejada]

These are some ideas of future possible extensions (new features) we can have in the model that are not yet in our current pipeline, depending on the users' needs:

• Include other objective functions like maximising revenues given a set of electricity prices.
  • Multi-objective (include societal benefit, land use, etc)
• Add one-way or two-way contracts for difference (CfDs) for an asset's bidding to determine the asset's revenues in the model.
• Longterm contracts for hybrid assets (maybe similar to above?)
• Add Flow-based market coupling (FBMC) feature using PTDFs (useful for EU runs).
• Consider HVDC cables in the formulation of the DC-OPF.
• Negative electricity prices (if not already in the pipeline)
• Export of final problem (obj, vars, consts) for user to check/view - relevant once multi-detail & optional constraints
• Run model unattended on a server/cluster
• Rough estimate of run-time before you run (mins, hours, days) - I think this is nicer/simpler than a progress bar - maybe we can get a feel for this based on the features selected (ramping, clustering, etc) and problem size? Then as people use Tulipa we could get feedback and adjust our estimate? 8D
• Way of creating input files (or DDB table) that only include necessary columns, based on analysis settings. We've already agreed the user should create an analysis settings file to explicitly communicate what they are trying to do - we can use it for validation and model settings. Maybe creating the template could be a few functions in TulipaIO, such as:
  • create_template_file ( file_type, analysis_settings ) : Create a blank file of file_type with all necessary columns for whatever analysis settings the user sets, such as "include investment" or "use clustering" or "use flex temp res".
  • create_all_template_files ( analysis_settings ) : Creates all files for analysis based on analysis_settings, calling create_template_file for each.
  • add_feature_columns( analysis_settings or new_analysis_setting ) : Same as above but edits existing files to add columns for a new feature. Should probably include user feedback to say what it added and where. Maybe they can specify for one file or if it's blank it adds to all relevant files.