<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>roadmap on JottR</title>
    <link>https://www.jottr.org/tags/roadmap/</link>
    <description>Recent content in roadmap on JottR</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.jottr.org/tags/roadmap/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>The Resource Project: Tell R How Much Memory You Need</title>
      <link>https://www.jottr.org/2026/08/11/roadmap-resources-memory/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.jottr.org/2026/08/11/roadmap-resources-memory/</guid>
      <description>Fit a cross-validated elastic net with cv.glmnet(x, y) on a design matrix that comfortably fits in memory, and the call can still fail. The reason is that the function needs several times the size of x while it runs, and nothing anywhere in your script says so. This post is about giving that requirement a home - a memory specification, written in R next to the code that knows it - first for a plain sequential call, then for the same call running in parallel.</description>
    </item>
    
  </channel>
</rss>