<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The upgrade of the LHCb trigger system · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1410.5012/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1410.5012/feed.xml" rel="self" type="application/rss+xml" /><item><title>The upgrade of the LHCb trigger system — mentioned by magicalhippo</title><link>https://news.ycombinator.com/item?id=38836808</link><guid isPermaLink="false">urn:hackerpapers:mention:1410.5012:38836808</guid><pubDate>Tue, 02 Jan 2024 00:46:50 GMT</pubDate><description>&lt;p&gt;&amp;gt; because you cannot save all data (waste of time and resources) AFAIK, at least for ATLAS and CMS, the sheer amount of raw data the sensors produce, like 40TB/s or more[1], requires using triggers to reduce the captured data rate. Even after that first trigger there&amp;#x27;s still over 100GB/s, which is too much for storing directly. Interestingly though, due to its design the LHCb detector has a lower intrinsic luminosity (ie less stuff happening) and so was able to move to a fully software-based trigger system[2]. This allows them to change the trigger parameters &amp;quot;at will&amp;quot;, unlike the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1410.5012/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>physics.ins-det</category></item></channel></rss>
