> For the complete documentation index, see [llms.txt](https://gitbook.bergelsonlab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.bergelsonlab.com/data-pipeline/basic-levels/faq.md).

# Troubleshooting

<details>

<summary>Why do I get warnings that we have nouns in skip regions when I update basic level files (aka sparse code csvs)? Didn't we remove all of those?</summary>

When you run \`blabpy.seedlings.pipeline.make\_updated\_basic\_level\_files\`, you might see a bunch of warnings like this one:

```
WARNING:root:Object word was found in a skip region. Fix this in the .cha file.
```

The reason is that skips are defined differently for months 6 and 7 and for the other months and it is perfectly normal to have nouns in month 6 and 7 skips. There used to be a few annotations in other months' recordings too but those were removed by Hallie and Zhenya in 2023.

Getting those warning and not being 100% sure they come only from month 6 and 7 recordings is not ideal, of course. To fix it, find where this warning is issued in blabpy and make sure `make_updatred_basic_level_files` passes smth like an `ignore_words_in_skips` parameter to that lower-level function and it is set to True iff the month is either "06" or "07".

</details>


---

# 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:

```
GET https://gitbook.bergelsonlab.com/data-pipeline/basic-levels/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.