Skip to content

Commit 17144a3

Browse files
authored
Merge pull request #27 from fallow64/2025-fellows
Add 2025 fellows
2 parents 9957f06 + 1c44244 commit 17144a3

File tree

6 files changed

+84
-0
lines changed

6 files changed

+84
-0
lines changed

images/kashika_mahajan.png

3.64 MB
Loading

images/sandhya_nayar.jpg

322 KB
Loading

images/william_jiang.png

290 KB
Loading

kashika_mahajan.yml

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
name: Kashika Mahajan
2+
title: Fellow
3+
institution: Morgridge Institute for Research
4+
status: Past
5+
organizations:
6+
- chtc
7+
image: images/kashika_mahajan.png
8+
9+
10+
fellowship:
11+
name: Research Facilitation Project
12+
description: |
13+
Researchers often have a hard time quickly figuring out how their
14+
computational workloads are doing. The way cluster data is currently
15+
shown through the system can be overwhelming and hard to
16+
interpret, especially for someone who isn't deeply familiar with
17+
how everything works. It's not always obvious whether their jobs
18+
are running smoothly, stuck, or underperforming.
19+
20+
That's what this project set out to fix. We wanted to build tools
21+
that make it easier for researchers to understand what's going on
22+
with their jobs, without having to dig through complicated logs
23+
or system outputs. A big part of the process was also figuring
24+
out what information researchers actually care about most, and
25+
how we could present that in a way that's simple, useful, and
26+
clear.
27+
mentor: Andrew Owen and Ian Ross

sandhya_nayar.yml

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
name: Sandhya Nayar
2+
title: Fellow
3+
institution: Morgridge Institute for Research
4+
status: Past
5+
organizations:
6+
- chtc
7+
image: images/sandhya_nayar.jpg
8+
9+
10+
fellowship:
11+
name: Smart Aggregation and Indexing with the Archive Librarian
12+
description: |
13+
HTCondor saves large amounts of useful data about finished jobs
14+
that can help administrators, facilitators, and researchers
15+
who are trying to utilize historical job data. Currently,
16+
condor_history manually parses through flat files to get users
17+
their data; this makes it significantly harder to use, especially
18+
for older jobs, with no easy way to create useful aggregates.
19+
20+
This project focused on the creation of the “Archive Librarian” service,
21+
to index job records from the HTCondor history archive and
22+
improve the usability of historical job data. Each job's “address”,
23+
which is the combination of an offset and file metadata of a
24+
historical archive file, is stored in a database. This allows
25+
the librarian to directly locate job records and avoid using a
26+
sequential scan. The database also stores relevant job attributes
27+
that researchers commonly rely on, enabling future support for
28+
complicated queries and aggregate statistics.
29+
mentor: Cole Bollig and Todd Tannenbaum

william_jiang.yml

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
name: William Jiang
2+
title: Fellow
3+
institution: Morgridge Institute for Research
4+
status: Past
5+
organizations:
6+
- chtc
7+
- pelican
8+
image: images/william_jiang.png
9+
10+
11+
fellowship:
12+
name: Integrating Pelican and Globus
13+
description: |
14+
The Pelican Platform is an open-source software platform designed to create
15+
data federations by unifying diverse data repositories (e.g. POSIX
16+
filesystems, S3) under a single architecture. It differs from the Globus
17+
project, whose main goal is to facilitate peer-to-peer data transfer, and it
18+
thus lacks the means to plug into cluster scheduling frameworks like HTCondor.
19+
20+
This project focused on bridging the gap between Pelican and Globus by
21+
integrating Globus transfer capabilities into Pelican. This will allow users
22+
to leverage Globus's robust data transfer features while benefiting from
23+
Pelican's unified data access model. The integration involved developing a
24+
Globus backend for Pelican and enabling seamless data transfers between
25+
Pelican-managed repositories and external systems via Globus.
26+
27+
28+
mentor: Emma Turetsky and Justin Hiemstra

0 commit comments

Comments
 (0)