<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>admin, Author at PatternSmart.com</title>
	<atom:link href="https://patternsmart.com/wp/author/glm/feed/" rel="self" type="application/rss+xml" />
	<link>https://patternsmart.com/wp/author/glm/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Jul 2026 03:24:10 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>

<image>
	<url>https://patternsmart.com/wp/wp-content/uploads/2026/04/cropped-icon-32x32.png</url>
	<title>admin, Author at PatternSmart.com</title>
	<link>https://patternsmart.com/wp/author/glm/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to identify when an indicator should not be used</title>
		<link>https://patternsmart.com/wp/how-to-identify-when-an-indicator-should-not-be-used/</link>
					<comments>https://patternsmart.com/wp/how-to-identify-when-an-indicator-should-not-be-used/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 03:24:09 +0000</pubDate>
				<category><![CDATA[Indicator Concepts]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1761</guid>

					<description><![CDATA[<p>The Boundaries of Algorithmic Logic: Identifying When an Indicator Fails In technical analysis, the quest for the ultimate indicator often blinds traders to a fundamental reality: indicators are mathematical transformations of price, volume, and time; they are not crystal balls. Every indicator is engineered with specific mathematical assumptions about how a market behaves. When the [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/how-to-identify-when-an-indicator-should-not-be-used/">How to identify when an indicator should not be used</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/how-to-identify-when-an-indicator-should-not-be-used/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-7.png" medium="image"></media:content>
            	</item>
		<item>
		<title>Trading the Quiet Before the Storm: How to Detect Volatility Compression</title>
		<link>https://patternsmart.com/wp/trading-the-quiet-before-the-storm-how-to-detect-volatility-compression/</link>
					<comments>https://patternsmart.com/wp/trading-the-quiet-before-the-storm-how-to-detect-volatility-compression/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 03:03:43 +0000</pubDate>
				<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1758</guid>

					<description><![CDATA[<p>In financial markets, volatility is cyclical. It continuously oscillates between two primary phases: compression (consolidation) and expansion (trend). Volatility compression represents a period where price action tightens, market participants reach a temporary equilibrium, and energy builds up within a narrow range. For systematic and technical traders, detecting compression is one of the most reliable ways [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/trading-the-quiet-before-the-storm-how-to-detect-volatility-compression/">Trading the Quiet Before the Storm: How to Detect Volatility Compression</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/trading-the-quiet-before-the-storm-how-to-detect-volatility-compression/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-6.png" medium="image"></media:content>
            	</item>
		<item>
		<title>Why support and resistance zones change over time</title>
		<link>https://patternsmart.com/wp/why-support-and-resistance-zones-change-over-time/</link>
					<comments>https://patternsmart.com/wp/why-support-and-resistance-zones-change-over-time/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 02:14:07 +0000</pubDate>
				<category><![CDATA[Support and Resistance]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1753</guid>

					<description><![CDATA[<p>Dynamic Market Structure: Why Support and Resistance Zones Shift In classical technical analysis, horizontal lines are often drawn across historical price peaks and troughs, treating support and resistance as static boundaries. While this approach looks clean on a historical chart, live market participants quickly realize a fundamental truth: support and resistance zones are dynamic, evolving [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/why-support-and-resistance-zones-change-over-time/">Why support and resistance zones change over time</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/why-support-and-resistance-zones-change-over-time/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-5.png" medium="image"></media:content>
            	</item>
		<item>
		<title>How to store indicator states for strategy access.</title>
		<link>https://patternsmart.com/wp/how-to-store-indicator-states-for-strategy-access/</link>
					<comments>https://patternsmart.com/wp/how-to-store-indicator-states-for-strategy-access/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 02:07:07 +0000</pubDate>
				<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1750</guid>

					<description><![CDATA[<p>In high-frequency or complex algorithmic trading, calculating trading indicators on the fly can quickly become a computational bottleneck. More importantly, if your strategy transitions from historical backtesting to live execution, managing how indicators hold, update, and persist their internal calculation states is critical. If state management is handled poorly, it can lead to state drift, [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/how-to-store-indicator-states-for-strategy-access/">How to store indicator states for strategy access.</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/how-to-store-indicator-states-for-strategy-access/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-4.png" medium="image"></media:content>
            	</item>
		<item>
		<title>How do I code dynamic slippage models in Python?</title>
		<link>https://patternsmart.com/wp/how-do-i-code-dynamic-slippage-models-in-python/</link>
					<comments>https://patternsmart.com/wp/how-do-i-code-dynamic-slippage-models-in-python/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 01:59:52 +0000</pubDate>
				<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1747</guid>

					<description><![CDATA[<p>Here is a robust Python implementation demonstrating how to model dynamic, volume-based slippage inside a custom Pandas backtester. Instead of applying a flat, unrealistic penalty to every trade, this snippet uses a nonlinear market impact model (often called a square-root law variant). The model dynamically scales execution friction based on two critical variables: Python Breakdown [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/how-do-i-code-dynamic-slippage-models-in-python/">How do I code dynamic slippage models in Python?</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/how-do-i-code-dynamic-slippage-models-in-python/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-3.png" medium="image"></media:content>
            	</item>
		<item>
		<title>Why backtest results can look better than live signals</title>
		<link>https://patternsmart.com/wp/why-backtest-results-can-look-better-than-live-signals/</link>
					<comments>https://patternsmart.com/wp/why-backtest-results-can-look-better-than-live-signals/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 01:51:39 +0000</pubDate>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1744</guid>

					<description><![CDATA[<p>It is a rite of passage for every algorithmic trader. You design a strategy, run a historical simulation over five years of market data, and the results are spectacular—a high Sharpe ratio, minimal drawdowns, and a smooth equity curve. Enthusiastic, you deploy the strategy to a live trading account. Weeks later, the real-world performance is [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/why-backtest-results-can-look-better-than-live-signals/">Why backtest results can look better than live signals</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/why-backtest-results-can-look-better-than-live-signals/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-2.png" medium="image"></media:content>
            	</item>
		<item>
		<title>The Invisible Leak: Mastering Multi-Timeframe Look-Ahead Bias</title>
		<link>https://patternsmart.com/wp/the-invisible-leak-mastering-multi-timeframe-look-ahead-bias/</link>
					<comments>https://patternsmart.com/wp/the-invisible-leak-mastering-multi-timeframe-look-ahead-bias/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 01:43:34 +0000</pubDate>
				<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1741</guid>

					<description><![CDATA[<p>In algorithmic trading, utilizing multiple timeframes (MTF) is one of the most effective ways to build a comprehensive market perspective. A classic multi-timeframe strategy uses a higher timeframe (HTF) chart—like a 4-hour or Daily chart—to determine the macro trend, while executing entries on a lower timeframe (LTF) chart—like a 5-minute or 15-minute chart. However, MTF [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/the-invisible-leak-mastering-multi-timeframe-look-ahead-bias/">The Invisible Leak: Mastering Multi-Timeframe Look-Ahead Bias</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/the-invisible-leak-mastering-multi-timeframe-look-ahead-bias/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image-1.png" medium="image"></media:content>
            	</item>
		<item>
		<title>How to avoid look-ahead bias when coding trading indicators</title>
		<link>https://patternsmart.com/wp/how-to-avoid-look-ahead-bias-when-coding-trading-indicators/</link>
					<comments>https://patternsmart.com/wp/how-to-avoid-look-ahead-bias-when-coding-trading-indicators/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2026 01:36:27 +0000</pubDate>
				<category><![CDATA[Coding Logic]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1738</guid>

					<description><![CDATA[<p>Every algorithmic trader has experienced this moment: You spend hours coding a new custom indicator, plug it into a backtester, and the equity curve shoots up like a rocket. It looks flawless. You have seemingly discovered the holy grail of trading systems. Then, you deploy it live, and it immediately loses money. The most common [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/how-to-avoid-look-ahead-bias-when-coding-trading-indicators/">How to avoid look-ahead bias when coding trading indicators</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/how-to-avoid-look-ahead-bias-when-coding-trading-indicators/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/image.png" medium="image"></media:content>
            	</item>
		<item>
		<title>USDJPY Momentum Double Divergence &#038; TPR Confluence Analysis on cTrader: Macro Bearish Resumption Across Multi-Range Frameworks</title>
		<link>https://patternsmart.com/wp/usdjpy-momentum-double-divergence-tpr-confluence-analysis-on-ctrader-macro-bearish-resumption-across-multi-range-frameworks/</link>
					<comments>https://patternsmart.com/wp/usdjpy-momentum-double-divergence-tpr-confluence-analysis-on-ctrader-macro-bearish-resumption-across-multi-range-frameworks/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 05 Jul 2026 21:39:21 +0000</pubDate>
				<category><![CDATA[cTrader]]></category>
		<category><![CDATA[Divergence]]></category>
		<category><![CDATA[Divergence Analysis]]></category>
		<category><![CDATA[Forex]]></category>
		<category><![CDATA[Indicator]]></category>
		<category><![CDATA[Indicator Concepts]]></category>
		<category><![CDATA[Market Analysis]]></category>
		<category><![CDATA[Support and Resistance]]></category>
		<category><![CDATA[TPR]]></category>
		<category><![CDATA[Double Divergence]]></category>
		<category><![CDATA[Momentum Divergence]]></category>
		<category><![CDATA[Momentum Double Divergence]]></category>
		<guid isPermaLink="false">https://patternsmart.com/wp/?p=1556</guid>

					<description><![CDATA[<p>1. Introduction &#38; Key Takeaways In modern systematic trading, isolating true structural shifts from temporary market noise requires cross-timeframe structural alignment. This technical analysis provides a deep dive into the USDJPY currency pair utilizing cTrader&#8216;s advanced Chart Typologies. By deploying a multi-range framework combined with the volume-neutralized Momentum Double Divergence indicator and the volatility-based Trend [&#8230;]</p>
<p>The post <a href="https://patternsmart.com/wp/usdjpy-momentum-double-divergence-tpr-confluence-analysis-on-ctrader-macro-bearish-resumption-across-multi-range-frameworks/">USDJPY Momentum Double Divergence &amp; TPR Confluence Analysis on cTrader: Macro Bearish Resumption Across Multi-Range Frameworks</a> appeared first on <a href="https://patternsmart.com/wp">PatternSmart.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://patternsmart.com/wp/usdjpy-momentum-double-divergence-tpr-confluence-analysis-on-ctrader-macro-bearish-resumption-across-multi-range-frameworks/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<media:content url="https://patternsmart.com/wp/wp-content/uploads/2026/07/cTraderMomentum2DIV-3.png" medium="image"></media:content>
            	</item>
	</channel>
</rss>
