<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Science Workflows on The Augmented Scholar</title><link>https://augmentedscholars.com/tags/data-science-workflows/</link><description>Recent content in Data Science Workflows on The Augmented Scholar</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 17:59:48 +0400</lastBuildDate><atom:link href="https://augmentedscholars.com/tags/data-science-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>Convert Markdown to Jupyter Notebooks with Jupytext</title><link>https://augmentedscholars.com/posts/research-tools/convert-markdown-to-jupyter-notebooks-with-jupytext/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/research-tools/convert-markdown-to-jupyter-notebooks-with-jupytext/</guid><description>&lt;h1 id="convert-markdown-to-jupyter-notebooks-using-jupytext--for-researchers-who-need-executable-code"&gt;Convert Markdown to Jupyter Notebooks Using Jupytext — For Researchers Who Need Executable Code&lt;/h1&gt;
&lt;p&gt;Your Markdown files are beautiful but frozen. You&amp;rsquo;ve written detailed documentation with embedded code snippets, but they&amp;rsquo;re just text—no execution, no live plots, no way to tweak parameters and see results instantly. &lt;strong&gt;Jupytext&lt;/strong&gt; solves this in one command: it transforms static Markdown into fully executable Jupyter Notebooks while keeping your source file version-control friendly.&lt;/p&gt;</description></item></channel></rss>