<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Structural &amp; Architectural Design - Timber Engineering Forum				            </title>
            <link>https://timberengineering.org/community/structural-architectural-design/</link>
            <description>Timber Engineering Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Tue, 05 May 2026 15:56:51 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Tapered Beam stability check</title>
                        <link>https://timberengineering.org/community/structural-architectural-design/tapered-beam-stability-check/</link>
                        <pubDate>Sat, 22 Feb 2025 17:30:54 +0000</pubDate>
                        <description><![CDATA[Is there any explicit recommendation in NDS on stability factor CL calculation for Tapered beams?
say I have a beam start from 20&quot; on one end and go to 10&quot; on the other end, what depth shou...]]></description>
                        <content:encoded><![CDATA[<p>Is there any explicit recommendation in NDS on stability factor CL calculation for Tapered beams?</p>
<p>say I have a beam start from 20" on one end and go to 10" on the other end, what depth should I use to go into the CL calculation?</p>
<p>Using 20 is apparently conservative and OK, but is there any explicit rule for that?</p>
<p><span>@billkirkham  @heblomgren  @johnlawson</span></p>]]></content:encoded>
						                            <category domain="https://timberengineering.org/community/structural-architectural-design/">Structural &amp; Architectural Design</category>                        <dc:creator>Shiling Pei</dc:creator>
                        <guid isPermaLink="true">https://timberengineering.org/community/structural-architectural-design/tapered-beam-stability-check/</guid>
                    </item>
				                    <item>
                        <title>Timber floor vibration design</title>
                        <link>https://timberengineering.org/community/structural-architectural-design/timber-floor-vibration-design/</link>
                        <pubDate>Wed, 06 Nov 2024 19:56:26 +0000</pubDate>
                        <description><![CDATA[Wood is lightweight with a relatively low bending stiffness. As mass timber is designed and built with increasing spans, floor vibration design becomes an important serviceability limit cons...]]></description>
                        <content:encoded><![CDATA[<p>Wood is lightweight with a relatively low bending stiffness. As mass timber is designed and built with increasing spans, floor vibration design becomes an important serviceability limit consideration. Floor vibration design often determines the allowable span and material use.</p>
<p> </p>
<p>There are very limited design guidelines or resources available for practitioners. The current design equations in the CLT Handbook (Canada or US versions) are limited to floors with rigid supports (walls), and the U.S. Mass Timber Floor Vibration Design Guide is basically a literature review of CLT handbook method and other response-based methods developed for concrete and steel floors, without any verifications against data.</p>
<p> </p>
<p>The challenges in vibration serviceability design for timber structures are twofold: predicting dynamic properties and responses and establishing suitable design or performance criteria. Due to the inhomogeneous material properties, orthotropic elastic constants, and construction details with discontinuity and semi-rigid connections, accurately predicting the dynamic properties and responses of timber structures under footfall or wind excitations can be complex. Moreover, human perception of vibration can be highly subjective, influenced by environmental conditions and psychological and physiological aspects. The latter one is even more challenging.</p>
<p> </p>
<p>To address this gap, the only way is to create a database, which consists of both the physical data of the floor and occupants' subjective ratings (post-occupancy evaluation). With the database, we can do all kinds of analysis and develop design guidelines tailored for mass timber floor systems. </p>
<p> </p>
<p>Please share your thoughts and discussion. </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>]]></content:encoded>
						                            <category domain="https://timberengineering.org/community/structural-architectural-design/">Structural &amp; Architectural Design</category>                        <dc:creator>Jianhui Zhou</dc:creator>
                        <guid isPermaLink="true">https://timberengineering.org/community/structural-architectural-design/timber-floor-vibration-design/</guid>
                    </item>
				                    <item>
                        <title>NDS vs. EuroCode 1995</title>
                        <link>https://timberengineering.org/community/structural-architectural-design/nds-vs-eurocode-1995/</link>
                        <pubDate>Fri, 25 Oct 2024 10:04:25 +0000</pubDate>
                        <description><![CDATA[]]></description>
                        <content:encoded><![CDATA[]]></content:encoded>
						                            <category domain="https://timberengineering.org/community/structural-architectural-design/">Structural &amp; Architectural Design</category>                        <dc:creator>Shiling Pei</dc:creator>
                        <guid isPermaLink="true">https://timberengineering.org/community/structural-architectural-design/nds-vs-eurocode-1995/</guid>
                    </item>
							        </channel>
        </rss>
		