> For the complete documentation index, see [llms.txt](https://janelia-flyem.gitbook.io/neutu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://janelia-flyem.gitbook.io/neutu/body-proofreading/correcting-false-splits.md).

# Correcting False Splits

Neurons may be over-segmented or falsely split and proofreaders must identify and merge segments to create the neuron of interest. Three steps are required to correct false splits:&#x20;

1. Select the bodies or segments for merging
2. Group
3. Upload&#x20;

The user’s ability to undo and the status of the body at each step is summarized in the table below.    &#x20;

| Step | Action                                                    | Update server | Lock bodies            | Ability to undo operation | Body ID                                                   |
| ---- | --------------------------------------------------------- | ------------- | ---------------------- | ------------------------- | --------------------------------------------------------- |
| 1    | Select bodies for merging by clicking and adding segments | No            | N/A                    | Yes                       | Each segment has a different body ID                      |
| 2    | Group                                                     | Yes           | Lock after grouping    | Yes                       | Each segment has a different body ID                      |
| 3    | Upload                                                    | Yes           | Unlock after uploading | No                        | Segments have the same body ID (considered one body now). |

## Basic instructions for merging bodies

1\. Select the body by either clicking on the body in the 2D image, double-clicking on a bookmark, or entering the body ID directly into the Go-to-Body function (short-cut for this option is F1).

![](/files/-Lz91IIgzCmEy2z33rVP)

2\. Choose the normal view or transparent view (also called h mode) in 2D and open the 3D coarse view.  Note that scrolling through z is much faster in h mode than normal view.

3\. Select bodies or segments for merging by clicking directly on the segmentation or draw a bounding box around the bodies. Press Shift + r to draw a box and then press “s” to select all bodies in the bounding box. Before executing the merge, it is important to inspect the bodies in the 3D coarse body viewer. Remove any bodies that are inappropriate by clicking on the body in the 2D segmentation window. After approving the bodies for merging, click ‘m’ for merge or press \<Group>.&#x20;

![](/files/-Lz93ryXQq6RcfzlE11G)

{% hint style="info" %}
This operation doesn’t save the result to the server. Even though the bodies are the same color, the body IDs have not been changed!&#x20;
{% endhint %}

4\. Click “Upload results” after approving the merge. The results will be uploaded to the server and you can not undo!


---

# 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://janelia-flyem.gitbook.io/neutu/body-proofreading/correcting-false-splits.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.
