> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive/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/archive/bootcamp-2021/schedule/thursday-6-may.md).

# Thursday, 6 May

Bioinformatics Essentials

## Foundations for Bioinformatics Data Analyses | 9:30 - 11:00 EDT

This session we will discuss the most common file formats used in bioinformatics, some resources for accessing public datasets (like the SRA), and a few other helpful bioinformatics QC tools

## Basic Bioinformatics Workflows on Oscar: BioFlows | 11:00 - 12:00 EDT

This session will address how you can use Bioflows to manage your analysis pipelines. Bioflows will automate job scheduling, impose a standardized organization to your files and folders, and write useful log files for debugging.

## Annotation Resources for Downstream Analyses Using Bioconductor | 1:30 - 3:00 EDT

The last formal session of the day is devoted to annotation resources and downstream analyses of NGS data using R and Bioconductor. We will cover different annotation file formats, public resources for annotation data, and leveraging those resources for downstream analyses in R.

## Bioinformatics Q\&A Session | 3:00 - 4:00 EDT

We will devote the last hour of the day for your bioinformatics on Oscar questions.


---

# 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://docs.ccv.brown.edu/archive/bootcamp-2021/schedule/thursday-6-may.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.
