jacob-valdez/synthux-economy-r5-w018
收藏资源简介:
SynthUX计算机使用数据集(经济模拟r5)是一个基于SynthUX生成的视觉计算机使用轨迹数据集,用于模拟公司环境中的员工设备会话。每个记录代表一个轨迹,其中目标扩展为节点树,终端节点通过底层鼠标和键盘输入驱动真实的桌面模拟器应用(如终端、笔记、VS Code、浏览器、Slack/Teams、邮件、表格、幻灯片等)。观察到的轨迹被记录为屏幕视频和每个节点的帧。数据集支持应用原生多应用程序执行(无工作台覆盖),具有每个参与者内容多样性、跨操作系统消息传递和大规模多公司经济模拟特性。每个经济模拟作为独立的数据集仓库发布。数据集包含data.jsonl(每个渲染轨迹的记录)、screenshots目录(每个终端节点的帧,以PNG格式存储)和videos目录(完整屏幕录制,以WebM格式存储)。记录模式包括轨迹ID、参与者ID、公司、角色、标题、环境(模拟器类型)、目标(自然语言会话目标)、节点树、输入事件、观察结果、对齐信息以及媒体文件(视频和帧)。统计信息显示:本版本包含36个轨迹、36个视频、920个帧、6家公司,环境分布为browser-os(6)、macos-web-next(9)和windows-web-next(21)。数据集由SynthUX生成,观察结果是因果性的(突变通道为底层输入),在捕获过程中未使用高级应用突变。
The SynthUX Computer-Use Dataset — economy sim r5 is a dataset of grounded visual computer-use trajectories generated by SynthUX. 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. The dataset 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 directory (a frame per terminal node stored as PNG), and videos directory (full screen recording in WebM format). The record schema includes fields like trajectory_id, actor_id, company, role_id, title, env (simulator type), goal (natural-language goal for the session), tree.nodes, trajectory.input_events, trajectory.observations, trajectory.alignment, and media files (video and frames). Statistics for this build show: 36 trajectories, 36 videos, 920 frames, 6 companies, with environment distribution as browser-os (6), macos-web-next (9), and windows-web-next (21). The dataset is generated with SynthUX, where observations are causal (mutation channel is low-level input), and no high-level app mutation is used during capture.




