> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/oscar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/oscar/dbgap-data/dbgap-project.md).

# dbGaP Architecture

The database of Genotypes and Phenotypes (dbGaP) was developed to archive and distribute the data and results from studies that have investigated the interaction of genotype and phenotype in Humans. The PI is responsible for completing the [NIH dbGaP application online](https://dbgap.ncbi.nlm.nih.gov/aa/wga.cgi?page=login).

## dbGaP Oscar Implementation

* The dbGap data is stored on the Isilon enterprise storage
  * All input/output data must go through the dbGap transfer server
  * Access to the dbGap transfer server and data is controlled by AD groups
  * A PI needs to request an AD group for a dbGap project
* Computing is performed on Oscar
  * DbGap jobs must be submitted to the `dbGap partition`, whose access is controlled by AD groups
  * A dbGap job runs exclusively on one or more nodes (serial or MPI jobs)
  * No internet access on the dbGap nodes when a job is running
  * A dbGap job can only access input and output directories in Isilon
    * Input directory: `/dbGaP/data/import/<dbGap_project>`
    * Output directory: `/dbGap/results/<dbGap_project>`
  * A dbGap job has access to Matlab and Intel license servers

To request access to dbGaP service please [submit this form](https://brown.co1.qualtrics.com/jfe/form/SV_2685FSGrZ4S7i62).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ccv.brown.edu/oscar/dbgap-data/dbgap-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.