# Building GRC

https://akougkas.io/work/building-grc/

Author: Anthony Kougkas

Updated: 2026-08-27

## The question

What would a research environment look like if it treated people, software, and ideas as parts of the same system?

When I arrived in Chicago in 2013, high-performance computing at [Illinois Tech](https://www.iit.edu/) was mostly one faculty laboratory, the Scalable Computing Software lab that [Xian-He Sun](https://www.iit.edu/directory/people/xian-he-sun) had run since 1999. I did my PhD there, led its research and student development from 2019, and by 2023 the work had outgrown a lab. That year Xian-He and I co-founded the [Gnosis Research Center](https://grc.iit.edu/).

GRC grew from a practical need. Ambitious systems work takes longer than a semester and involves more than a paper: repositories, releases, machines, proposals, documentation, mentoring, collaborations, and the confidence to try a direction that might fail. Those pieces compound only when someone tends the connections between them.

## The organizational bet

My bet is that a center can be rigorous without becoming impersonal, and entrepreneurial without pretending every prototype is a company. It can give people ownership while maintaining enough shared structure that their work survives a graduation, a deadline, or a change of direction.

That means treating research operations as design work. How do we decide what to build? Who owns a component? What evidence makes a claim ready? How does a student learn to review, release, teach, and explain, not only implement? What should become shared infrastructure, and what should remain a focused experiment?

## Who is here

The center now has research faculty, engineers, and a dozen PhD students, working with partners at [Argonne](https://www.anl.gov/), [The HDF Group](https://www.hdfgroup.org/), [Sandia](https://www.sandia.gov/), [Livermore](https://www.llnl.gov/), [Oak Ridge](https://www.ornl.gov/), [Pacific Northwest](https://www.pnnl.gov/), [Utah](https://www.utah.edu/), and [Chicago](https://www.uchicago.edu/).

Two outcomes I am especially glad about. [Luke Logan](https://grc.iit.edu/center/team/luke-logan/) and [Jaime Cernuda](https://grc.iit.edu/center/team/jaime-cernuda/), who both did their PhDs inside these systems, chose to stay on as research faculty in January 2026. Luke now leads software engineering, including day-to-day [CLIO Core](https://akougkas.io/work/clio/) engineering; Jaime leads student development and day-to-day [Agent and Relay](https://akougkas.io/work/clio/) development. [Kun Feng](https://grc.iit.edu/center/team/kun-feng/) runs the center’s infrastructure, and [Eneko Gonzalez](https://grc.iit.edu/center/team/eneko-gonzalez/) led its product work until September 2026.

## What we are building

The visible outputs are systems, papers, talks, tutorials, and open repositories: [IOWarp](https://akougkas.io/work/iowarp/) and [CLIO](https://akougkas.io/work/clio/), [ChronoLog](https://akougkas.io/work/chronolog/), [LABIOS](https://akougkas.io/work/labios/), the [DeepIO](https://akougkas.io/work/deepio/) line, and the completed [Hermes](https://akougkas.io/work/hermes/) and [DTIO](https://akougkas.io/work/dtio/). Underneath them is an operating practice: regular technical exchange, explicit ownership, public artifacts when work is ready, and a willingness to connect foundational research with tools people can run. In 2025 I started a Friday seminar on AI-assisted programming for the graduate researchers, because the tools were changing faster than any curriculum.

## My role

My role is to frame research directions, create proposals, build teams and partnerships, align milestones, integrate the systems, coauthor the research, report to sponsors, and remove obstacles without taking technical leadership away from other people. I do not always get the balance right. Too little structure strands people; too much structure turns research into ticket processing.

The goal is independent judgment. A strong mentee should eventually disagree with my architecture for reasons I did not see, then have the evidence and communication skill to carry a better idea forward.

## The entrepreneurial edge

I use “entrepreneurial” here in its oldest useful sense: noticing an unmet need, assembling people and resources, accepting uncertainty, and making something durable enough to test in the world. Sometimes that becomes software infrastructure, a new collaboration, a community, or a proposal. The measure is whether the work creates new agency for the people around it.

## What I am still learning

- How to preserve speed without building around a single person’s memory.
- How to make evidence and disclosure boundaries part of everyday development.
- How to give emerging researchers ownership with a safe place to fail.
- How to keep the center technically ambitious, publicly useful, and human as it grows.
