tespy
tespy copied to clipboard
Package revisions
- [ ] Similar to oemof/oemof-solph/pulls/793 future revisions should consider private and public API.
- [ ] The structure of input data, processing/solving and output data could be adjusted to pandas/numpy like data structures.
- [ ] Algorithms for starting value generation shoudl be improved.
- [x] Renaming of some components:
- [x] HeatExchangerSimple -> SimpleHeatExchanger
- [x] CombustionChamber -> SimpleCombustionChamber/AdiabaticCombustionChamber
- [x] DiabaticCombustionChamber -> CombustionChamber
- [x] Renaming of some modules:
- [x] heat_exchangers
- [x] heat_exchanger_simple.py -> simple.py
- [x] heat_exchanger.py -> base.py (???)
- combustion
-
combustion_chamber_stoich.py -> stoichiometric.py - [x] combustion_chamber.py -> adiabatic.py/simple.py
- [x] combustion_engine.py -> engine.py
-
- [x] heat_exchangers
- The unit system should get a major rework and include units for component properties
- Rework docs
- [x] Fresh look
- [x] Improved structure
Perhaps https://pint.readthedocs.io/en/stable/index.html could be useful for the unit definitions and conversions?
- The fluid property back end should be changed in a way, that the CoolProp AbstractState object which is used to call the fluid property functions is tied to the network object. By this, it will be easier
- to implement different fluid property back ends and use them simultanously in a single model (see #327, #302)
- to allow paralllel processing (if copies of a network are made, see #343)
- Make use of more generic base classes #219