Conversion assets with multiple inputs and outputs

[aporrasc]

Description

I guess that to model an asset that converts inputs into outputs you would have to create relationships using the flow table.
In case of conversion, when you model the capacity of the asset, where do you apply that capacity? in the flow before applying the efficiency or in the flow after using the efficiency?
In case of having several outputs, it would be very nice to have the capability to define relationships between them, i.e. from_asset-CCGT---to_asset-electricity flow = 1.73 from_asset-CCGT---to_asset-CO2 flow. The same between inputs.

For example, in the industrial sector the processes have many inputs and as ouputs the process itself and emissions, and in exceptional cases CO2 captured. Often it is not intuitive to calculate this CO2 captured based on the inputs and the references are given based on the tons of product produced.

Hope you find this useful.

Target audience

• End users

[datejada]

Thanks @aporrasc! Regarding your questions:

1. We apply the capacity constraint to the sum of all outputs times a coefficient. So, if an output is CO2, you can have a capacity coefficient of zero and then it won't be included in the capacity constraint. See, https://tulipaenergy.github.io/TulipaEnergyModel.jl/dev/20-how-to-use/#coefficient-for-capacity-constraints
2. We are developing the feature to create the flows relationships (see Implement relationships for Multiple Inputs Multiple Outputs (MIMO) of an asset #596) so you can have an output of CO2 emissions (with a zero coefficient for the capacity constraint) and then when this feature is ready you can create a relationship between either another output or an input to the CO2 output with a fix ratio to calculate the CO2 emissions.

Let us know, if still I am missing something :)

The fixed ratio flows relationship is being developed, so it should be available in the following months (before June...maybe before...). Please keep an eye on the upcoming releases.

[clizbe]

Thanks for the feedback @aporrasc! I'm moving this to a Q&A discussion. :)