Comments (3)
@canafarci the latent heat of evaporation is a constant, so it shouldn't be changing.
Can you provide the epw and input files you are using so I can try to reproduce it on my end?
from uwg.
Of course,
EPW i have used is here, it is from Ankara, Turkey
and the scipt i have used is this, , on my end i receive the above mentioned error on day 87
from uwg.
The problem does lie with the indoor_hum
, but it's not because of the latent heat of evaporation which is in fact constant through everything. It's because the calculated latent impact of dehumidification gets larger at every timestep during the cooling season because the cooling airflow rate is maxed out. In turn, this is because:
- The sensible cooling demand is larger then the cooling capacity of your hvac system
- The sensible cooling demand is calculated for an indoor air temperature below the cooling supply air temperature.
(2) itself causes an interesting dynamic, where the calculated airflow rate is negative (since T_indoor
is less than the supply air temperature), but the change in humidity is also negative (since 'indoor_hum' is less than the supply air humidity), so the dehumidification demand (airflow rate x density x latent heat of evaporation x delta humidity) is a large positive number, that dwarfs latent energy gains and so continually dries out the indoor air until it hits zero.
And the culprit behind the maxed out cooling demand is the schedules you're defining in your script for the cooling and heating setpoints:
default_week = [[0.15] * 24] * 3
schdef1 = SchDef(elec=default_week, gas=default_week, light=default_week,
occ=default_week, cool=default_week, heat=default_week,
swh=default_week, q_elec=18.9, q_gas=3.2, q_light=18.9,
n_occ=0.12, vent=0.0013, v_swh=0.2846, bldtype='midriseapartment',
builtera='new')
According to this, the cooling and heating setpoints are 0.15C. Both heating and cooling seasons thus attempt to mechanically condition the indoor air to an extremely low temperature. This isn't a problem during the heating season since UWG simply adds the appropriate (efficiency-adjusted) heat energy to the zone thermal balance and ignores any energy associated with dehumidification. But once the cooling season starts (day 87), the dehumidification demand is calculated and conflicts with the way the UWG models cooling via an HVAC air system. Basically, the UWG attempts to calculate a supply airflow rate that can meet the cooling demand, and incorporates the dehumidification energy into the evolution of the indoor humidity, which is why we eventually get the error with the psychrometric calculations.
On your end, you can fix this simply be fixing your setpoint temperatures (in Celsius) in your schedule. I realize this was likely copied from an example script I made, so fyi those values are dummy values for testing and aren't meant to represent real values. You can find real representative values in the DOE reference buildings include in UWG.
I'm also going to add some checks in the code to make sure this doesn't happen again. I've already a numerical range check to the setpoint schedules, but I think I'll also raise an exception if the indoor temperature ever goes below the supply air temperature during the cooling demand calculations, since that breaks UWG's assumption that mechanical cooling is only used when indoor temperatures are above the supply air temperature (i.e. below that you get negative airflow rates, and humidity ratios), and there are a bunch of user-exposed parameters in the cooling demand calculation that can cause this behaviour again. I can't think of a similar threshold to use for the heating season, even though a ~0C heating setpoint doesn't make sense, technically nothing breaks the underlying physics assumptions, so I'll leave it as is.
I also realize now that the indoor temp/humidity parameters in the building object aren't set with the getter/setter pattern, which is why the physically impossible condition of negative humidity didn't throw a setter exception, which is an easy fix.
from uwg.
Related Issues (20)
- Cannot run the example file HOT 14
- albroof and c_exch on daily maximum air DB temperature in UC HOT 1
- Add a log file option to the CLI commands
- Possible error in uwg.py HOT 2
- Ventilation and infiltration definitions in building.py HOT 1
- buildings area HOT 1
- Example UWG file in resources is out of date HOT 5
- Possible bug on Sensible Cooling/Heating demand calculation HOT 1
- Nightlimit issue HOT 6
- Error in saturation_pressure calculation HOT 7
- Error mediumoffice HOT 2
- UWG Processor HOT 1
- computation of verTohor
- dragonfly_UWGBldgTypes
- Parameter
- Anthropogenic heat calculation from traffic
- canyon orientation in solarcalcs.py
- DIR_DOE_PATH issue
- UWG - places without buildings
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from uwg.