> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/zh/cli-reference/run/dataset-worker.md).

# 数据集处理器

{% code fullWidth="true" %}

```
名称:
   singularity run dataset-worker - 启动数据集准备工作者进行数据集扫描和准备任务处理

使用方法:
   singularity run dataset-worker [命令选项] [参数...]

选项:
   --concurrency value  并发工作者的数量 (默认值: 1)
   --enable-scan        启用数据集扫描 (默认值: true)
   --enable-pack        启用数据集打包，计算CIDs，并将其打包为CAR文件 (默认值: true)
   --enable-dag         启用数据集的DAG生成，保持数据集的目录结构 (默认值: true)
   --exit-on-complete   当没有更多任务需要处理时退出工作者 (默认值: false)
   --exit-on-error      当出现任何错误时退出工作者 (默认值: false)
   --help, -h           显示帮助信息
```

{% endcode %}


---

# 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://data-programs.gitbook.io/singularity/zh/cli-reference/run/dataset-worker.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.