> For the complete documentation index, see [llms.txt](https://docs.segments.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.segments.ai/how-to-annotate/label-3d-point-clouds/batch-mode-for-dynamic-objects.md).

# Batch mode (for dynamic objects)

{% hint style="info" %}
Batch mode is only available for 3D cuboid labeling.
{% endhint %}

{% hint style="info" %}
Tip: [use your GPU in Chrome](https://segmentsai.notion.site/How-to-use-your-GPU-in-Chrome-2b95e19fb77c456c87f798013769a98a) to make sure the 3D point cloud interface runs smoothly.
{% endhint %}

When labeling or reviewing dynamic objects in 3D point cloud sequences, working object by object is usually the most efficient way to obtain precise annotations. However, this means navigating through the different frames in a sequence constantly. To make this process more efficient, we developed batch mode. Batch mode shows you an object in multiple frames at the same time. This way, you can easily choose where to make adjustments to label an object, and easily review an object by simply scrolling through the frames.

{% embed url="<https://youtu.be/om5w69OErVs?t=121>" %}
This video shows how you can use batch mode to quickly adjust a cuboid.
{% endembed %}

## Toggle the batch mode

1. Select the object you want to adjust/review.
2. Click on the batch mode icon (![](https://1553794111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHczBG7NHgAtEe4ql1rXH%2Fuploads%2FatmUhoEqWfOf6EVfD6Nd%2Fimage.png?alt=media\&token=c20e01f4-73b2-4f14-960a-cc381cb60c03)) in the right toolbar to toggle batch mode on/off.

You can also exit batch mode by pressing the hotkey (`Escape` by default).

## Select a frame

Clicking somewhere in a frame to select the frame. If you want to select the previous or next frame, press the back or forward arrow, respectively.

## Zoom in/out

* Double-click a view to zoom in on that view.
* Press the hotkey (`Shift` by default) + double-click a view to zoom out on that view.

## Edit the object

Object editing works exactly in the same way as in the single frame interface, so you can still use your mouse or the hotkeys. See the following pages:

{% content-ref url="/pages/STCGOim5NnMFMZG2yqMP" %}
[3D point cloud cuboid interface](/how-to-annotate/label-3d-point-clouds/3d-point-cloud-cuboid-interface.md)
{% endcontent-ref %}

## Remove the object

1. Select the frame where you want to remove the object.
2. Press the trash icon on the left of the frame.

## Add the object to an empty frame

1. Select the empty frame where you want to add the object.
2. Press the plus icon on the left of the frame.

## Use keyframes

Keyframes work in the same way as in the single frame interface, see [Use keyframe interpolation](/how-to-annotate/label-sequences-of-data/use-keyframe-interpolation.md). The only difference is that keyframes are now displayed directly next to the frame.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.segments.ai/how-to-annotate/label-3d-point-clouds/batch-mode-for-dynamic-objects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.