<?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>Kaggle on Veritable Tech Blog</title>
    <link>https://blog.ceshine.net/tags/kaggle/</link>
    <description>Recent content in Kaggle on Veritable Tech Blog</description>
    <generator>Hugo -- 0.149.1</generator>
    <language>en</language>
    <copyright>2015-2026 Ceshine Lee · CC BY-NC-SA 4.0</copyright>
    <lastBuildDate>Fri, 10 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.ceshine.net/tags/kaggle/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Kaggle] Quick Recap of Orbit Wars</title>
      <link>https://blog.ceshine.net/post/orbit-wars-2026-kaggle/</link>
      <pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/orbit-wars-2026-kaggle/</guid>
      <description>Reflections on competing in Kaggle&amp;#39;s Orbit Wars, from building a Rust simulation engine to learning hard lessons about complexity and prioritization.</description>
    </item>
    <item>
      <title>[Kaggle] Google Research Football 2020</title>
      <link>https://blog.ceshine.net/post/16th-place-google-research-football/</link>
      <pubDate>Mon, 28 Dec 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/16th-place-google-research-football/</guid>
      <description>Describing my 16th place solution and also reviewing some of the others&amp;#39;</description>
    </item>
    <item>
      <title>[Competition] Jigsaw Multilingual Toxic Comment Classification</title>
      <link>https://blog.ceshine.net/post/multilingual-toxic-classification/</link>
      <pubDate>Wed, 05 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/multilingual-toxic-classification/</guid>
      <description>The 3rd Jigsaw Text Classification Competition</description>
    </item>
    <item>
      <title>TensorFlow 2.1 with TPU in Practice</title>
      <link>https://blog.ceshine.net/post/tf21-quest/</link>
      <pubDate>Thu, 13 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/tf21-quest/</guid>
      <description>Case Study: Google QUEST Q&amp;amp;A Labeling Competition</description>
    </item>
    <item>
      <title>[Notes] Jigsaw Unintended Bias in Toxicity Classification</title>
      <link>https://blog.ceshine.net/post/kaggle-jigsaw-toxic-2019/</link>
      <pubDate>Sun, 04 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/kaggle-jigsaw-toxic-2019/</guid>
      <description>Bias Reduction; Summary of Top Solutions</description>
    </item>
    <item>
      <title>[Notes] iMet Collection 2019 - FGVC6 (Part 1)</title>
      <link>https://blog.ceshine.net/post/kaggle-imet-2019/</link>
      <pubDate>Tue, 16 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/kaggle-imet-2019/</guid>
      <description>Overview; Augmentation; Training Models on Kaggle</description>
    </item>
    <item>
      <title>[Review] Kaggle Toxic Comment Classification Challenge</title>
      <link>https://blog.ceshine.net/post/kaggle-toxic-comment-classification-challenge/</link>
      <pubDate>Sat, 24 Mar 2018 05:40:19 +0000</pubDate>
      <guid>https://blog.ceshine.net/post/kaggle-toxic-comment-classification-challenge/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;18gwWxW96N8CSCpOVZZ1tbA.jpeg&#34;
         alt=&#34;Photo Credit&#34;/&gt; &lt;figcaption&gt;
            &lt;p&gt;&lt;a href=&#34;https://pixabay.com/en/pollution-toxic-products-environment-3075857/&#34;&gt;Photo Credit&lt;/a&gt;&lt;/p&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://www.kaggle.com/c/jigsaw-toxic-comment-classification-challenge&#34;&gt;Jigsaw toxic comment classification challenge&lt;/a&gt; features a multi-label text classification problem with a highly imbalanced dataset. The test set used originally was revealed to be already public on the Internet, so &lt;a href=&#34;https://www.kaggle.com/c/jigsaw-toxic-comment-classification-challenge/discussion/47835&#34;&gt;a new dataset was released&lt;/a&gt; mid-competition, and the evaluation metric was &lt;a href=&#34;https://www.kaggle.com/c/jigsaw-toxic-comment-classification-challenge/discussion/48639&#34;&gt;changed from Log Loss to AUC&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I tried a few ideas after building up my PyTorch pipeline but did not find any innovative approach that looks promising. Text normalization is the only strategy I had found to give solid improvements, but it is very time consuming. The final result (105th place/about top 3%) was quite fitting IMO given the time I spent on this competition(not a lot).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
