Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam distribution systems #124

Open
kwakuwulf opened this issue Nov 3, 2016 · 5 comments
Open

Steam distribution systems #124

kwakuwulf opened this issue Nov 3, 2016 · 5 comments

Comments

@kwakuwulf
Copy link

As discussed in Vienna I'm adding some issues from the viewpoint of industrial process modelling:

I was wondering how one would define a steam system in the EnergyADE. Two areas of concern:

  • ThermalDistributionSystem: most distribution system in industries are based on steam. For that purpose the returnTemperature and supplyTemperature are insufficient information. The pressure of the supply line and the condensate return percentage would be important information. Maybe we could add another inheritance to EnergyDistributionSystem named SteamDistributionSystem that specifically addresses the requirements of steam distribution and does not affect the "normal" distribution systems of buildings.
  • Similary a SteamBoiler could be added to EnergyConversionSystems to allow a more specific definition of a steam boiler
@RomainNouvel
Copy link

RomainNouvel commented Nov 4, 2016

  • Then, we could replace the general ThermalDistributionSystem by a LiquidDistributionSystem and a SteamDistributionSystem. Are all existing attributes of ThermalDistributionSystem relevant (although not sufficient) for SteamDistributionSystem? If not, we could create inherited classes.
  • which additional SteamBoiler attributes would you like to add?
  • Should we also adapt the ThermalStorageSystem definition in relation to Steam? Are further attributes necessary for it?

@RomainNouvel
Copy link

For non-reisdential buildings (and american residential building), we might miss also a AirDistributionSystem solution, with attributes different from those of other EnergyDistributionSystem...

@mlauster mlauster self-assigned this Dec 5, 2016
@mlauster mlauster added this to the v0.8.0 milestone Dec 5, 2016
@mlauster
Copy link
Contributor

mlauster commented Dec 7, 2016

@kwakuwulf, are all attributes of the current ThermalDisributionSystem applicable for steam systems? For me it looks like this. Then I would propose leave the ThermalDisributionSystem as it is and add attributes nominalPressure, pressureDrop, supplyTwoPhaseRatio and returnTwoPhaseRatio. @RomainNouvel, what for attributes would you like to add for AirDistributionSystems?
For ThermalStorageSystem, we could add nominalPressure and twoPhaseRatio.
In consequence, we should split our energy conversion systems inheritances into thermal and electrical, e.g. by adding ElectricalConversionSystem with attribute voltage and nominalCurrent as inheritance of EnergyConversionSystem with inheritances to _SolarEnergySystem and CombinedHeatPower. Then a ThermalConversionSystem with attributes nominalPressure, pressureDrop, supplyTemperature, returnTemperature, supplyTwoPhaseRatio and returnTwoPhaseRatio as inheritance of EnergyConversionSystem with inheritances to Boiler, ElectricalResistance, HeatPump, CombinedHeatPower, DistrictNetworkSubstation and MechanicalVentilation.

So our module gets more complex if we really want to describe multi-phase flows, for what we need temperatures and pressure of all subsystems. Any opinions on that?

@mlauster mlauster removed this from the v0.8.0 milestone Dec 7, 2016
@mlauster
Copy link
Contributor

mlauster commented Dec 7, 2016

I think we should skip this for v0.8 and discuss this in more detail.

@mlauster
Copy link
Contributor

mlauster commented Jul 3, 2017

Let's first see the impacts of #137, we could pick up that topic here later again with this new structure. Will not be part of v0.9.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants