De list of assetflowcategories (AFC) now has 'duplicates' of batteryCharging and batteryDischarging, or similar entries for EVs.
We would like these to be removed and to have seperate bookkeeping for production and consumption analogous to the bookkeeping of energycarriers.
This would probably imply that the base J_EA would get two fields, one for the input AFC and one for the output AFC. Assets such as the J_EAProduction or J_EAConsumption are clear in which of those AFC they use so when the AFC is passed into the constructor the rest of the implementation need not worry about the other field. (It can be left null)
J_EAStorage would still need only one AFC in its constructor as the input and output AFC are the same?
For J_EAs such as the J_EAConversion the constructor could be passed two AFCs.
De list of assetflowcategories (AFC) now has 'duplicates' of batteryCharging and batteryDischarging, or similar entries for EVs.
We would like these to be removed and to have seperate bookkeeping for production and consumption analogous to the bookkeeping of energycarriers.
This would probably imply that the base J_EA would get two fields, one for the input AFC and one for the output AFC. Assets such as the J_EAProduction or J_EAConsumption are clear in which of those AFC they use so when the AFC is passed into the constructor the rest of the implementation need not worry about the other field. (It can be left null)
J_EAStorage would still need only one AFC in its constructor as the input and output AFC are the same?
For J_EAs such as the J_EAConversion the constructor could be passed two AFCs.