ale-tasks-chip / README.md
sunyiyou's picture
Describe this dataset: repository, layout, access
5c5f172 verified
|
Raw History Blame Contribute Delete
2.38 kB
metadata
pretty_name: ALE Tasks — Chip Design (assets)
tags:
  - agents-last-exam
  - ale-task-assets

ALE Tasks — Chip Design: Task assets

The Hugging Face side of AgentsLastExam/ale-tasks-chip. That repository keeps its Tasks' code and configuration in Git; this dataset holds all of their material (inputs, reference deliverables, rubric and source documents) under the same paths. The rules are the Task repository conventions.

No Task material is here yet; it arrives with each Task's first ale assets push.

Layout

tasks/<path>/
├── environment/assets/   inputs; the image build copies them, e.g. to /home/user/input/
├── tests/assets/         rubrics, expected values, reference and source documents the verifier reads
└── solution/assets/      reference deliverables solve.sh copies to the output

Every file under an assets/ root is stored with Git LFS (**/assets/** filter=lfs in .gitattributes), as ale assets push writes them.

Repository and access commands

This dataset belongs to AgentsLastExam/ale-tasks-chip. ALE finds it as <namespace>/<repository name> with the namespace ale-chips, so asset commands for that repository set ALE_ASSETS_NAMESPACE=ale-chips (in the engine checkout's .env, or per command):

cd /absolute/path/to/ale        # engine checkout; ALE_HF_TOKEN in its .env
ALE_ASSETS_NAMESPACE=ale-chips uv run ale assets push /absolute/path/to/ale-tasks-chip/tasks/<path>
ALE_ASSETS_NAMESPACE=ale-chips uv run ale assets pull /absolute/path/to/ale-tasks-chip

Versions

Each push makes one dataset commit per Task (Update tasks/<path> assets). A Task's material is identified by the git tree id of tasks/<path> on this dataset; with the tree id of the same folder in the repository it gives the Task's version, independent of every other Task. The run records of each version are in ale-chips/ale-tasks-chip-runs.

Access

Public and gated with manual approval: anyone can see the file list; downloading needs an administrator's approval, so tests, solutions and licensed material are never open to everyone.