<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Semantic-Search on RawCull</title><link>https://techrawcull.netlify.app/tags/semantic-search/</link><description>Recent content in Semantic-Search on RawCull</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 12 Aug 2026 15:22:20 +0200</lastBuildDate><atom:link href="https://techrawcull.netlify.app/tags/semantic-search/index.xml" rel="self" type="application/rss+xml"/><item><title>How PhotoAIKit Is Constructed</title><link>https://techrawcull.netlify.app/docs/packages/photoaikit/</link><pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate><guid>https://techrawcull.netlify.app/docs/packages/photoaikit/</guid><description>&lt;h1 id="how-photoaikit-is-constructed"&gt;How PhotoAIKit Is Constructed&lt;a class="td-heading-self-link" href="#how-photoaikit-is-constructed" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;PhotoAIKit is a reusable Swift package extracted from application code. Its most
important achievement is not merely that CLIP and SAM 3 run. It is that reusable
AI behavior has been separated from RawCull&amp;rsquo;s UI, RAW-file handling, paths,
sandbox rules, and culling policy.&lt;/p&gt;
&lt;p&gt;This document explains the construction from the bottom up and gives the reason
for each boundary.&lt;/p&gt;
&lt;h2 id="1-begin-with-the-package-boundary"&gt;1. Begin With The Package Boundary&lt;a class="td-heading-self-link" href="#1-begin-with-the-package-boundary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The package owns:&lt;/p&gt;</description></item><item><title>How RawCull Loads and Uses CLIP</title><link>https://techrawcull.netlify.app/docs/ai/clip-in-rawcull/</link><pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate><guid>https://techrawcull.netlify.app/docs/ai/clip-in-rawcull/</guid><description>&lt;h1 id="how-rawcull-loads-and-uses-clip"&gt;How RawCull Loads and Uses CLIP&lt;a class="td-heading-self-link" href="#how-rawcull-loads-and-uses-clip" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;RawCull supports two CLIP models:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;OpenAI CLIP ViT-B/32&lt;/strong&gt;, which processes a 224 × 224 image;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;OpenCLIP DataComp ViT-B-32-256&lt;/strong&gt;, which processes a 256 × 256 image.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The user selects one model in &lt;strong&gt;Settings &amp;gt; AI&lt;/strong&gt;. That one selection defines the
vector space used for both image-to-image similarity and text-to-image semantic
search. RawCull never mixes vectors from the two models.&lt;/p&gt;
&lt;p&gt;This page starts with the basic idea behind CLIP and then follows the current
source code from application startup, through model validation and Core AI
inference, to search results, burst groups, and persisted artifacts.&lt;/p&gt;</description></item><item><title>CLIP Model Evaluation Results</title><link>https://techrawcull.netlify.app/docs/ai/evaluation/</link><pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate><guid>https://techrawcull.netlify.app/docs/ai/evaluation/</guid><description>&lt;h1 id="clip-model-evaluation-results"&gt;CLIP Model Evaluation Results&lt;a class="td-heading-self-link" href="#clip-model-evaluation-results" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Report date:&lt;/strong&gt; 2026-08-12&lt;/p&gt;
&lt;p&gt;This report compares the product-behavior results produced by RawCullFB for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;OpenAI CLIP ViT-B/32 at 224 × 224; and&lt;/li&gt;
&lt;li&gt;OpenCLIP DataComp ViT-B/32-256 using the &lt;code&gt;datacomp_s34b_b86k&lt;/code&gt;
checkpoint.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The runs follow the product-behavior portion of
&lt;a href="../evaluateclipmodels/"&gt;Evaluating CLIP Models&lt;/a&gt;. They cover the canonical 77
semantic queries and a complete all-pairs image-similarity pass over 453 indexed
images.&lt;/p&gt;
&lt;p&gt;The reports show that both integrations completed cleanly, neither model shows
semantic collapse, and both produce coherent image-neighbourhood structures.
DataComp is modestly faster and more consistent across paraphrases. Those are
promising sanity-check results, but they are not labeled accuracy metrics.&lt;/p&gt;</description></item></channel></rss>