Commit cbcff803 authored by Esteban Munoz's avatar Esteban Munoz
Browse files

change font size of listings. Ref. cstb/citygml-energy#100

parent 1af29edd
......@@ -28,9 +28,9 @@
\definecolor{tag}{rgb}{0,0.46,0}
\lstset{
basicstyle=\ttfamily \lst@ifdisplaystyle\scriptsize\fi,
basicstyle=\ttfamily \lst@ifdisplaystyle\footnotesize\fi,
framexleftmargin = 5mm,
frame = shadowbox,
%frame = shadowbox,
rulesepcolor = \color{lightgraycode},
numbers = left,
numberstyle = \tiny,
......@@ -91,6 +91,10 @@
\let\stdsection\section%
\renewcommand\section{\newpage\stdsection}
%% Reformat Paragraph
\let\stdparagraph\paragraph%
\renewcommand{\paragraph}[1]{\stdparagraph{#1}\mbox{}\\\vspace{-0.5cm}}
%% Title Page
\usepackage{fancyhdr}
\pagestyle{fancy}
......@@ -850,15 +854,30 @@ properties of the building envelope to calculate the heating and cooling
demand.
\begin{lstlisting}[language=XML]
<!--Example of a ThermalComponent-->
<energy:ThermalComponent gml:id="id_thermalcomponent_1">
<gml:description>Thermal Component 1</gml:description>
<gml:name>Thermal Component 1</gml:name>
<energy:construction xlink:href="#id_construction_1"/>
<energy:area uom="m^2">50.0</energy:area>
<energy:isGroundCoupled>false</energy:isGroundCoupled>
<energy:isSunExposed>true</energy:isSunExposed>
</energy:ThermalComponent>
<!--Example of a Facade with 20% window to wall ratio -->
<energy:ThermalBoundary gml:id="Id_Facade_1">
<energy:thermalBoundaryType>OuterWall</energy:thermalBoundaryType>
<energy:partOf xlink:href="ID_ZONE_1"/>
<energy:composedOf>
<energy:ThermalComponent gml:id="id_Wall_1">
<gml:description>Part of the facade of wall</gml:description>
<energy:construction xlink:href="#id_WallConstruction_1"/>
<energy:area uom="m^2">40.0</energy:area>
<energy:isGroundCoupled>false</energy:isGroundCoupled>
<energy:isSunExposed>true</energy:isSunExposed>
</energy:ThermalComponent>
</energy:composedOf>
<energy:composedOf>
<energy:ThermalComponent gml:id="id_Window_1">
<gml:description>Part of the facade of windows</gml:description>
<energy:construction xlink:href="#id_WindowConstruction_1"/>
<energy:area uom="m^2">10.0</energy:area>
<energy:isGroundCoupled>false</energy:isGroundCoupled>
<energy:isSunExposed>true</energy:isSunExposed>
<energy:relates xlink:href="#opening_window_1"/>
</energy:ThermalComponent>
</energy:composedOf>
</energy:ThermalBoundary>
\end{lstlisting}
\section{Temporal Data Module}\label{temporal-data-module}
......@@ -1392,33 +1411,52 @@ are neglectable in comparison with \lstinline!SolidMaterial!.
\end{figure}
The Occupancy Module contains the detailed characterization of the
building usage, it is related to the rest of the ADE Energy and CityGML
model through the class \lstinline!UsageZone!. Due to the type of
information it allows to store, the Occupancy Module may be used also
for multi-field analysis (socio-economics, demographics etc.).
building usage, it means the people and the facilities. It is related to
the rest of the ADE Energy and CityGML model through the class
\lstinline!UsageZone!. One building may have several
\lstinline!UsageZone!. Due to the type of information it allows to
store, the Occupancy Module may be used also for multi-field analysis
(socio-economics, demographics etc.).
\subsection{Usage zones and building
units}\label{usage-zones-and-building-units}
\subsubsection{UsageZone}\label{usagezone}
Zone of a building with homogeneous usage type. It is a semantic object,
with an optional geometry (\lstinline!volumeGeometry!), which may be or
not related to a geometric entity (Building, BuildingPart, Room etc.).
Its usage type is defined by a \lstinline!usageZoneClass! (corresponding
to the CityGML Code list of the \lstinline!_AbstractBuilding! attribute
class). This zone is operated with a single heating and cooling
set-point temperature schedule (\lstinline!heatingSchedule! respectively
\lstinline!coolingSchedule!) and single air ventilation schedule.
This class inherits from \lstinline!_CityObject! and may therefore be
associated to 1 or more \lstinline!EnergyDemand! objects. This class is
defined by at least a usage zone class and a floor area. The building
storeys occupied by this UsageZone may be also indicated by means of the
attribute usedFloorNumbers, e.g.~with 0 corresponding to the ground
floor. Its internalGains attribute corresponds to the sum of the energy
dissipated from the occupants and the facilities inside the zone.
The \lstinline!UsageZone! is a new object introduced in the Energy ADE
to realize building usage analyses, and in particular to calculate the
energy demand related to occupant-depending end-uses such as domestic
hot water, electrical appliances, cooking etc. When related to the
\lstinline!ThermalZone!, it allows also to provide the zone usage
conditions (e.g.~internal gains, HVAC schedules) for the space heating
and cooling demand calculations.
\lstinline!UsageZone! is a zone of a \lstinline!Building! (or of a
\lstinline!BuildingPart!) with homogeneous usage conditions and indoor
climate control settings. It is a semantic object, with an optional
geometry (\lstinline!volumeGeometry!), which may be or not related to a
geometric entity (Building, BuildingPart, Room etc.).
\lstinline!UsageZone! is minimally defined by the two mandatory
attributes \lstinline!usageZoneClass! (its usage type according to the
CityGML Code list of the \lstinline!_AbstractBuilding! attribute
\lstinline!class!) and \lstinline!floorArea!. The latter may be
attributed several times to a building, specifying different values for
different \lstinline!FloorAreaType!. Its HVAC schedules are
characterized by the optional attributes \lstinline!heatingSchedule!,
\lstinline!coolingSchedule! and \lstinline!ventilationSchedule!
(respectively for the heating and cooling set-point temperature
schedules, and air ventilation schedules). Alternatively to the
\lstinline!volumeGeometry! attribute, the building storeys occupied by
this \lstinline!UsageZone! may be also indicated by means of the
attribute \lstinline!usedFloors! (0 corresponding to the ground floor).
Its optional \lstinline!internalGains! attribute corresponds to the sum
of the energy dissipated from the occupants and the facilities inside
the zone.
The following XML example describe the modeling of a mixed-usage
building. {[}Please introduce the photo of the mixed-usage building of
Piergiorgio and the related XML code{]}
\begin{lstlisting}[language=XML]
<!--Example of a UsageZone-->
......@@ -1651,25 +1689,94 @@ shares the same structure and attributes of the ElectricalAppliances.
\caption{Class diagram of Energy System Module}
\end{figure}
The Energy System Module is a module of the ADE Energy which contains
information concerning the energy forms (energy demand, supply, sources)
and the energy systems (conversion, distribution and storage systems).
It is arranged around one central \lstinline!EnergyDemand! object.
The Energy System Module contains the energy forms (energy demand and
sources) and energy systems (conversion, distribution and storage
systems) to realize energy demand and supply analyses. It allows also to
calculate \(CO_2\) emissions or Primary energy balances.
It is related to the Energy ADE and CityGML model through the object
\lstinline!EnergyDemand!, which can be related to any
\lstinline!_CityObject!. The \lstinline!EnergyConversionSystems! may be
additionally related to the \lstinline!_AbstractBuilding! and
\lstinline!_BoundarySurface! where, respectively on which, they are
installed.
The Energy System Module follows a ``star structure'', with the
\lstinline!EnergyDistributionSystem!, \lstinline!_StorageSystem! and
\lstinline!EnergyConversionSystem! all related to the central object
\lstinline!EnergyDemand!, defined for different end-uses (e.g.~space
heating, electrical appliances) and acquisition methods
(e.g.~measurements, simulation).
\subsection{Energy amounts and types}\label{energy-amounts-and-types}
\subsubsection{EnergyDemand}\label{energydemand}
Useful energy required to satisfy a specific end use, such as heating,
cooling, domestic hot water etc. Beside its \lstinline!EndUseType!, this
object is characterized its \lstinline!energyAmount! (time-depending
energy demand value) and its maximum yearly load
(\lstinline!maximumLoad!) used for the sizing of the energy systems.
The \lstinline!EnergyDemand! is the central object of the Energy System
Module.
Every \lstinline!_CityObject! (typically
\lstinline!ADE:_AbstractBuilding!, \lstinline!ThermalZone!,
\lstinline!UsageZone! and \lstinline!BuildingUnit!) may have one or more
\lstinline!EnergyDemand!.
It is the useful energy required to satisfy the specific end-use
(e.g.~space heating, space cooling, domestic hot water) of a given
object (\lstinline!_CityObject! to which it relates). Beside its
attribute \lstinline!endUse!, this object is characterized by its
\lstinline!energyAmount! (time-depending energy demand values) and its
maximum yearly load (\lstinline!maximumLoad!) used for the sizing of the
energy systems.
Every \lstinline!_CityObject! (typically \lstinline!_AbstractBuilding!,
\lstinline!ThermalZone!, \lstinline!UsageZone! and
\lstinline!BuildingUnit!) may have one or more \lstinline!EnergyDemand!,
related to its different \lstinline!endUseType!, and possibly to
different \lstinline!acquisitionMethod! and \lstinline!sources! (both
attributes of the \lstinline!TimeValueProperties! defining the time
series \lstinline!energyAmount!) such as ``measurements'',
``simulations'' etc.
The XML examples below detail the two end-uses of a same building.
\begin{lstlisting}[language=XML]
<!--Building characterized with its Domestic hot water and electrical appliances demands-->
<bldg:Building>
<energy:energyDemands>
<energy:EnergyDemand>
<energy:endUse>DomesticHotWater</energy:endUse>
<energy:energyAmount>
<energy:IrregularTimeSeries>
<gml:description>DHW demand of Mr X for year 2016</gml:description>
<energy:variableProperties>
<energy:TimeValuesProperties>
<energy:acquisitionMethod>Measurements</energy:acquisitionMethod>
<energy:source>Company X, year 2016</energy:source>
</energy:TimeValuesProperties>
</energy:variableProperties>
<energy:uom uom="kWh"/>
<!-- here come the values of the time series -->
</energy:IrregularTimeSeries>
</energy:energyAmount>
<energy:maximumLoad uom="kW">8.0</energy:maximumLoad>
</energy:EnergyDemand>
</energy:energyDemands>
<energy:energyDemands>
<energy:EnergyDemand>
<energy:endUse>ElectricalAppliances</energy:endUse>
<energy:energyAmount>
<energy:RegularTimeSeriesFile>
<gml:description>Simulated electrical demand of Mr X for typical year</gml:description>
<energy:variableProperties>
<energy:TimeValuesProperties>
<energy:acquisitionMethod>Simulated</energy:acquisitionMethod>
<energy:source>Research Institut Y</energy:source>
</energy:TimeValuesProperties>
</energy:variableProperties>
<!-- here come the file reading information -->
</energy:IrregularTimeSeries>
</energy:energyAmount>
<energy:maximumLoad uom="kW">5.2</energy:maximumLoad>
</energy:EnergyDemand>
</energy:energyDemands>
</bldg:Building>
\end{lstlisting}
\subsubsection{EndUseType}\label{endusetype}
......@@ -1744,12 +1851,12 @@ the battery technology.
System converting an energy source into the energy necessary to satisfy
the \lstinline!EnergyDemand! (or to feed the networks).
Energy conversion systems have common parameters: efficiency indicator,
nominal installed power, nominal efficiency (in reference to an
efficiency indicator), year of manufacture, name of the model, a serial
number, a reference to product or installation documents and optionally
refurbishment measures. They may be one or more (in this case, the
nominal installed power corresponds to the totality).
\lstinline!EnergyConversionSystem! have common parameters: efficiency
indicator, nominal installed power, nominal efficiency (in reference to
an efficiency indicator), year of manufacture, name of the model, a
serial number, a reference to product or installation documents and
optionally refurbishment measures. They may be one or more (in this
case, the nominal installed power corresponds to the totality).
Specific energy conversion systems may have in addition specific
parameters:
......
......@@ -42,6 +42,7 @@ Script to generate a latex via `pandoc` and compile via `pdflatex`.
``` shell
pandoc -S -o Guidelines_EnergyADE.tex \
--listings \
--template=template1 \
--filter pandoc-citeproc \
Guidelines_EnergyADE.md metadata.yaml
......@@ -52,6 +53,7 @@ pdflatex Guidelines_EnergyADE.tex
Script to generate the pdf directly with `pandoc`.
```
pandoc -S -o Guidelines_EnergyADE.pdf \
--listings \
--template template1 \
--filter pandoc-citeproc \
Guidelines_EnergyADE.md metadata.yaml
......
......@@ -28,9 +28,9 @@
\definecolor{tag}{rgb}{0,0.46,0}
\lstset{
basicstyle=\ttfamily \lst@ifdisplaystyle\scriptsize\fi,
basicstyle=\ttfamily \lst@ifdisplaystyle\footnotesize\fi,
framexleftmargin = 5mm,
frame = shadowbox,
%frame = shadowbox,
rulesepcolor = \color{lightgraycode},
numbers = left,
numberstyle = \tiny,
......@@ -95,6 +95,10 @@
\let\stdsection\section%
\renewcommand\section{\newpage\stdsection}
%% Reformat Paragraph
\let\stdparagraph\paragraph%
\renewcommand{\paragraph}[1]{\stdparagraph{#1}\mbox{}\\\vspace{-0.5cm}}
%% Title Page
\usepackage{fancyhdr}
\pagestyle{fancy}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment