<?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>DICOM on Qualia Radiomics</title>
    <link>https://qradiomics.com/tags/dicom/</link>
    <description>Recent content in DICOM on Qualia Radiomics</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 17:00:00 -0400</lastBuildDate>
    <atom:link href="https://qradiomics.com/tags/dicom/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Announcing Gemini Gem for Computational Medical Physics — Your Specialized AI Research Assistant</title>
      <link>https://qradiomics.com/posts/2026-05-24-announcing-gemini-gem-for-computational-medical-physics/</link>
      <pubDate>Sun, 24 May 2026 17:00:00 -0400</pubDate>
      <guid>https://qradiomics.com/posts/2026-05-24-announcing-gemini-gem-for-computational-medical-physics/</guid>
      <description>&lt;p&gt;We are excited to share the release of a specialized &lt;strong&gt;Gemini Gem&lt;/strong&gt; designed specifically for &lt;strong&gt;Computational Medical Physicists&lt;/strong&gt;. This AI agent acts as a knowledgeable co-pilot for research, computational modeling, dosimetry, and medical image computing.&lt;/p&gt;
&lt;h2 id=&#34;what-is-the-computational-medical-physicist-gem&#34;&gt;What is the Computational Medical Physicist Gem?&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://gemini.google.com/gem/17j3telEOpOnpU01FDvGLAcLEu1mOxrtG?usp=sharing&#34;&gt;Computational Medical Physicist Gem&lt;/a&gt; is a custom-tuned assistant tailored to the complex, multidisciplinary domain of medical physics. It bridges the gap between physics modeling, coding, and clinical guidelines.&lt;/p&gt;</description>
    </item>
    <item>
      <title>qradiomics — Radiomics Research CLI</title>
      <link>https://qradiomics.com/projects/2026-05-17-qradiomics/</link>
      <pubDate>Sun, 17 May 2026 20:31:21 -0400</pubDate>
      <guid>https://qradiomics.com/projects/2026-05-17-qradiomics/</guid>
      <description>&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Python:&lt;/strong&gt; 3.11+ · &lt;strong&gt;Version:&lt;/strong&gt; 0.9.0 · &lt;strong&gt;Repo:&lt;/strong&gt; &lt;a href=&#34;https://github.com/choilab-jefferson/qradiomics&#34;&gt;choilab-jefferson/qradiomics&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Active successor for three earlier Choi Lab radiomics codebases.&lt;/strong&gt; The C++/MATLAB pipelines in
&lt;a href=&#34;https://github.com/taznux/radiomics-tools&#34;&gt;taznux/radiomics-tools&lt;/a&gt;,
&lt;a href=&#34;https://github.com/taznux/lung-image-analysis&#34;&gt;taznux/lung-image-analysis&lt;/a&gt;, and
&lt;a href=&#34;https://github.com/choilab-jefferson/LungCancerScreeningRadiomics&#34;&gt;choilab-jefferson/LungCancerScreeningRadiomics&lt;/a&gt;
are &lt;strong&gt;superseded&lt;/strong&gt; by this repo. The feature extractors are now in
&lt;code&gt;qradiomics.feature.rtools&lt;/code&gt; (Python ITK port, numerically exact to the C++ binary).
New work should land here.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Radiomics research CLI. &lt;code&gt;qr&lt;/code&gt; does two things equally well:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Atomic tasks&lt;/strong&gt; — convert DICOM, extract features, merge clinical, fit a model. Each is a single command, files in / files out.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow assembly&lt;/strong&gt; — generate, mutate, scaffold, and run multi-step pipelines from those atomic tasks. Default executor is &lt;strong&gt;Nextflow&lt;/strong&gt; (per-patient parallel + cache + HPC); &lt;strong&gt;Prefect&lt;/strong&gt; is the secondary executor; &lt;code&gt;inline&lt;/code&gt; is the small-cohort fallback.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The canonical radiomics data flow has four stages — &lt;code&gt;data → image → features → modeling&lt;/code&gt; — and one &lt;code&gt;qr workflow plan&lt;/code&gt; call instantiates the whole chain:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
