Académique Documents
Professionnel Documents
Culture Documents
Summary
In this report, HAMLab (Heat, Air & Moisture simulation Laboratory) applications for
Common Exercise 1 (CE1) are given. The aim of this report is to provide practical
information on how HAMLab can be used for CE1. Detailed descriptions of the used models,
model assumptions, parameters, etc, can be found in Annex report: TUE Oct2004 PaperA41-
T1-NL-04-3.pdf. Section 1 start with a short introduction on the use of HAMLab. The next
Sections show details of the modeling and simulations of CE1. Appendix A&B contain the
complete HAMBase input file for Case 600_Open. Appendix C contains the complete
FemLab input file for Case 600_Open.
1 Introduction of HAMLab
The roots of the current HAM building model appeared in 1988 called ELAN [de Wit &
Driessen 1988]. This model was originally programmed in Fortran and simulated heat flows
in a multizone building with a hourly based time step. The next improvement was the
development of moisture transport model called AHUM [de Wit and Donze 1990] and
integration of both models (ELAN & AHUM) in MatLab called WaVo. (in dutch Warmte en
Vocht; i.e. Heat and Moisture). Because the aim is to integrate building component models
and systems models, it became necessary to adapt the WaVo building model so it could also
handle small time steps. This major recent improvement is realised using SimuLink and is
called HAMBase. Together with the early WaVo model this improvement is presented in
Oct2004 PaperA41-T1-NL-04-3.pdf. WaVo can be used as a starting tool to simulate and
evaluate indoor climates according corresponding building designs. The output gives hourly
values for the indoor temperature, Rh, energy and mass flows. Using only WaVo, already a
great variety of buildings and systems can be simulated with sufficient accuracy. In case more
modeling accuracy is needed for building systems and/or building details, the WaVo model
can be exported to SimuLink into a HAMBase model. This HAMBase model can further
refined in the MatLab/SimuLink/FemLab environment by using the currently developing
HAM modeling and simulation laboratory (HAMLab). Important criteria for such a modeling
and simulation environment are discussed now.
1
The next facilities play an important role for the development of a HAMLab:
- Laboratory simulation environment It is important that the simulation environment
contains functions for a) quick evaluation of results, such as plotting facilities, statistical
functions, etc., b) basic HAM supporting calculations, such as properties of moist air,
dewpoint, etc. and c) quick importing of data.
- HAM building modeling This is a key facility. The type of model simulates the heat, air
and moisture transport in building zones and constructions. Because the aim is to integrate
building component models and systems models, it is important that the building models can
also handle small time steps
- HAM systems modeling This is another key facility. An important property to take into
account is the relative fast dynamics of systems, which can be in the order of seconds.
- Controllers modeling Because almost all systems have some type of controller it is
important that common controller types on/off, and PI controllers are included.
- Integration of ODE and PDE based models- This is very important feature if new models
have to be integrated. Most HAM systems can be modeled by ODEs. Furthermore if
geometrical aspect plays a dominant role, for example HAM transport in constructions or
airflow in and around buildings, it is crucial that general PDE based models can be included.
Also transparency and flexibility are important.
- Transparency of modeling A clear relation between the physics of models (mathematical
description in terms of ODEs, PDEs and initial/boundary values) and computer code of
models is important for a) implementing new models and b) validation of models.
- Optimization The simulation results of indoor climate models are dependent on a set of
parameters. To create an optimal climate and taking durability and economics into account it
is necessary have an optimization tool. This tool is capable of selecting a optimal set of
parameters given an object function and constraints.
The modeling philosophy of HAMLab is top-down and based on: Start with the main
contribution (the indoor climate), refine only when necessary. The next steps explain this
philosophy in more detail:
1) Start simulating the indoor climate with WaVo, export to SimuLink
2) Check model assumptions, if necessary improve the model.
For example: HAMBase has a model assumption that the Rh in constructions stays
within 20<Rh<90. The HAMBase model can be improved by the coupling of a
FemLab model to investigate this model assumption.
3) Validate model, if necessary adapt parameters
4) Ready to use for further research or design problems
2
The modeling strategy of HAMLab is shown in figure 1:
WaVo
Model
SimuLink
Model
improve model using
- HAMSys
Check model assumptions
- HAMDet
Model
OK ? N
Adapt parameters
Validate model
Parameters
OK ? N
READY
For further use
2.1 Input
We start with a WaVo model for the Case 600_Open geometry. In appendix A the necessary
input mfile for WaVo without comments is given. In appendix B the same model with
comments is given so the reader can understand the syntax. For example in Appendix A you
find (first line) BASE.Period=[1872,1,1,365]; In Appendix B you can find the syntax:
3
% FORMAT BASE.Period=[yr,month,day,ndays]
%
% yr = start year
% month = start month
% day = start day
% ndays = number of days simulated
The reader should now be able to understand the model in Appendix A by reading Appendix
B. Additional information is given now for a) the import of climate data and b) the import of
material data other than the default present data.
4
The next table shows the corresponding new WaVo material numbers for each CE1 material
` c bv nr
0.16 395 1880 0.9 2.1 101 19; 651
0.04 12 840 0.9 1.5 0.34 5.8; 652
0.04 55 1880 0.9 1.4 14 8.8; 653
0.14 530 900 0.9 2.1 101 19; 654
0.14 650 1880 0.9 2.1 101 19; 655
0.04 80 840 0.9 1.5 0.34 5.8; 656
0.14 530 1880 0.9 95 120 3.1; 657
0.51 2300 840 0.9 120 90 2.4; 658
0.04 10 1400 0.9 18 1.2 0.7; 659
1.13 2300 840 0.9 120 90 2.4; 660
0.16 950 840 0.9 7.8 42 6.4; 661
200 2800 840 0.9 700000 0 0 662
200 2800 840 0.9 700000 0 0 663
0.16 395 1880 0.9 4200 101 19; 664
0.14 650 1880 0.9 1850 101 19; 665
2.2 Output
The output is shown in figures 2.1 2.6.
5
Figure 2.1 The external temperature
6
Figure 2.3 The internal air temperature
7
Figure 2.5 The mean RH in the walls
8
Figure 2.7 The heating and cooling load
9
3 Case 600_0A
3.1 Input
The previous model of appendix A has been changed for this case and exported to SimuLink.
An analytical model is also made for comparison. The models are shown in the next figure:
Figure 3.1 HAMBase model and exact first order model for Case 600_OA
The next changes of the model of Appendix A are made for this case
10
3.2 Output
Figure 3.2 shows the simulation result:
4 Case 600_OB
4.1 Input
Again the model of appendix A has been changed for this case and exported to SimuLink.
The model is shown in the next figure:
11
Figure 4.1 HAMBase model for Case 600_OB
This model is the same as Appendix A, accept that again the climate date are changed to
steady state (analog to step 3 of previous Section)
4.2 Output
Figure 4.2 shows the simulation result:
12
5. Case 600_Open revisit
Already a first simulation of indoor temperature, Rh and heating/cooling load has been done
in Section 2. A next step is a detail 1D simulation of the roof. The reason is twofold:
1) calculating the requested Rh as well as the heat flux through the roof
2) checking the model assumption of HAMBase that the moisture transport is dominated by
vapor transport
5.1 Input
FemLab is used as for solving this coupled heat and moisture problem. In Appendix C the
complete mfile for the detail 1D simulation of the roof is given. More details about this
approach can be found in [Schijndel 2003a].
5.2 Output
The output is shown in figures 5.1 5.5
13
Figure 5.2 The Rh at x=0.01 in the roof
14
Figure 5.4 The Rh at the external surface of the roof (x=0.1408)
Figure 5.5 The heatflux (without latent heat) from the room air to internal surface of
the roof
15
6. Case 600_Open Paint&VR
6.1 Input
Again the mfiles of Appendix A & C are used as a starting point. The next adaptations of
these files are made for this case.
WAVO, Compared with appendix A, the construction data are now
BASE.Con{1} = [0.121, 0.012,664, 0.066, 653, 0.009,654, 0.034, 0.6, 0.9];
BASE.Con{2} = [0.121, 0.025,665, 1.003, 656, 0.034, 0.6, 0.9];
BASE.Con{3} = [0.121, 0.010,664, 0.1118,653, 0.019,657, 0.001,663, 0.034, 0.6, 0.9];
16
Figure 6.2 The internal Rh
17
Figure 6.3 The mean wall Rh
18
Figure 6.5 The Rh at the internal surface of the roof (x=0)
19
Figure 6.7 The Rh at x=0.1218 in the roof
20
Figure 6.9 The heatflux (without latent heat) from the room air to internal surface of
the roof
21
7. Case 900_Open
7.1 Input
Again the mfiles of Appendix A & C are used as a starting point. The next adaptations of
these files are made for this case.
WAVO, Compared with appendix A, the construction data are now
BASE.Con{1} = [0.121, 0.100,658, 0.0615,659, 0.009,654, 0.034, 0.6, 0.9];
BASE.Con{2} = [0.121, 0.080,660, 1.007, 656, 0.034, 0.6, 0.9];
BASE.Con{3} = [0.121, 0.010,661, 0.1118,653, 0.019,657, 0.001,663, 0.034, 0.6, 0.9];
22
7.2 Output, The output is shown in figures 7.1 7.9
23
Figure 7.3 The mean wall Rh
24
Figure 7.5 The Rh at the internal surface of the roof (x=0)
25
Figure 7.7 The Rh at x=0.1218 in the roof
26
Figure 7.9 The heatflux (without latent heat) from the room air to internal surface of
the roof
27
8. Discussion and Conclusions
In this report the application of HAMLab on common exercise 1 is presented. The included
models are capable to simulate all requested outputs except the heat flow through the ceiling
with latent heat. Case 600_0A agrees well with an analytical solution. Validation data for all
other cases are not present. Our modeling strategy implies that modeling refinements are only
considered when absolute necessary. For this reason, a linear modeling approach for the heat
and moisture transport in the roof has been used. If necessary this modeling can be further
improved by
1) more accurate modeling of moisture dependencies of the material properties as presented in
[Schijndel 2003a]
2) using a more sophisticated modeling approach (for example HAMSTADT) and taking
latent heat into account as presented in [Hagentoft et all]
3) full coupling between HAMBase and FemLab, instead of the post processing used in this
report as presented in [Schijndel 2003c]
4) 2D and 3D modeling as presented in [Schijndel 2003a]
LITERATURE
Hagentoft, C.-E.; Kalagasidis, A.S.; Adl-Zarrabi, B; Roels, S.; Carmeliet, J.; Hens,
H.; Grunewald, J.; Funk, M.; Becker, R.; Shamir, D.; Adan, O.; Brocken, H.; Kumaran, K.;
Djebbar, R. 2004. Assessment Method of Numerical Prediction Models for Combined Heat,
Air and Moisture Transfer in Building Components: Benchmarks for One-dimensional Cases.
Journal of Thermal Envelope and Building Science, Vol. 7 (4), pp. 327-352.
Schijndel, 2003a, A.W.M. van, Modeling and solving building physics problems with
FemLab, Building and Environment 38, pp319-327
Schijndel, A.W.M. van et all, 2003b, Optimal setpoint operation of the climate
control of a monumental church, Sec. Int. Building Physics conference Leuven, pp777-784
Schijndel, 2003c, A.W.M. van, Integrated building physics simulation with
FemLab/SimuLink/Matlab, 8TH Int. IBPSA Conf. Eindhoven August 2003, pp1177-1184
Wit M.H. de and H.H. Driessen, 1988, ELAN A Computer Model for Building
Energy Design. Building and Environment, Vol.23, No 4, pp.285-289
Wit, M.H. de, 2001, WaVo, a simulation model for the thermal and hygric
performance of a building, Univ. of Tech. Eindhoven, group FAGO.
28
Appendix A. HAMBase input file Case 600_Open without comments
BASE.Period=[1872,1,1,365];
BASE.DSTime=0;
BASE.Vol{1}= 8*6*2.7;
BASE.shad{1}=[
4 20 30 40 50 60 70 80 ;...
5 787/789 784/789 775/789 754/789 700/789 563/789 302/789];
BASE.Ers{1} =300;
BASE.dayper{1}= [ 0, 9, 17 ];
BASE.vvmin{1}= [ 0.41, 0.41, 0.41 ];
BASE.vvmax{1}= [ 0.41, 0.41, 0.41 ];
BASE.Tfc{1}= [ 300, 300, 300 ];
BASE.Qint{1}= [ 200, 200, 200 ];
BASE.Gint{1}= [ 0, 1.3889e-004, 0 ];
BASE.Tsetmin{1}= [ 20, 20, 20 ];
BASE.Tsetmax{1}= [ 27, 27, 27 ];
BASE.RVmin{1}= [ -1, -1, -1 ];
BASE.RVmax{1}= [ 100, 101, 100 ];
BASE.Plant{1}=[1e6,-1e6,0,0];
BASE.convfac{1}=[1, 1, 1];
BASE.heatexch{1}=[0 100];
BASE.furnishings{1}=[0, 0.2];
[Control,Profiles,InClimate,InBuil]=Hambasefun(BASE);
29
% Adjust for Bestest climate
InClimate.LAT=39.8;
%LSMLON=LSM-LON;
LSM=-105;
LON=-104.9;
InClimate.LSMLON=LSM-LON;
InClimate.gref=0.2;
InClimate.nin=10;
InClimate.kli(:,4)=8*InClimate.kli(:,4)/100;
InBuil.oriennr=[1:5];
%****************CALCULATION*****************************
Output=Wavox0304(Control,Profiles,InClimate,InBuil);
30
Appendix B HAMBase input file Case 600_Open with comments
% ------------------------------------------------------------------------------
% PART 1 : THE CALCULATION PERIOD
% -------------------------------------------------------------------------
% The available climate data of De Bilt are of the years 1971 till 2000. If the
% climate files of a different location are used the name and format must be
% adapted and the geographical coordinates must be changed (in InClimate-file).
% As an average year can be considered 1 May 1974 till 30 April 1975.
% A cold winter (242 days) started 1 September 1978.
% A hot summer (123 days) started 1 May 1976.
% 9 hot days started 1 at July 1976 and 9 cold days started at 30 Dec. 1978.
%
% FORMAT BASE.Period=[yr,month,day,ndays]
%
% yr = start year
% month = start month
% day = start day
% ndays = number of days simulated
%BASE.Period=[1976,1,1,90,1];
BASE.Period=[1872,1,1,365];
BASE.DSTime=0;
% ------------------------------------------------------------------------- ---
% PART 2 : THE BUILDING
% ------------------------------------------------------------------------- ---
31
% outdoors and for construction components between zones from the zone with the
% lowest zone-number to the highest so: 1->2,1->3,2->3etc.. The material
% properties of the component layer are inserted by a material ID-number. By
% typing 'help matpropf' a list of materials appear with a material ID-number.
% Also each different construction component gets a different construction
% ID-number: conID=1,2,....
%
% FORMAT BASE.Con{conID}=[Ri,d1,matID,...,dn,matID,Re,ab,eb].
% dn = material layer thickness [m]
% matn = material ID-number.
% Ri = internal surface heat transfer resistance (for example Ri=0.13) [Km2/W]
% Re = surface heat transfer resistance at the opposite site (for example Re=0.04) [Km2/W]
% ab = external solar radiation absorption coefficient [-] e.g.light ab=0.4, dark ab=0.9.
% eb = external longwave emmisivity [-]. Almost always: eb=0.9
% Comments
% Glazing 1 saint-roch skn 165
% Glazing 2 single glazing with interior sunblinds
% Glazing 3 HR glazing with interior sunblinds
% Glazing 4 double glazing with interior sunblinds
% ** ORIENTATIONS **
%
% For each surface of the building envelope (exterior walls) the tilt and the
% orientation with respect to the south has to be known. Each different
% orientation gets a different orientation-ID-numbernumber orID.
%
% FORMAT BASE.Or{orID}=[beta gamma]
% beta = tilt (vertical=90,horizontal=0)
% gamma = azimuth (east=-90, west=90, south=0, north=180)
%
%BASE.Or{orID}=[beta, gamma];
32
BASE.Or{1}= [90.0, 180.0 ];
BASE.Or{2}= [90.0, -90.0 ];
BASE.Or{3}= [90.0, 0 ];
BASE.Or{4}= [90.0, 90.0 ];
BASE.Or{5}= [0.0, 0.0 ]; % horizontal roof
% **SHADOW DATA**
%
% For each vertical window the shadow by exterior obstacles can be accounted
% for. The obstacles can have any combination of blocks, cylinders and spheres,
% provided some limitations regarding the positioning: The position of the
% blocks is such that two planes are horizontal, two vertical and perpendicular
% to the window pane and two parallel. The axis of the cylinder must be
% vertical. E.g. a tree is a cylinder and a sphere. If two equal windows with
% the same orientation and zone have a different shadow they cannot be added to
% one window (with the sum of the surface areas) anymore. Each shadow situation
% gets a shadow ID-number shaID.
%
% FORMAT BASE.shad{shaID}= [
% typenr, size1, size2, size3, x, y, z, extra;
% ......,......,......,......,..,..,..,......;
% typenr, size1, size2, size3, x, y, z, extra;
% typenr, size1, size2, size3, x, y, z, extra;]
%
% x,y,z are Cartesian coordinates where z is vertical and x is horizontal and
% perpendicular to the window plane. Left means left when facing the window from
% outside. The sizes are always positive numbers.
%
% typenr=1 (window):size1=depth (=distance glazing to exterior surface), size2=
% width, size3=height of the window
% [x,y,z] = the coordinates of the lowest window corner at the left side
% extra = elevation-angle of the horizon in degrees to account for far-away
% obstacles.
% typenr=2 (block):size1= width(in x-direction),size2=length(in y-direction),
% size3=height(in z-direction)
% x,y,z] coordinates of the left block corner closest to the window
% extra= solar transmission
% factor (0 opaque)
% typenr=3 (tree):size1=radius crown,size2=radius trunk (e.g.1/20*radius crown),
% size3=height center of crown
% [x,y,z]: coordinates of the bottom of trunk.
% extra=solar transmission factor of crown(0 opaque). In winter(120<iday< 304)
% this is higher than in summer. e.g. winter extra=0.8, summer extra=0.35
% typenr =4 input for incident angle dependency of transmittivity of glazing.
% Perpendicular (angle=0) always 1 and for 90 degrees (parallel) always 0. So
% there is no need for an input for these angles! First row [4, incident
% angle1,.,incident angle7], second row [5, transmittivity1,.,transmittivity7]
%
% Example input
%
BASE.shad{1}=[
4 20 30 40 50 60 70 80
;...
5 787/789 784/789 775/789 754/789 700/789 563/789 302/789];
% Changing '0' into '1' below, gives for one shadow ID-number a drawing of the
% obstacle geometry.
if 1==0
shaID=1;
33
figure(1)
shaddrawf1101(BASE.shad,shaID);
end
% ------------------------------------------------------------------------------
% A building is an assembly of different construction components. The input here
% is about the seize, place in the building and ID of these different components
% (for convenience called walls and windows, so also the doors floors and roofs).
% They are divided into 5 groups:
% I. Constructions separating a zone from the exterior climate: EXTERNAL WALLS
% II. Windows in external walls I
% III. Constructions separating a zone from an environment with a constant
% temperature e.g. the ground: CONSTANT TEMPERATURE WALLS
% IV. Constructions separating a zone from an environment with the same
% conditions: ADIABATIC EXTERNAL WALLS
% V. Constructions between and in zones: INTERNAL WALLS
% For external walls and constant temperature walls the heat loss by thermal
% bridges can be accounted for if the steady state heat loss in Watt per 1K
% temperature difference from these bridges is known. These values can be
% obtained by thermal bridge software or a approximate methods. Use '0' if not
% known.
% -------------------------------------------------------------------------
% I. EXTERNAL WALLS
%
% For each wall ID-number exID=1,2,...
%
% FORMAT BASE.wallex{exID} = [zonenr,surf,conID,orID,bridge];
% zonenr = select zone number from ZONES Section
% surf = total surface [m2], the windows surface area is included
% conID = select construction ID-number from CONSTRUCTION Section.
% orID = select orientation ID-number from ORIENTATIONS Section
% bridge= the heat loss in W/K of the thermal bridges (choose 0 if unknown)
34
BASE.window{1} = [3, 6*2, 1, 1];
%-------------------------------------------------------------------------- --
% PART 3 : profiles for internal sources, ventilation, sunblinds and free
% cooling
% ------------------------------------------------------------------------- ---
%
%
% **PROFILES**
%
% Profiles are related to the use of a zone: office, living room, school etc
% Each day of a week can have a different profile e.g. weekends are different.
35
% Here the profiles are defined and given an ID-number; proID.
% For each day up to 24 different periods can be defined with different data. period1:
% start time = hrnr1 and end time = hrnr2; period2: start time = hrnr2 and end
% time = hrnr3; last period: the hours that are left on the same day.
% for example [1,8,18] means period1: 1h till 8h, period2: 8h till 18h, period 3:
% 24h(==0h) till 1h and 18h till 24h. (3 periods are often used).
% The inserted hours are the clock time.
% The profile allows for free cooling i.e. above a certain threshold Tfc (oC)
% the ventilation is increased from vvmin to vvmax: e.g. vvmax=3*vvmin. So if
% vvmin=vvmax there is no free cooling. The temperature Tfc is also used for the
% control of sunblinds: if the solar irradiance on the window is higher than Ers
% and the indoor temperature higher than Tfc the blinds will be down. This means
% that if there is no free cooling the temperature Tfc is still necessary for
% the control of sunblinds. Ers is the same for all zones. A number often
% encountered for Ers is 300W/m2.
%
% BASE.Ers{proID} = irradiance level for sun blinds [W/m2]
% BASE.dayper{proID} = [hrnr1,hrnr2,hrnr3], the starting time of a new period
% BASE.vvmin{proID} = [. . . ], the ventilation [1/hr], for each period
% BASE.vvmax{proID} = [. . . ], the ventilation [1/hr] in case free cooling
% BASE.Tfc{proID} = [. . . ], treshold [oC] for free cooling, for each period
% BASE.Tsetmin{proID}= [. . . ], setpoint [oC] switch for heating, (in case of
% no heating choose -100)
% BASE.Tsetmax{proID} = [. . . ], setpoint [oC] switch for cooling, (in case
% of no cooling choose 100)
% BASE.Qint{proID} = [. . . ], internal heat gains [W]
% BASE.Gint{proID} = [. . . ], moisture gains [kg/s]
% BASE.RVmin{proID} = [. . . ], setpoint [%] switch humidification,(in case of no
% humidifcation choose -1)
% BASE.RVmax{proID} = [. . . ], setpoint [%] switch dehumidification,(in case
% of no dehumidifcation choose 101)
% proID=1
BASE.Ers{1} =300;
BASE.dayper{1}= [ 0, 9, 17 ];
BASE.vvmin{1}= [ 0.41, 0.41, 0.41 ];
BASE.vvmax{1}= [ 0.41, 0.41, 0.41 ];
BASE.Tfc{1}= [ 300, 300, 300 ];
BASE.Qint{1}= [ 200, 200, 200 ];
BASE.Gint{1}= [ 0, 1.3889e-004, 0 ];
BASE.Tsetmin{1}= [ 20, 20, 20 ];
BASE.Tsetmax{1}= [ 27, 27, 27 ];
BASE.RVmin{1}= [ -1, -1, -1 ];
BASE.RVmax{1}= [ 100, 101, 100 ];
36
BASE.weekfun{1}= [1, 1, 1, 1,
1, 1, 1];
%-------------------------------------------------------------------------- --
% PART 4 : Heating, cooling, humidification, dehumidification
% ------------------------------------------------------------------------- ---
% If the maximum heating capacity is known then that value can be used. If it is
% unknown the value '-1' means an infinite capacity. The value '-2' can be used
% for a reasonable estimate of the maximum heating capacity. If there is no
% cooling the dehumidification capacity is '0' Cooling and dehumification are
% negative! for each zone :
%
% FORMAT BASE.Plant{zonenr}=[heating capacity [W], cooling capacity [W],
% humidification capacity [kg/s],dehumidification capacity [kg/s]];
BASE.Plant{1}=[1e6,-1e6,0,0];
% The simulation program treats radiant heat and convective heat differently.
% For each zone:
%
% FORMAT BASE.convfac{zonenr}=[CFh CFset CFint ];
% CFh =Convection factor of the heating system: air heating CFh=1,
% radiators CFh=0.8 floor heating CFh=0.5, cooling usually CFh=1
% CFset= Factor that determines whether the temperature control is on the air
% temperature (CFset=1), or comforttemperature (CFset=0.6),Tset=CFset*Ta+(1-CFset)*Tr
%
% CFint= is the convection factor of the casual gains (usually CFint=0.5)
BASE.convfac{1}=[1, 1, 1];
BASE.heatexch{1}=[0 100];
BASE.furnishings{1}=[0, 0.2];
37
% BASE in the command window, the input can be checked and changed
%
% In Hambasefun input is changed to an input the simulation program WAVO needs.
[Control,Profiles,InClimate,InBuil]=Hambasefun(BASE);
% The advanced user can modify the files InClimate, InBuil,Profiles, Control
% (type help_wavooutput)
InBuil.oriennr=[1:5];
Output=Wavox0304(Control,Profiles,InClimate,InBuil);
% Output contains all calculated data. Weather data are in InClimate. With
% these file the program wavooutput makes some plots. Type 'help_wavooutput' to
% see the explanation of the content of Output and of InClimate
energy=Output.Qplant;
heating=energy;
i0=find(heating<0);
heating(i0)=0;
cooling=energy;
i0=find(cooling>0);
cooling(i0)=0;
sum(heating)
sum(cooling)
max(heating)
find(heating==max(heating))
min(cooling)
find(cooling==min(cooling))
%Wavooutput
38
Appendix C
%ROOF600_OPEN_CLIM_ST ROOF Case 600 Open Thermal and Hygric, Climate boundary
%
clear all
load Case600_OpenData.mat
load TslData.mat
appla.mode.class='HeatTransfer';
appla.assignsuffix='_ht';
appla.equ.init=10;
appla.equ.k= {'0.16' '0.04' '0.14' };
appla.equ.rho= {'395' '55' '530' };
appla.equ.C= {'1880' '1880' '1880' };
appla.equ.ind=[1 2 3];
applb.mode.class='FlDiffusion';
applb.assignsuffix='_di';
applb.equ.init=500;
applb.equ.D= {'psatf(T)*1.8e-10/(101*2.1)' 'psatf(T)*1.8e-10/(14*1.4)' 'psatf(T)*1.8e-10/(120*95)' };
applb.equ.ind=[1 2 3];
fem.geom=s;
fem.appl={appla applb};
fem.mesh=meshinit(fem);
%fem.mesh=meshrefine(fem); %?
fem=multiphysics(fem);
fem.xmesh=meshextend(fem);
fem.sol=femtime(fem,'tlist',[0:3600:100*24*3600]);
%%%%OUTPUT%%%%%
tu=fem.sol.tlist;
ntu=length(tu);
tdag=tu/(24*3600);
39
xp=[0 0.010 (0.010+0.1118) (0.010+0.1118+0.019)];
Txp=postinterp(fem,'T',xp,'Solnum',[1:ntu]);
Pxp=postinterp(fem,'c',xp,'Solnum',[1:ntu]);
figure(2)
subplot(211)
plot(tdag,Txp)
subplot(212)
plot(tdag,Pxp)
AT=[ NaN xp
tu' Txp ];
AP=[ NaN xp
tu' Pxp ];
40