> For the complete documentation index, see [llms.txt](https://cmo-ci.gitbook.io/cci/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmo-ci.gitbook.io/cci/the-onboarding/collaborations.md).

# Collaborations

This will help you to find correct people to connect with from the subgroups.

{% hint style="info" %} <mark style="color:blue;">**In all the groups there are multiple amazing individuals involved, but listing just a few**</mark>
{% endhint %}

## Confluence knowledgebase **across collabrators**

{% embed url="<https://mskconfluence.mskcc.org/x/vzV2B>" %}
Link to Knowledgebase for information across groups
{% endembed %}

## **CMO Project Managers**

CCI works closely with CMO project managers to track the progress of cfDNA projects submitted to CMO by MSK researchers. CMO project managers support CCI by facilitating and coordinating project initiation, sample collection, and metadata collection.

### People to connect

* [Kirsten Fuller](mailto:fullerk@mskcc.org)
* [Casey Savin](mailto:SavinC@mskcc.org)
* [Jennifer Milbank](mailto:MilbankJ@mskcc.org)

## Integrated Genomics Operations (IGO)

CCI works with to make sure that the data generated for the cfDNA assays is of the highest standards.

### People to connect

* [Neeman Mohibullah](mailto:mohibuln@mskcc.org)
* [Ruchi Patel](mailto:patelr1@mskcc.org)
* [Marisa Dunigan](mailto:duniganm@mskcc.org)
* [David Mcmanamon](mailto:mcmanamd@mskcc.org)

## **CMO Informatics (CI)**

&#x20;CCI works closely with CMO Software Engineering (CSE) team within CI to support the development of Voyager & Hermes. The CSE/CAS team supports the development, integration, processing of CCI’s workflows implemented in Voyager.&#x20;

### People to connect

#### CMO Software Engineers (CSE)

* [Christopher Allan Bolipata](mailto:bolipatc@mskcc.org)
* [Sinisa Ivkovic](mailto:ivkovics@mskcc.org)
* [Nikhil Kumar](mailto:kumarn1@mskcc.org)

#### CMO Analysis Systems (CAS)

* [Timothy Song](mailto:songt@mskcc.org)
* [Stephen Kelly](mailto:KellyS5@mskcc.org)
* [Suleman Vural](mailto:vurals@mskcc.org)

## **Berger Lab/Technology Innovation Lab/CMO Computational Science (CCS)**&#x20;

CCI collaborates with scientists in various CMO groups to improve the existing workflows and to analyze the data in a consistent manner. &#x20;

### People to connect

#### Berger Lab

* [Kanika Arora](mailto:AroraK@mskcc.org)
* [Shalabh Suman](mailto:sumans@mskcc.org)
* [Chaitanya Bandlamundi](mailto:bandlamc@mskcc.org)

#### Technology Innovation Lab

* [Brian Loomis](mailto:loomisb@mskcc.org)
* [David Brown](mailto:brownd7@mskcc.org)

#### CMO Computational Sciences (CCS)

* [Mark Donoghue](mailto:donoghum@mskcc.org)
* [Yixiao Gong](mailto:gongy@mskcc.org)

## **Clinical Bioinformatics (ClinBx)**

CCI works closely with the ClinBx group in the Molecular Diagnostics Service to deploy core workflows and maintain consistency among analyses performed on research and clinical cfDNA samples. We work together to improve the workflows in sync and to learn from one another about how to identify artifacts and interpret the data. CCI is also working with the ClinBx Software group to port an instance of the mPATH system used by the ClinBx team to sign-out cases for research.

### People to know

[Rose Brannon](mailto:brannona@mskcc.org)

[Aijazuddin Syed](mailto:syeda1@mskcc.org)

[Ryan Ptashkin](mailto:ptashkir@mskcc.org)

[Anoop Balakrishnan](mailto:balakra1@mskcc.org)

## **High Performance Computing (HPC)**

CCI works with HPC to request resources and support w\.r.t JUNO cluster and virtual machines that enable various aspects of our goals.

[Neeraj Girija](mailto:girijapn@mskcc.org)

[Lohit Valleru](mailto:vallerul@mskcc.org)

Slack Channel

<hpc-request@cbio.mskcc.org>

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cmo-ci.gitbook.io/cci/the-onboarding/collaborations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.