> For the complete documentation index, see [llms.txt](https://docs.virtual-flow.org/documentation-vf1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.virtual-flow.org/documentation-vf1/vflp/untitled-2/untitled-1.md).

# Input & Output Databases

The input and output ligand database are in the standard VirtualFlow format as described [here](/documentation-vf1/principles-and-theory/naming-conventions.md). 

## Input Ligand Databases

In VFLP, the ligands (fourth hierarchical level) in the input databases are stored as plain text files in the SMILES format. The filename ending of each file has to be `.smi`.  Each ligand in the SMILES format only contains the SMILES, and no additional information. 

## Output Ligand Databases

In VFLP, the output ligand databases contain for each ligand a text file. The chemical file format depends on the target file format which is specified in the control file. Multiple output databases can be generated at the same time when specified so in the control file.


---

# 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.virtual-flow.org/documentation-vf1/vflp/untitled-2/untitled-1.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.