Skip to content

Commit

Permalink
Merge Split Branch
Browse files Browse the repository at this point in the history
  • Loading branch information
actions-user committed Jul 25, 2024
2 parents d917661 + 89151e9 commit 271924c
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 17 deletions.
2 changes: 1 addition & 1 deletion preview-update-submodules/assets/search/index.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion preview-update-submodules/assets/search/metadata.json

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions preview-update-submodules/collaborations-epic-eic.html
Original file line number Diff line number Diff line change
Expand Up @@ -226,15 +226,15 @@ <h1 class="uw-mini-bar mb-4">
<img style="width:100%" src="https://raw.githubusercontent.com/CHTC/Articles/main/images/epic-eic-collab.jpg" alt=" Electron Beam Ion Source / Brookhaven National Laboratory" />
<figcaption>Electron Beam Ion Source / Brookhaven National Laboratory</figcaption>
</figure>
<p><br /><br />Seeking to unlock the secrets of the glue” binding visible matter in the universe, the <a href="https://www.bnl.gov/eic/epic.php">ePIC Collaboration</a> stands at the forefront of innovation. Led by a collective of hundreds of scientists and engineers, the Electron-Proton/Ion Collider (ePIC) Collaboration was formed to design, build, and operate the first experiment at the <a href="https://www.bnl.gov/eic/">Electron-Ion Collider</a> (EIC). This experiment aims to construct the world’s most advanced particle detector, capable of analyzing collisions between electrons and protons or other atomic nuclei.</p>
<p><br /><br />Seeking to unlock the secrets of the glue” binding visible matter in the universe, the <a href="https://www.bnl.gov/eic/epic.php">ePIC Collaboration</a> stands at the forefront of innovation. Led by a collective of hundreds of scientists and engineers, the Electron-Proton/Ion Collider (ePIC) Collaboration was formed to design, build, and operate the first experiment at the <a href="https://www.bnl.gov/eic/">Electron-Ion Collider</a> (EIC). This experiment aims to construct the world’s most advanced particle detector, capable of analyzing collisions between electrons and protons or other atomic nuclei.</p>

<p>“They are building a detector that can slide seamlessly into EIC’s infrastructure. When these collisions occur, they will capture a wealth of physics data that advances our understanding of high-energy nuclear interactions. The outcomes of these collisions allow us to explore new frontiers in physics” reports Pascal Paschos, the OSG Consortium Facilitator who supports the work of ePIC. Paschos oversees the collaborations’ access to computational capacity necessary to conduct these experiments.</p>

<p>The EIC, developed by the collaboration between <a href="https://www.bnl.gov/about/">Brookhaven National Lab</a> (BNL) and <a href="https://www.jlab.org/">Jefferson Lab</a> (JLab), will be the world’s first electron-nucleus collider of its kind. It features two intersecting accelerators—one generating a powerful polarized electron beam and the other a high-energy beam of polarized protons or heavier atomic nuclei. However, ePIC faces the challenge of validating the detector design for integration with the EIC. Paschos explains, “To validate the detector design, throughput capacity is required to model and experimentally simulate the detector. The goal is to evaluate how the detector would respond to signals generated from theoretical collisions included in their parameter files.”</p>

<p>“This project isn’t new,” adds <a href="http://wouterdeconinck.com/">Dr. Wouter Deconinck</a>, associate professor at the University of Manitoba and Deputy Software and Computing Coordinator (SCC) for Operations at ePIC. “Concepts for an electron-ion collider have been in development for 20 or 30 years, aiming to include a polarized ion beam.” Drawing on his experience at the <a href="https://en.wikipedia.org/wiki/HERA_(particle_accelerator)">HERA</a> electron-proton collider and post-graduate work in electron polarimetry, Deconinck, alongside BNL postdoctoral fellow <a href="https://www.bnl.gov/staff/srahman1">Sakib Rahman</a>, explains, “Since 2008, we’ve been evaluating the computing and software stacks needed for an electron-ion collider. Planning for operation into the 2030s necessitates future-proof and modular development to incorporate emerging technologies.”</p>

