jacob-valdez/synthux-economy-r4-w019
收藏资源简介:
SynthUX计算机使用数据集是一个基于视觉的计算机使用轨迹数据集,由SynthUX生成,专门针对经济模拟场景(r4版本)。每个数据记录代表一个工人在模拟公司内的设备会话:一个目标扩展为节点树,终端节点通过低级鼠标/键盘输入驱动真实的桌面模拟器应用(如终端、笔记、VS代码、浏览器、Slack/Teams、邮件、表格、幻灯片等),观察到的轨迹被记录为屏幕视频加上每个节点的帧。该数据集支持应用原生的多应用程序执行(无工作台覆盖)、每个参与者的内容多样性、跨操作系统消息传递,以及大型多公司经济模拟。每个经济模拟作为独立的数据集仓库发布。数据集内容包括:data.jsonl文件(每个渲染轨迹一条记录)、screenshots/<trajectory>/<node_id>.png(每个终端节点在最后输入事件时的帧图像)和videos/<trajectory>.webm(完整屏幕录制)。记录模式包括轨迹ID、参与者ID、公司、角色、环境、目标、节点树、轨迹事件、观察、对齐和媒体引用等字段。本版本统计信息:轨迹36条、视频36个、帧879个、公司6家,环境分布为浏览器操作系统(13条)、macOS网络下一个版本(15条)、Windows网络下一个版本(8条)。数据集由SynthUX生成,观察基于因果模拟(突变通道为低级输入),捕获过程中未使用高级应用突变。
The SynthUX Computer-Use Dataset is a grounded visual computer-use trajectories dataset generated by SynthUX, specifically for economy simulation scenarios (r4 version). Each record represents one workers device session inside a simulated company: a goal expands into a node tree, terminal nodes drive real desktop-simulator apps (such as Terminal, Notes, VS Code, Browser, Slack/Teams, Mail, Sheets, Slides, etc.) through low-level mouse/keyboard input, and the observed trajectory is recorded as a screen video plus per-node frames. It features app-native multi-application execution (without workbench overlay), per-actor content diversity, cross-OS messaging, and large multi-company economies. Each economy simulation is published as its own dataset repository. Contents include: data.jsonl (one record per rendered trajectory), screenshots/<trajectory>/<node_id>.png (a frame per terminal node, taken at that nodes last input event), and videos/<trajectory>.webm (the full screen recording). The record schema includes fields like trajectory_id, actor_id, company, role_id, title, env, goal, tree.nodes, trajectory.input_events, trajectory.observations, trajectory.alignment, media.video, and media.frames. Stats for this build: trajectories: 36, videos: 36, frames: 879, companies: 6, with environment distribution as browser-os (13), macos-web-next (15), windows-web-next (8). Provenance: generated with SynthUX, observations are causal (mutation channel = low_level_input), and no high-level app mutation is used during capture.




