> For the complete documentation index, see [llms.txt](https://clipforum.flow.bio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clipforum.flow.bio/to-be-answered.md).
# To be Answered
* **How to accurately compare two CLIP libraries of the same RBP with \~10-fold difference of CLIPped RBP abundance in the cell? How can we account for RBP/target RNA ratio?**
* **Is it necessary to use spike ins, and if so, what kind of spike ins and how should I analyse this?**
* **How do I choose/remove redundant annotations from genome annotation files?**
* **How can I compare multiple RBP baits with different IP efficiencies?**
* **What are the best ways to access and analyze published CLIP data?**
* **What available pipelines are out there for analysing different CLIP datasets (iCLIP & PAR-CLIP)? Are there advantages/disadvantages to different established pipelines?**
* **Which statistical methods are best at identifying cross-link sites?**
---
# 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://clipforum.flow.bio/to-be-answered.md?ask=&goal=
```
`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.