<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Usage of GPUs in ALICE Online and Offline processing during LHC Run 3 · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2106.03636/</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/2106.03636/feed.xml" rel="self" type="application/rss+xml" /><item><title>Usage of GPUs in ALICE Online and Offline processing during LHC Run 3 — mentioned by akubera</title><link>https://news.ycombinator.com/item?id=40230622</link><guid isPermaLink="false">urn:hackerpapers:mention:2106.03636:40230622</guid><pubDate>Wed, 01 May 2024 22:52:53 GMT</pubDate><description>&lt;p&gt;What makes you think it&amp;#x27;s not compressed? (or that the data is stored as XML?) There&amp;#x27;s very sophisticated compression systems throughout each experiment&amp;#x27;s data acquisition pipelines. For example this paper[1] describes the ALICE experiment&amp;#x27;s system for Run3, involving FPGAs and GPUs to be able to handle 3.5TB/s from all the detectors. This one [2] outlines how HL-LHC &amp;amp; CMS use neural networks to fine tune compression algorithms on a per-detector basis. Not to mention your standard data files are ROOT TFiles with TTrees which store arrays of compressed objects. It&amp;#x27;s all pretty neat. [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2106.03636/"&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>
