<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://windtakemenorth.github.io/feed.xml" rel="self" type="application/atom+xml"/><link href="https://windtakemenorth.github.io/" rel="alternate" type="text/html" hreflang="en"/><updated>2026-05-29T20:09:20+00:00</updated><id>https://windtakemenorth.github.io/feed.xml</id><title type="html">blank</title><subtitle>Researcher at the University of Cambridge. Clinical AI evaluation, digital food environment, US housing market dynamics, and applied machine learning. </subtitle><entry><title type="html">An accidental international team — and our first epidemic-forecasting paper</title><link href="https://windtakemenorth.github.io/blog/2026/epidemic-forecasting-three-cities/" rel="alternate" type="text/html" title="An accidental international team — and our first epidemic-forecasting paper"/><published>2026-05-29T09:00:00+00:00</published><updated>2026-05-29T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/epidemic-forecasting-three-cities</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/epidemic-forecasting-three-cities/"><![CDATA[<p>I don’t usually write blog posts about how a paper happened. This one is an exception, because this one didn’t happen the way papers usually do.</p> <h2 id="how-it-started--a-formal-swap">How it started — a formal swap</h2> <p>Early in the MPhil, I met <strong>Minghong</strong> through a <strong>formal swap</strong> between our two colleges. I’m at <strong>Wolfson</strong>; he’s at <strong>Peterhouse</strong>. Formal swaps are a Cambridge ritual where colleges trade a handful of students for a black-tie dinner across the dining hall — a low-friction way to meet people outside your own department and your own college.</p> <p>We ended up at the same table. The conversation kept going after dinner, and over the next few weeks Minghong mentioned, in passing, that his older brother <strong>Mingxin Liu</strong> was a researcher in the <strong>Department of Health Communication at the University of Tokyo’s Graduate School of Medicine</strong>. I filed it away.</p> <h2 id="a-dalian-coincidence">A Dalian coincidence</h2> <p>Around the same time, I got to know <strong>Jingyuan Han</strong> — a researcher in the <strong>Department of Cancer Prevention and Control at the National Cancer Center, Chinese Academy of Medical Sciences and Peking Union Medical College</strong> in Beijing. We weren’t in any of the same labs either. We met the way two Chinese students in different cities do: through somebody who knew somebody.</p> <p>Somewhere in our first real conversation Jingyuan mentioned his girlfriend was a student at <strong>Dalian Medical University</strong>.</p> <p>I’m from Dalian.</p> <p>That moment landed in the place such moments land. The conversation slowed down for a second, then sped up. We didn’t immediately start talking about science — we talked about Dalian. The seafood. The harbour. Where she studied versus where I grew up. Whether the campus had changed since I was last back.</p> <p>I think that’s actually when the project started, even though the project didn’t exist yet.</p> <h2 id="the-accidental-geometry">The accidental geometry</h2> <p>After a few more conversations, the three of us — <strong>Cambridge → Tokyo → Beijing</strong> — realised we were each chasing the same problem from different angles.</p> <p>Public-health surveillance systems do not speak the same language across borders. Different case definitions. Different rules for what counts as a lab-confirmed case. Different ICD coding habits. <strong>Reporting delays, revisions, and backfill</strong>. A forecasting model fitted on one system breaks the moment you cross a border, change a coding standard, or pull from a different reporting tier.</p> <p>Mingxin saw it from the <strong>health-communication</strong> side at Tokyo — how surveillance protocols shape what the public ends up hearing and trusting. Jingyuan saw it from the <strong>cancer prevention and control</strong> side at the National Cancer Center, where national surveillance data flows through specific institutional pipes and feeds intervention design. I saw it from the <strong>statistical / methodological</strong> side at Cambridge — <em>if the underlying protocols differ, your forecasting model needs to know about the protocols.</em></p> <p>None of us would have written this paper alone.</p> <h2 id="epimap-llm">EpiMap-LLM</h2> <p>The proposal is straightforward in retrospect: <strong>bake the protocol structure into the forecasting model itself.</strong> Instead of treating each surveillance stream as a black-box source of case counts, condition the model on the protocol that generated those counts — case definition, reporting cadence, revision pattern, backfill — so it learns what each stream is <em>actually measuring</em>, not just the headline numbers.</p> <p>We built this as <strong>EpiMap-LLM</strong> — a parameter-efficient alignment framework that connects numerical time-series representations with a <strong>frozen language-model backbone</strong>, with only lightweight trainable components on top. Protocol-aware tokens are injected as context, so the model can distinguish protocol-induced fluctuations from genuine epidemiological shifts and transfer across datasets and temporal granularities.</p> <p>We tested it on two heterogeneous surveillance settings — <strong>JHU CSSE COVID-19</strong> (daily) and <strong>CDC influenza hospitalization</strong> (weekly). EpiMap-LLM consistently improves MAE and RMSE over strong forecasting baselines. The gain is largest where reporting irregularities are worst — exactly the operational regime where forecasts have to be trusted.</p> <p>The full paper is open access in <em>Frontiers in Public Health</em>, published 29 May 2026. Jingyuan and I are <strong>co-first authors</strong>.</p> <p><a href="/publications/#hu2026protocol">Read the paper</a> · <a href="https://www.frontiersin.org/journals/public-health/articles/10.3389/fpubh.2026.1829302/full">Frontiers (open access)</a></p> <h2 id="what-i-want-to-remember">What I want to remember</h2> <p>The geometry. Cambridge, Tokyo, Beijing. A college friend’s older brother. A girlfriend at a Dalian medical school. Late-night WeChat threads that turned into shared spreadsheets that turned into a draft. International collaboration sometimes gets described as if it were arranged at the institutional level — MOUs, summer schools, formal exchanges. This wasn’t that. Three sides showed up because three friendships did. The paper followed.</p> <h2 id="whats-next">What’s next</h2> <p>Jingyuan and I are starting to look at a follow-up — <strong>social media in China and cancer prevention</strong> — pulling on his cancer-prevention work at the National Cancer Center and on the communication side that Mingxin works on in Tokyo. It’s a natural extension: surveillance data and public-facing communication are two halves of the same loop. It also connects to my dissertation thread on the digital food environment, where the same question recurs in a different language. When we have something to show, this is where I’ll write about it.</p> <p>Mingxin, Jingyuan — thank you. This one is special.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="epidemic-forecasting"/><category term="surveillance"/><category term="LLM"/><category term="collaboration"/><category term="Cambridge"/><category term="Tokyo"/><category term="Beijing"/><summary type="html"><![CDATA[How a friendship at Peterhouse, a hometown coincidence with Dalian, and three time zones turned into EpiMap-LLM and a paper in Frontiers in Public Health.]]></summary></entry><entry><title type="html">BFR with sprinters — a collaborative RCT</title><link href="https://windtakemenorth.github.io/blog/2026/bfr-sprinters-collab/" rel="alternate" type="text/html" title="BFR with sprinters — a collaborative RCT"/><published>2026-05-12T09:00:00+00:00</published><updated>2026-05-12T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/bfr-sprinters-collab</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/bfr-sprinters-collab/"><![CDATA[<p>Coming into the MPhil at Cambridge, I wanted to get <strong>hands-on experience across the breadth of health research</strong> — not just nutritional epi, but also things like genomics, physiology, sport science — before settling deeper into one. The publication itself is secondary to the experience. So when an opportunity came to join a sport-physiology RCT led by Ji Zhu and colleagues at Fujian Normal University (with Jiale Wang, Huangkun Chen, Ming Li, and Yanlin Wang), I took it. I contributed the statistical analysis and the writing, and joined as corresponding author.</p> <p>Most blood-flow restriction (BFR) evidence is in older adults and rehabilitation populations. Data in trained athletes is thin. The team ran an 8-week study in <strong>male college sprinters</strong> (n = 28), comparing functional strength training (FST) alone against FST + BFR. Cuff pressures were set at 50% of individualised arterial occlusion pressure measured by Doppler — a more rigorous protocol than ratio-based BFR prescriptions.</p> <p>The finding was narrower than I expected, and that’s the interesting part:</p> <ul> <li><strong>Both groups improved</strong> on isokinetic knee strength, CMJ, squat jump, FMS, Y-Balance</li> <li>The <strong>BFR-specific advantage</strong> was a significant group × time interaction on <strong>anaerobic power only</strong> (+92.99 W vs FST alone, F = 80.51, η²p = 0.756)</li> <li>For overall strength and movement quality, FST alone got you most of the way</li> </ul> <p>Practical framing for coaches: BFR is a <strong>power tool</strong>, not a generic strength multiplier. If the priority is sprint-relevant anaerobic power, the cuffs do real work. If the priority is general strength, FST alone is probably enough.</p> <p>Open access in Frontiers in Physiology, 2026: <a href="/publications/#zhu2026effects">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="sport-science"/><category term="BFR"/><category term="strength-training"/><category term="RCT"/><category term="collaboration"/><summary type="html"><![CDATA[Eight-week RCT on functional strength training with vs without blood-flow restriction.]]></summary></entry><entry><title type="html">Food policy is still regulating streets — we wrote to The Lancet about screens</title><link href="https://windtakemenorth.github.io/blog/2026/upf-lancet-correspondence/" rel="alternate" type="text/html" title="Food policy is still regulating streets — we wrote to The Lancet about screens"/><published>2026-04-30T09:00:00+00:00</published><updated>2026-04-30T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/upf-lancet-correspondence</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/upf-lancet-correspondence/"><![CDATA[<p><em>The Lancet</em> ran a comment on ultra-processed food policy by Scrinis and colleagues — a strong piece that pushed UPF policy beyond reformulation toward fiscal, labelling, marketing, and retail measures. But the <strong>digital food environment</strong> barely came up.</p> <p>This sat alongside the MPhil dissertation work on UPFs I was doing with my supervisors <strong>Mike Essman</strong> and <strong>Jean Adams</strong> at Cambridge. Reading the UPF literature in depth, then talking through what the policy frame still missed — with Mike, Jean, and other colleagues at the MRC Epidemiology Unit and CEDAR — made the gap feel obvious. Online food delivery platforms, social media food marketing, and algorithm-driven content curation are now major exposure pathways. Current food-environment frameworks don’t really see them.</p> <p>I wrote a follow-up correspondence in <em>The Lancet</em>. The argument is simple: UPF policy needs an explicit digital track. Three concrete asks:</p> <ul> <li><strong>Algorithmic exposure audits</strong> for adolescent food marketing</li> <li><strong>Platform-level marketing regulation</strong> parallel to broadcast rules</li> <li><strong>Measurement frameworks</strong> that include view-weighted exposure, not just retail proximity</li> </ul> <p>Correspondence in The Lancet, 2026: <a href="/publications/#hu2026upf">link</a>. Pairs naturally with <a href="/publications/#hu2026tiktok">the TikTok exposure letter in Public Health Nutrition</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="ultra-processed-food"/><category term="food-policy"/><category term="digital-food-environment"/><category term="Cambridge"/><summary type="html"><![CDATA[Lancet correspondence arguing UPF policy needs an explicit digital track.]]></summary></entry><entry><title type="html">Clinical LLM apps need retrieval-grounded evaluation, not just AUC</title><link href="https://windtakemenorth.github.io/blog/2026/rag-clinical-evaluation/" rel="alternate" type="text/html" title="Clinical LLM apps need retrieval-grounded evaluation, not just AUC"/><published>2026-04-15T09:00:00+00:00</published><updated>2026-04-15T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/rag-clinical-evaluation</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/rag-clinical-evaluation/"><![CDATA[<p>Same MPhil exploration period that gave me the <em>Clinical Imaging</em> letter — reading widely across clinical AI, evaluation methodology, and infectious-disease epidemiology. <em>JMIR AI</em> published a study using fine-tuned LLaMA2 / Flan-T5 for pediatric COVID-19 severity risk assessment, deployed as a conversational app. The evaluation reported AUC.</p> <p>AUC tells you the classifier is calibrated on held-out data. It does not tell you whether the <strong>natural-language explanations</strong> the deployed app produces are grounded in actual clinical guidance — only whether the underlying yes/no token probabilities discriminate on the dataset.</p> <p>That gap matters. The deployed system is a chat interface giving caregivers fluent risk explanations. Fluent + calibrated is not the same as grounded. A model can confidently invent a CDC recommendation that doesn’t exist.</p> <p>I wrote a methodological letter for <em>JMIR AI</em> arguing for a <strong>parallel evaluation track</strong>. Same pipeline, evaluated twice:</p> <ol> <li>LLM-only, current setup. Score on AUC, accuracy, calibration.</li> <li>Retrieval-grounded against a fixed clinical corpus (CDC pediatric COVID guidance + WHO + IDSA). Score on <strong>citation faithfulness</strong>, <strong>evidence-grounded correctness</strong>, and <strong>subgroup robustness</strong>.</li> </ol> <p>This is an architectural shift, not a tuning refinement. RAG is not just a deployment pattern; it is an evaluation substrate.</p> <p>Letter in JMIR AI, 2026: <a href="/publications/#hu2026retrieval">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="clinical-AI"/><category term="RAG"/><category term="evaluation"/><category term="AUC"/><summary type="html"><![CDATA[Letter in JMIR AI on evaluating conversational clinical LLM systems.]]></summary></entry><entry><title type="html">End-to-end LLM clinical triage misses the steps that matter</title><link href="https://windtakemenorth.github.io/blog/2026/breast-pain-llm-commentary/" rel="alternate" type="text/html" title="End-to-end LLM clinical triage misses the steps that matter"/><published>2026-03-15T09:00:00+00:00</published><updated>2026-03-15T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/breast-pain-llm-commentary</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/breast-pain-llm-commentary/"><![CDATA[<p>Starting the MPhil, I deliberately let myself wander a bit before settling — reading across nutritional epi, genomics, sport-physiology, and clinical imaging — partly to know what the next year of work should look like, partly because I just enjoyed the surveying. This letter came out of that wandering period. A <em>Clinical Imaging</em> paper crossed my reading list: GPT-4 mapping free-text breast-pain descriptions to a binary triage recommendation. Sensitivity was reasonable, and the demonstration was useful. But the <strong>end-to-end design bothered me</strong>.</p> <p>Clinical reasoning for breast pain does not go directly from “free text” to “refer / don’t refer.” It goes via intermediate attributes — focality, cyclicity, associated red-flag features (mass, skin changes, lymphadenopathy) — and only then to a risk-stratified decision. An end-to-end LLM that skips attribute extraction is asking the model to implicitly infer features that are neither extracted nor verifiable.</p> <p>The original paper’s misclassifications cluster in cases with ambiguous or absent attribute information. That is exactly what you would expect if the model is failing on implicit feature inference.</p> <p>I wrote a methodological commentary arguing for a <strong>two-step pipeline</strong>: attribute extraction first, risk stratification second. Failures become localisable. Clinicians can override at the attribute level rather than at the decision level. That is what auditable clinical AI looks like.</p> <p>Letter in Clinical Imaging, 2026: <a href="/publications/#hu2026comment">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="clinical-AI"/><category term="LLM"/><category term="evaluation"/><category term="Cambridge"/><summary type="html"><![CDATA[Commentary in Clinical Imaging on a GPT-4 breast-pain triage paper.]]></summary></entry><entry><title type="html">From a Cambridge nutritional epi class to a letter in PHN</title><link href="https://windtakemenorth.github.io/blog/2026/tiktok-exposure-cambridge-class/" rel="alternate" type="text/html" title="From a Cambridge nutritional epi class to a letter in PHN"/><published>2026-02-18T09:00:00+00:00</published><updated>2026-02-18T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/tiktok-exposure-cambridge-class</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/tiktok-exposure-cambridge-class/"><![CDATA[<p>This one came out of my <strong>MPhil dissertation work</strong> on ultra-processed foods, supervised by <strong>Mike Essman</strong> and <strong>Jean Adams</strong> at Cambridge. Reading widely around UPFs and the food environment for the dissertation, I kept running into TikTok food-marketing surveillance papers — careful methodology, but the implicit step from “content prevalence” to “adolescent exposure” bothered me.</p> <p>On algorithm-driven platforms, what creators post is not what teenagers see. The platform decides. A handful of high-view posts can drive most of the actual exposure; a much larger number of low-view posts can drive almost none. Sampling content does not give you exposure unless you weight by views.</p> <p>Conversations with Mike, Jean, and other colleagues across the MRC Epidemiology Unit and CEDAR sharpened the argument. I wrote it up as a letter. <em>Public Health Nutrition</em> published it.</p> <p>The proposal is methodological: surveillance studies should report <strong>view-weighted prevalence</strong>, <strong>bounded sensitivity analysis</strong> for missing nutrient data, and <strong>audit multi-product appearances</strong>. None of these require platform-side data access; they make the inference defensible.</p> <p>Letter in Public Health Nutrition, 2026: <a href="/publications/#hu2026tiktok">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="TikTok"/><category term="food-marketing"/><category term="nutritional-epidemiology"/><category term="Cambridge"/><summary type="html"><![CDATA[A measurement objection to TikTok food-marketing surveillance studies, written from MPhil coursework.]]></summary></entry><entry><title type="html">From data to mechanism — continuing with Cemil, now under review at JEBO</title><link href="https://windtakemenorth.github.io/blog/2026/housing-mobility-follow-up/" rel="alternate" type="text/html" title="From data to mechanism — continuing with Cemil, now under review at JEBO"/><published>2026-02-10T09:00:00+00:00</published><updated>2026-02-10T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2026/housing-mobility-follow-up</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2026/housing-mobility-follow-up/"><![CDATA[<p>The empirical paper documented <em>that</em> US housing seasonality shifted. This one asks <em>why</em>.</p> <p>After the MDPI paper came out, <strong>Cemil Selcuk</strong> — my original undergrad supervisor at UCL, now at Cardiff — and I picked the project back up over the holidays. We turned the empirical pattern into a structural story. He brought the modelling discipline; I brought the data and the calibration. The whole thing was built across vacations and weekends, on top of the MPhil schedule, but the dynamic that started in his STAT0035 office is still what made it work.</p> <p>We extended <strong>Ngai-Tenreyro (2014)</strong> search-and-matching to monthly frequency, proved existence and uniqueness of the equilibrium, and calibrated to observed US data.</p> <p>The headline: a post-2021 shift in the <strong>timing of residential moves</strong> (SIPP household-mobility data, with Google Trends as a corroborating signal) is <strong>sufficient on its own</strong> to reproduce the spring shift in both prices and transaction volumes. We don’t need to invoke remote work, credit conditions, or housing supply shocks. The mobility channel alone gets you there. Those other channels may be operating too — they just aren’t required.</p> <p>The paper is <strong>currently under review at the <em>Journal of Economic Behavior and Organization</em> (JEBO)</strong>. Working paper version on SSRN: <a href="/publications/#hu2026summer">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="housing"/><category term="search-matching"/><category term="mobility"/><category term="working-paper"/><category term="JEBO"/><summary type="html"><![CDATA[Working paper extending Ngai-Tenreyro to monthly frequency. Mobility timing alone explains the spring shift. Under review at JEBO.]]></summary></entry><entry><title type="html">My first journal paper — started as a UCL undergrad project</title><link href="https://windtakemenorth.github.io/blog/2025/housing-seasonality-first-paper/" rel="alternate" type="text/html" title="My first journal paper — started as a UCL undergrad project"/><published>2025-12-15T09:00:00+00:00</published><updated>2025-12-15T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2025/housing-seasonality-first-paper</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2025/housing-seasonality-first-paper/"><![CDATA[<p>This one is special to me. It started as my <strong>STAT0035 third-year project at UCL Data Science</strong>, supervised by <strong>Cemil Selcuk</strong>. The question was simple: had US housing market seasonality changed since the pandemic? The textbook said summer peak, June-July, every year. The FHFA data after 2020 looked different to me, and I wanted to know whether the eye was right.</p> <p>It was. X-13-ARIMA on 33 years of FHFA HPI + Census transaction data: peak moved from May/June to March/April after 2020, amplitude grew, pattern consistent across most US regions.</p> <p>What I’m proud of is that I didn’t stop when the course did. After graduating, I teamed up with <strong>Yifei Huang</strong> — a close classmate and friend from the UCL stats department, who has since moved on to Northwestern University in the US — to extend the project into a full journal article. Together we worked through additional data, robustness checks, and the regional breakdown that ended up in the published version.</p> <p>It is rare for an undergrad project to make it all the way through to a published journal paper, and rarer still to keep building on it afterwards. The follow-up — a structural model with Cemil — is now <a href="/blog/2026/housing-mobility-follow-up/">under review at JEBO</a>.</p> <p>Open access in Real Estate (MDPI), 2025: <a href="/publications/#hu2025seasonality">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="housing"/><category term="economics"/><category term="seasonality"/><category term="UCL"/><summary type="html"><![CDATA[How the US housing seasonality paper began as STAT0035 at UCL Data Science and ended up in Real Estate (MDPI).]]></summary></entry><entry><title type="html">Where I started — a UCL undergrad project on K-means initialisation</title><link href="https://windtakemenorth.github.io/blog/2023/customer-clustering-ucl-stat/" rel="alternate" type="text/html" title="Where I started — a UCL undergrad project on K-means initialisation"/><published>2023-11-15T09:00:00+00:00</published><updated>2023-11-15T09:00:00+00:00</updated><id>https://windtakemenorth.github.io/blog/2023/customer-clustering-ucl-stat</id><content type="html" xml:base="https://windtakemenorth.github.io/blog/2023/customer-clustering-ucl-stat/"><![CDATA[<p>This is where my publication record actually starts. UCL Data Science, <strong>STAT0041 (Computational Statistics)</strong>. The course was taught by Professor <strong>Yvo Pokern</strong>, and the experience reshaped how I think about three things at once — statistics, algorithms, and programming. His teaching had a particular <strong>German rigour to it</strong>: an algorithm is not just a recipe to memorise but an object you derive, dissect, and rebuild from first principles. After that module I no longer experienced “stats” and “code” as two separate subjects. They were the same craft. This paper was the first thing I wrote with that perspective in mind.</p> <p>The annoyance that drove it: random and k-means++ initialisation can place initial centres in low-density regions, then converge to clusters that don’t match anything a marketer would recognise. The fix was almost embarrassingly simple — pick initial centres from the centroids of the densest grid cells in feature space. The interesting bit was the data representation. Treating customer features as interval-valued data (each feature an interval [min, max] capturing per-customer variability) rather than as point estimates preserved a layer of information that simpler approaches squashed.</p> <p>On simulation experiments: silhouette +0.1249 over k-means++, +0.4903 over vanilla K-means.</p> <p>Looking back, the methodological reflex that runs through everything I’ve done since started here. <strong>What is the data actually telling you, beyond the point estimate?</strong> That question carries from clustering all the way to TikTok exposure measurement and clinical LLM evaluation.</p> <p>Conference paper at ICIICS 2023 (IEEE): <a href="/publications/#hu2023customer">link</a>.</p>]]></content><author><name></name></author><category term="research-journey"/><category term="machine-learning"/><category term="clustering"/><category term="UCL"/><summary type="html"><![CDATA[My first published paper. Final-year project at UCL Data Science, ICIICS 2023.]]></summary></entry></feed>