> For the complete documentation index, see [llms.txt](https://clinical-genomics.gitbook.io/project-mip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clinical-genomics.gitbook.io/project-mip/develop/documentation/api/path.md).

# Path

*"On heights all paths are paved with dagger -Old Seanchan saying"*

1. "a/dir/file\_1.1.txt"
2. "a/dir/file\_1.txt"

## Definitions:

### Array file features

#### file\_paths:

Complete paths

* \[0] "a/dir/file\_1.1.txt"
* \[1] "a/dir/file\_1.txt"

#### file\_suffixes:

Including first "." and everything after

* \[0] ".1.txt"
* \[1] ".txt"

#### file\_path\_prefixes:

Paths without suffix

* \[0] "a/dir/file\_1"
* \[1] "a/dir/file\_1"

#### file\_names:

File names

* \[0] "file\_1.1.txt"
* \[1] "file\_1.txt"

#### file\_name\_prefixes:

File names without suffix

* \[0] "file\_1"
* \[1] "file\_1"

### Scalar file features

#### dir\_path:

Directory path

* "a/dir/"

#### dir\_path\_prefix:

Directory name without trailing slash

* "a/dir"

**file\_suffix:**

Everything after last "."

* ".txt"

### Constant file features

#### file\_path\_prefixes:

Paths without suffix

* "a/dir/file\_1"

#### file\_name\_prefix:

File name without suffix

* "file\_1"

**file\_constant\_suffix:**

Only for identical file\_suffixes otherwise undef

For paths:

* \[0] "a/dir/file.1.txt"
* \[1] "a/dir/file.1.txt"

*file\_constant\_suffix*:

* ".1.txt"

### Hash file features

iterator: string between dots in file\_suffixes, e.g. ".1.txt" => iterator = "1".

#### file\_path\_href:

Complete paths per iterator. { 1 => "a/dir/file\_1.1.txt", }

#### file\_name\_href:

File name per iterator. { 1 => "file\_1.1.txt", }


---

# 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://clinical-genomics.gitbook.io/project-mip/develop/documentation/api/path.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.