<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Reducing Computational Costs - SST Turbulence Model in CFD Forum</title>
    <link>https://forums.autodesk.com/t5/cfd-forum/reducing-computational-costs-sst-turbulence-model/m-p/9637192#M4777</link>
    <description>&lt;P&gt;I am modeling the external aerodynamics of a class 8 vehicle (in other words, a semi-truck). In order to achieve a y+ value less than 1 for accurate results with the SST Turbulence Model, I have refined the boundary layer that exponentially increases my computational costs. Currently, my simulations use 25+ million fluid elements. Any insight or tips on how to reduce this element count would be greatly appreciated&lt;/P&gt;</description>
    <pubDate>Wed, 15 Jul 2020 15:44:23 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2020-07-15T15:44:23Z</dc:date>
    <item>
      <title>Reducing Computational Costs - SST Turbulence Model</title>
      <link>https://forums.autodesk.com/t5/cfd-forum/reducing-computational-costs-sst-turbulence-model/m-p/9637192#M4777</link>
      <description>&lt;P&gt;I am modeling the external aerodynamics of a class 8 vehicle (in other words, a semi-truck). In order to achieve a y+ value less than 1 for accurate results with the SST Turbulence Model, I have refined the boundary layer that exponentially increases my computational costs. Currently, my simulations use 25+ million fluid elements. Any insight or tips on how to reduce this element count would be greatly appreciated&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2020 15:44:23 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/cfd-forum/reducing-computational-costs-sst-turbulence-model/m-p/9637192#M4777</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-07-15T15:44:23Z</dc:date>
    </item>
  </channel>
</rss>

