<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>CartPole on Yeongseung's Blog</title><link>https://yeongseung.github.io/tags/cartpole/</link><description>Recent content in CartPole on Yeongseung's Blog</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Tue, 20 Jan 2026 16:14:29 +0900</lastBuildDate><atom:link href="https://yeongseung.github.io/tags/cartpole/index.xml" rel="self" type="application/rss+xml"/><item><title>Stabilizing Q-Learning in CartPole</title><link>https://yeongseung.github.io/posts/mastering_cartpole/post/</link><pubDate>Tue, 20 Jan 2026 16:14:29 +0900</pubDate><guid>https://yeongseung.github.io/posts/mastering_cartpole/post/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;If you are interested in reinforcement learning, you have probably heard of &lt;a href="https://gymnasium.farama.org/environments/classic_control/cart_pole/"&gt;CartPole&lt;/a&gt; &lt;a href="#ref-6"&gt;[6]&lt;/a&gt;, often considered the &amp;ldquo;Hello World&amp;rdquo; environment of the field. This is partly because the task is simple to understand, and partly because each episode ends quickly, allowing you to observe learning progress within a short time.&lt;/p&gt;
&lt;figure class="figure-center"&gt;
&lt;img src="https://yeongseung.github.io/posts/Mastering_CartPole/cartpole.png" width="300"&gt;
&lt;figcaption&gt;Figure 1. CartPole environment visualization&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;Looking back, I have run many experiments in CartPole before, but not in a structured or systematic way, which caused me to forget most of the details over time. In this post, I aim to consolidate those trials into a coherent narrative, focusing in particular on why Q-learning can become unstable and how techniques such as experience replay, Double DQN, and failure-focused sampling can improve robustness.&lt;/p&gt;</description></item></channel></rss>