> 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/kr/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/kr/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.