<p>Achieving a unified system is one important goal for the project. ePIC requires an infrastructure capable of simulating and gathering essential data for their design. One option was the <a href="https://osg-htc.org/services/open_science_pool.html">OSPool</a>, a shared computing capacity available to researchers affiliated with US academic institutions. Deconinck and Rahman considered other computing infrastructures for these simulation jobs. Deconinck notes, “We evaluated the OSPool and compared it with the EIC pool of resources available at JLab, BNL and the <a href="https://alliancecan.ca/en">Digital Research Alliance of Canada</a> (the Alliance.) Both pools were capable of handling about 2,000 jobs at a time.” Ultimately selecting the OSPool, Deconinck notes,“We saw it as a way to convince JLab to allocate jobs to the OSPool indirectly, transferring jobs to the Alliance, and continuing to submit to the OSPool. The primary advantage was achieving a unified interface across all these sites.”</p>
<p>Achieving a unified system is one important goal for the project. ePIC requires an infrastructure capable of simulating and gathering essential data for their design. One option was the <a href="https://osg-htc.org/services/open_science_pool.html">OSPool</a>, a shared computing capacity available to researchers affiliated with US academic institutions. Deconinck and Rahman considered other computing infrastructures for these simulation jobs. Deconinck notes, “We evaluated the OSPool and compared it with the EIC pool of resources available at JLab, BNL and the <a href="https://alliancecan.ca/en">Digital Research Alliance of Canada</a> (the Alliance.) Both pools were capable of handling about 2000 jobs at a time.” Ultimately selecting the OSPool, Deconinck notes,“We saw it as a way to convince JLab to allocate jobs to the OSPool indirectly, transferring jobs to the Alliance, and continuing to submit to the OSPool. The primary advantage was achieving a unified interface across all these sites.”</p>

<p>Rahman also emphasizes OSPool’s role in the integrated system, stating, “Previously, someone had to create accounts on every site to submit jobs. Now, running production campaigns, others need an account on one <a href="https://path-cc.io/about/">PATh</a> operated Access Point, with their work credited to ePIC. This detachment from individual operators and alignment with the project as a whole significantly reduces onboarding time.”</p>

Expand Down
32 changes: 19 additions & 13 deletions preview-update-submodules/fellowships/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -232,14 +232,14 @@ <h1 class="uw-mini-bar mb-4">

<h2 id="featured-fellow">Featured Fellow</h2>

<div id="ryan-boone" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
<div id="patrick-brophy" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
<div class="uw-card-content shadow">
<div class="row">
<div class="col-3">
<div class="overflow-hidden d-flex justify-content-center">


<img src="/web-preview/preview-update-submodules/staff-list/images/ryan_boone.jpg" alt="Headshot for Ryan Boone" />
<img src="/web-preview/preview-update-submodules/staff-list/images/patrick_brophy.jpg" alt="Headshot for Patrick Brophy" />

</div>
</div>
Expand All @@ -248,24 +248,30 @@ <h2 id="featured-fellow">Featured Fellow</h2>
<div>
<h2 class="uw-mini-bar mb-0 mt-3">

Ryan Boone
Patrick Brophy

</h2>
<div><h6 class="mt-2">Mentor(s):</h6> Cole Bollig and Rachel Lombardi</div>
<div><h6 class="mt-2">Mentor(s):</h6> Haoming Meng</div>
</div>
</div>
</div>
<div class="col-12">
<h4 class="mt-3">Grid Exerciser</h4>
<h4 class="mt-3">Expanded Pelican Origin Monitoring</h4>
<div class="pt-2">
<p>The OSPool is a very large, very dynamic, heterogenous high throughput system composed of execute
points from dozens of campuses all over the United States. Sometimes, something will go wrong
at one of these many sites, or one network, or one storage point, and it is difficult to determine
where the problem is. This project proposed the design and construction of a “Grid Exerciser”,
which consists of intentionally sending sample jobs to targetted locations on the OSPool to verify
correct operation and sufficient performance. The project will also have a reporting and
visualization component so that the voluminous results can be understood by a human in a
concise manner.</p>
<p>The Pelican origin service is responsible for exporting objects in the backend
storage to the data federation. As it is the “entry point” for the data, understanding
the load on the origin and its activities is key to keeping the federation healthy.<br />
Pelican takes monitoring data from the web server component and feeds it into the popular
Prometheus software to store time series about the activity. This project would focus on:</p>
<ul>
<li>Implementing new monitoring probes to complement the existing information.</li>
<li>Forwarding the raw, unsummarized data to an ElasticSearch database for further analysis.</li>
<li>Designing visualizations to provide administrators with an overview of the origin’s activities.</li>
<li>Implementing alerts when there are health issues with the origin.</li>
</ul>

<p>After a successful summer, the student fellow will gain skills in using the Go
language, the Prometheus monitoring system (and other Cloud Native technologies), and web design.</p>

</div>
</div>
Expand Down

0 comments on commit 271924c

Please sign in to comment.