<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01568nab a2200205   4500</leader>
  <controlfield tag="005">20260520000944.0</controlfield>
  <controlfield tag="008">260224s2010    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">A comparison of a statistical and computational fluid dynamics approach to estimate heat release rate in road tunnel fires</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">jul. 2010</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">26/08/2010 ; 26/08/2010</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">19 p. ; 531-549</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. Computational tools such as one-dimensional models or Computational Fluid Dynamics (CFD) have been used for the fire safety design of road tunnels. However, most of these analyses are performed using a specified fire source where the heat release rate (HRR) in the tunnel is fixed by the user and the influences of ventilation conditions and tunnel geometry are not considered. For a more realistic estimate, models need to incorporate these factors in their input. This paper discusses the use of a statistical approach previously developed by other researchers (Carvel and Beard, The handbook of tunnel fire safety. Thomas Telford Publishing, pp 184&amp;#x96;197, 2005) and the use of a CFD approach to estimate the HRR in a road tunnel fire. As an application example, fire scenarios in which a light goods vehicle carrying wooden pallets are used to compare the estimation of the HRR using these two methods.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">3</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Fire Technology</subfield>
    <subfield code="g">46</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Cheong, M.K.</subfield>
    <subfield code="9">46624</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Spearpoint, M.J.</subfield>
    <subfield code="9">46625</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Fleischmann, C.M.</subfield>
    <subfield code="9">46626</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">176318</subfield>
    <subfield code="d">176318</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">244137</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200048247</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200048247</subfield>
    <subfield code="r">2026-03-05 18:56:59</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
