http://github.com/dylang/node-rsssite-lib/media/favicon.pngWebpage HTML Export plugin for ObsidianFri, 09 Oct 2026 09:35:26 GMTFri, 09 Oct 2026 09:35:26 GMT60P1 and R1 are internal numbers within this record, not the four-digit research record numbers of the Vault. Each proposition uses a fixed number, e.g. P1. New propositions continue the numbering; they are not renumbered when presentation order or page numbers change. P1 through P4 retain the meanings used in this round of discussion.Each record entry contains: Content: a statement that can be discussed independently. Nature: fact or observation, input condition, goal, route choice, or judgment to be verified. Discussion status: agreed, adopted wording, to be discussed, or not adopted. Basis: user confirmation, specific experience, literature, mathematical reasoning, or experimental record.
"Premise" and "conclusion" are the roles a proposition plays in a particular inference, not two permanently distinct types of node. A proposition can be the conclusion of R1 and also a premise of R2.
Each time premises are connected to a conclusion, a fixed number is used, e.g. R1. Each record entry contains: Natural-language argument: first write out the premises, connecting reasoning, and conclusion in full, marking the corresponding P numbers alongside the relevant sentences. The reader should not have to flip back to the proposition list to understand. Premises: which P numbers are referenced. Conclusion: which P number is supported. Mode: D, I, or A. Rationale: the specific connection between premises and conclusion. Scope and open items: how far this step can reach, and what is still missing. Symbolic shorthand comes after the natural-language argument; it is for tracking and referencing, not a substitute for explanation. P and R references use Obsidian section links, displaying the short number, with hover preview of the corresponding content; these links are not placed inside code blocks.Reasoning modes: D, deduction: under explicit conditions, the conclusion follows from the premises. Check whether the premises hold, and whether the inference is valid. I, induction: forming a more general judgment from multiple observations or experiments. Record the sample, comparison conditions, and scope of applicability. A, abduction: proposing a candidate explanation or plan with reasons. This record also uses A to mark scheme-level inferences made around research goals; it is not a proof of uniqueness or optimality. During discussion, use the shorthand:
R1: {P1, P4} —A→ P2
This means P1 and P4 support our choice of P2; it does not mean P2 necessarily holds. Only D expresses "under these premises, one can conclude"; A or I must not be rewritten as unconditional necessities.Input conditions that have not been made explicit should be listed separately. Do not hide them behind a single "assume this is so", and do not register hoped-for effects as facts.S1 is the narrative: what problem we are addressing, why it is worth doing, why we chose this route, and the trade-offs against alternative routes.S2 is the method: what relationships retargeting preserves, how the mathematical objectives and constraints are formulated, and how MPC generates robot motion.Internal argumentation may have multiple branches. The presentation selects one easy-to-follow path from them; it does not need to read out every P and R in order. First make the argument coherent, then decide on page breaks.We want to extend robot applications from workstations arranged for specific tasks to environments that people use in daily life; the robot needs to adapt to varying objects, layouts, and operating conditions.Nature: goal. Discussion status: agreed. Basis: user explicitly confirmed during this round of discussion.The contrast between an industrial workstation and a kitchen illustrates this extension; it does not imply that dedicated automation is obsolete, nor that all factories are free of variation.We want to leverage human demonstrations to help robots acquire manipulation skills, without having to specify the complete robot motion for each case.Nature: route choice. Discussion status: agreed. Basis: user explicitly confirmed, and pointed out that this step is abductive rather than deductive.
It is one route toward P1, not the only route P1 permits.If we want to convert a human's direct manipulation demonstration into robot execution under a different body and a different layout, we need to solve the conversion from human motion to robot motion.Nature: conditional task argument. Discussion status: to be discussed. Basis: the discussion in this round about "why not just collect data".Here we call this conversion retargeting. It does not require that all robot learning must use human-body retargeting, nor does it specify a particular loss function or solver.Humans already possess experience with the manipulation tasks we are interested in, such as approaching, grasping, carrying, and placing objects.Nature: fact and observation. Discussion status: adopted wording. Basis: everyday manipulation and demonstration scenarios raised by the user.It supports leveraging human experience; it does not directly prove that a particular demonstration collection method can improve robot learning performance.We choose to have the human demonstrate manipulation directly in their own workspace, while the robot executes the corresponding motion in real time in the target workspace, recording the robot-side observations, commands, and execution feedback.Nature: collection route and data objective. Discussion status: adopted wording; specific data fields to be clarified. Basis: user's description of the online system, source scene, target scene, and purpose of data collection.The human's action record and the robot's execution record should be described separately. Directly completing a teleoperation task and collecting data for subsequent learning are two uses of this route.The human on the source side and the robot on the target side have different body structures; the positions, orientations, and table layouts of objects on both sides can also differ.Nature: input condition. Discussion status: adopted wording. Basis: the human body and the NERO platform in this system, and the two-sided workspace examples in this round of discussion.These differences impose requirements on retargeting. The absolute trajectory from the source human cannot be directly used as the manipulation trajectory for the target robot.Human body and object observations describe states in the source scene, but do not directly specify the joint motions the target robot should execute.Nature: data semantics. Discussion status: adopted wording. Basis: different subjects and representations between human body observations and robot execution commands.For example, recording that the human reached out and grasped the source bottle does not mean we have obtained the command for how the robot should grasp the target bottle at a different location.We want the collection interface to be low-cost, to reduce equipment worn on the operator's body, and to be suitable for long-duration demonstrations; it should not require body markers, VR headsets, or continuously manipulating a leader arm.Nature: interface goal. Discussion status: agreed. Basis: device, cost, and ergonomic requirements raised by the user.Reducing wearable and hand-held equipment does not eliminate the burdens of camera placement, calibration, occlusion handling, computational resources, and maintenance.The user already has a leader arm and finds that operating it for extended periods is neither easy nor comfortable.Nature: specific usage experience. Discussion status: adopted wording. Basis: personal experience explicitly reported by the user in this round.
This explains one practical source of P8; it cannot be generalized to all leader systems or all operators' experiences.RT-COSMIK is a real-time, low-cost, markerless human motion estimation tool developed by CNRS colleagues, using RGB cameras and a human body model to obtain human motion.
Nature: fact, describing tool capability and origin. Discussion status: adopted wording. Basis: RT-COSMIK official page.It describes the available observation capability, not the accuracy or latency tests of a locally integrated version. Hand and object observations cannot all be attributed to COSMIK's contribution.We leverage the existing COSMIK human body observation capability to use the human's body movements as robot manipulation input.Nature: implementation choice. Discussion status: agreed. Basis: user-confirmed COSMIK plus MPC retargeting route.Low cost and no body markers are the reasons for this choice. The human body estimation contribution belongs to the CNRS colleagues; our research needs to explain how these observations become robot motion.For a robotic arm with redundant degrees of freedom, specifying only the wrist pose does not uniquely determine the configuration of the entire arm.Nature: geometric fact. Discussion status: adopted wording. Basis: the same wrist target can correspond to different elbow positions and joint configurations.It shows that body information can distinguish postures that end-effector targets do not distinguish; it does not prove that preserving this distinction necessarily improves manipulation.We want retargeting to consider body configuration and hand–object relationships simultaneously, rather than only passing the wrist pose to the robot.Nature: research goal. Discussion status: direction adopted; value argument to be completed. Basis: user's desire to leverage human body coordination, and the current discussion on body and manipulation relationships.It still needs to be clarified: is body configuration demonstration content we want the data to preserve, a means to improve object manipulation, or both? "Moving like a human" should not be directly taken as a sufficient justification.The body or hand–object relationships we wish to preserve may require the robot to exceed joint limits, motion constraints, or enter collision zones, and therefore cannot be exactly realized.Nature: conditional judgment. Discussion status: adopted wording. Basis: the robot's limited motion range and scene geometry.
This entry discusses the conflict between goals and execution constraints. The conflict between body configuration preservation and object manipulation goals is recorded separately in P23.We want the robot to operate in collaborative environments where other people are nearby, and to respect necessary safety boundaries.Nature: application requirement. Discussion status: agreed. Basis: collaborative environment requirements explicitly raised by the user in this round.This is a requirement, not a completed safety conclusion. Body similarity, using MPC, or configuring collision geometry cannot individually prove personnel safety.The robot needs to continuously respond to new observations while considering joint limits, motion constraints, and selected collision geometry.Nature: online execution requirement. Discussion status: adopted wording. Basis: user-confirmed online teleoperation mode and robot execution conditions.Online does not mean zero latency. The currently modeled robot and scene constraints also do not automatically cover moving people nearby.MPC can jointly optimize a segment of robot motion for objectives and constraints within a prediction horizon, and update upon receiving new observations.Nature: method capability. Discussion status: adopted wording. Basis: the predictive motion optimization approach used in this system.This capability still requires a specific motion model, objectives, constraints, and computational budget. Adopting MPC does not automatically yield a feasible solution, nor does it mean all contact decisions have been included in the optimization.We choose MPC to coordinate, online, the geometric relationships we wish to preserve with the robot's execution limits.Nature: method choice. Discussion status: agreed. Basis: user-confirmed current system route.This explains the method's purpose; it does not prove it is superior to per-frame optimization or learning-based control for all tasks, nor does it mean no loss function or weight design is needed.The current fixed-base dual-arm platform is the validation stage; the long-term direction includes whole-body retargeting. Whole-body MPC itself is also not the final application goal.Nature: research scope. Discussion status: agreed. Basis: user's explicit description of dual-arm, whole-body retargeting, and long-term robot applications.The presentation needs to separate current results from long-term directions; it must not describe existing dual-arm experiments as a complete whole-body manipulation capability.Camera-based teleoperation, human body following, interaction relationship preservation, and MPC retargeting all have existing prior work.
Nature: literature fact. Discussion status: adopted wording. Basis: AnyTeleop, H2O, OmniRetarget, X-OP.
Entry points to related literature are in Literature Index. When comparing online versus offline approaches, check human input, reference construction, and deployment execution separately. These citations establish precedent; they do not prove one method is superior to another on a shared task.We should compare methods around the same set of tasks and requirements, stating what our approach gains, what costs it incurs, and how far the evidence supports it.Nature: comparison principle. Discussion status: agreed. Basis: user's discussion about "why adopt our method" and the different design intents of various methods.Different methods may serve different goals, or may use different solutions for the same goal. The intent explicitly stated by the authors and the intent we infer should be recorded separately.The camera body interface is more suitable for long-duration demonstration collection than the leader interface being compared.
Nature: comparative judgment to be verified. Discussion status: to be verified; not treated as an established conclusion. Basis: the goal in P8 and the personal experience in P9.
The comparison devices, tasks, operators, and duration of use need to be specified. P9 alone is not a complete controlled comparison.The body configuration in a human demonstration serves the human's manipulation in the source scene. When the robot's body or target object layout differs, preserving the demonstrated body configuration may not allow the robot's hands to reach appropriate manipulation positions. To complete the corresponding object manipulation, the robot may need to change its body configuration. Therefore, preserving body configuration and completing object manipulation are two goals that may conflict with each other.
Nature: conditional judgment. Discussion status: agreed. Basis: user's description of body differences, scene differences, and manipulation goals, with explicit agreement to add P23.Body configuration here does not mean copying human joint angles one-to-one; even if what is preserved is a mapped body geometric relationship, it may still be inconsistent with the hand–object relationship required in the target scene. This conflict does not require joint limits or collision constraints to be active before it arises.
We want robots to perform manipulation in environments people use daily, adapting to varying objects, layouts, and operating conditions (P1). Humans already possess experience with these manipulations (P4). Therefore, we choose to leverage human demonstrations, using humans' existing experience to help robots acquire manipulation skills without specifying complete motions case by case (P2).
R1: {P1, P4} —A→ P2Status: agreed as a route choice. Scope: does not conclude that demonstration-based learning is the only approach, nor that our data has already improved downstream learning.
In our chosen collection route, the human directly manipulates objects in the source scene, the target robot executes corresponding motions in real time, and records its own observations, commands, and execution feedback (P5). However, the robot and the human have different bodies, and the object layouts on both sides can differ (P6); observing the human's motion does not yet provide the target robot's motion commands (P7). Therefore, to complete this collection route, we need to convert the human's manipulation into executable motion for the target robot. This conversion is what we call the retargeting task here (P3).
R2: {P5, P6, P7} —D→ P3Status: connection to be jointly reviewed. Scope: this is a conditional task definition, not a requirement for all data collection or robot learning. It does not conclude that COSMIK, MPC, or any particular loss function must be used.
We want demonstration collection to be low-cost, to reduce equipment on the operator, and to be suitable for extended use, without requiring body markers, VR, or continuously manipulating a leader arm (P8). The user has already encountered the problem of operating the existing leader being neither easy nor comfortable for extended periods (P9). COSMIK, developed by CNRS colleagues, provides existing low-cost, markerless human motion observation capability (P10). Therefore, we leverage this capability to form the body input interface, allowing the human's body movements to enter the robot retargeting system (P11).
R3: {P8, P9, P10} —A→ P11Status: choice agreed. Scope: reduced wearables and hand-held devices are interface characteristics; total cost, calibration effort, and long-duration comfort still need separate evaluation.
For a robotic arm with redundant degrees of freedom, even when the wrist reaches the same target pose, the entire arm can still have different configurations (P12). Transmitting only the wrist target does not express which body posture the demonstrator used. This gives us a reason to study the preservation of body relationships, and supports the research direction of "not only transmitting wrist targets" (P13). But this step only shows that there is body information that can be transmitted; which information is worth preserving, and what value it has for manipulation, still needs to be explained.
R4: {P12} —A→ P13
Status: reasoning not yet sufficient. What needs to be completed is why these distinctions are worth preserving: is it demonstration content, task necessity, or motion preference? P12 only proves there is information left unspecified; it cannot prove that more information is necessarily better.
We want the robot to consider both body configuration and hand–object relationships (P13). However, when the body and layout differ, preserving body configuration and completing object manipulation may require different motions (P23); these goals may also conflict with the robot's execution constraints (P14). The robot also needs to respect execution requirements in environments where other people are nearby (P15), and must continuously respond to new observations while considering joint limits, motion constraints, and selected collision geometry (P16). MPC can jointly optimize motion objectives and constraints within a prediction horizon, and update with new observations (P17). Therefore, we choose MPC: on one hand to coordinate trade-offs between different goals, and on the other to satisfy robot execution constraints (P18).
R5: {P13, P23, P14, P15, P16, P17} —A→ P18Status: method choice agreed; its relative advantages still need specific comparison. Scope: safety requirements support constraints and reliable execution, but do not prove MPC automatically guarantees personnel safety. MPC also has costs in online computation, modeling, loss design, and weight selection.
Camera-based teleoperation, human body following, interaction relationship preservation, and MPC retargeting all have existing related work (P20). Therefore, merely listing that we adopted these technologies does not yet explain why this combination suits our task. We choose to compare routes around concrete tasks and requirements, stating what our choices gain, what costs they incur, and what evidence supports the results (P21).
R6: {P20} —A→ P21Status: comparison approach agreed. Scope: a combination of requirements does not automatically constitute innovation; specific mathematical differences, experiments, or practical use value are still needed.
No I-type reasoning completed with controlled experiments from this system has been registered so far. P9 is a genuine usage experience that can support research motivation; it cannot yet derive the general comparative judgment in P22.When adding I-type reasoning in the future, state the source of the records or experiments, the comparison conditions, the observed results, and the scope the conclusion covers. Data not yet collected must not be filled in as premises.
Corresponds to P8 through P11, P22, and R3. Compare cameras, body markers, VR, and leader systems in terms of observation capability, equipment burden, cost, and usage conditions.
Corresponds to P3, P6, P7, P12 through P14, P23, and R2, R4. Discusses wrist targets, body configuration, bimanual relationships, hand–object relationships, and scene differences. This is about problem definition and mathematical objectives, not merely choosing an input device.
Corresponds to P14 through P18, P23, and R5. Compares how online optimization, predictive control, and learning-based tracking handle motion, constraints, training, and computational budgets. The retargeting task, MPC solve, controller tracking, and hardware execution are not the same concept.COSMIK mainly provides human body observation; retargeting defines what to transmit; MPC is the means for optimizing motion; the controller and hardware are responsible for actual execution. Relationship preservation objectives can enter MPC directly; it is not necessary to build a separate trajectory optimization layer externally for this purpose.
P2 to P5: leveraging demonstration-based learning does not necessarily require online teleoperation data collection. Why does this round choose real-time robot following, rather than only recording the human body or generating references offline? We need to compare the uses of robot-executed data and live guidance; this step cannot be skipped.
P13 and R4: what is the specific value of preserving body configuration? Find a real example of "wrist in position but body motion still unsuitable", distinguishing demonstration content from manipulation effect.
P3 and R2: further clarify the robot data being collected, and how the human demonstration enters execution. We cannot jump from general data needs to a particular interface.
P22 and R3: how to evaluate the operational burden of long-term use? First delimit the equipment and tasks, then discuss the comfort comparison.
P15 and R5: which safety requirements are already covered by models and mechanisms, and which are still only application requirements? People observation, robot collision avoidance, and body similarity should be treated separately.
P21 and R6: among the current tasks, which requirements are primary and which are acceptable costs? Use this to select related work and comparison conditions. S2: before freezing the method narrative, verify against the actual algorithm version. The PI wants to include more manipulation decisions in MPC—this is a development direction and should not substitute for the description of the current implementation.
The candidate main line for S1 is P1, P2, P5, P3, then connecting P11, P13, and P18. The interface, relationship preservation, and execution constraints are three branches of reasoning, not a chain of necessary conclusions. Each choice should state which requirement it addresses.
S2 expands P13 and P18: how to express relationships, how to handle conflicts, how to formulate the optimization problem, and how the solve and execution connect.The left-right comparison confirmed on the second page is preserved: an industrial workstation arranged around a fixed task versus a daily environment designed for people. Related work serves the argument, explaining alternative routes and trade-offs at the corresponding choice points; a detailed comparison table can serve as backup material and does not need to be explained row by row in the main presentation.Low equipment burden is a system usage value; which relationships to preserve across different bodies and scenes, and how to generate executable motion, is the research question. The two can be presented together but cannot substitute for each other's evidence.]]>telecosmik-narrative-arguments.htmlpresentations/en/telecosmik-narrative-arguments.mdFri, 09 Oct 2026 09:34:47 GMTP1、R1 是本记录内部编号，不是 Vault 的四位研究记录编号。每个命题使用一个固定编号，例如 P1。新增命题继续编号，不因讲述顺序或页码变化而重新编号。P1 至 P4 沿用本轮讨论中已经使用的含义。每项记录包含： 内容：一句能够独立讨论的表述。 性质：事实或观察、输入条件、目标、路线选择，或待检验的判断。 讨论状态：已同意、已采用的表述、待讨论，或不采用。 依据：用户确认、具体经历、文献、数学理由或实验记录。 “已同意”表示我们认可这个目标或表述，不表示已经用实验证明了效果。目标回答“希望达到什么”；事实回答“已经知道什么”；路线选择回答“决定怎样做”。三者不能互相替代。
“前提”和“结论”是命题在某次推理中的角色，不是两类永久不同的节点。一个命题可以是 R1 的结论，又是 R2 的前提。一个编号只保留一个当前表述。若只是澄清措辞，保留编号并记录修订；若改变了命题含义，新增编号，旧项标为被替代。删除一条主张时保留编号和删除理由，不把它分配给别的主张。
每次连接前提与结论，使用一个固定编号，例如 R1。每项记录包含： 自然语言论证：先把前提、连接理由和结论写完整，在对应句子旁标出 P 编号。读者不必回翻命题列表才能理解。 前提：引用哪些 P 编号。 结论：支持哪个 P 编号。 方式：D、I 或 A。 理由：前提与结论之间的具体连接。 范围与待解决项：这一步能说到哪里，还缺什么。 符号简写放在自然语言论证之后，用于追踪与引用，不代替解释。P、R 引用使用 Obsidian 章节链接，显示短编号，悬停可预览对应内容；这些链接不放在代码块中。
阅读视图可直接悬停。编辑视图按住 Ctrl，macOS 按住 Cmd，再悬停。需要启用 Obsidian 的页面预览插件，见官方说明。推理方式： D，演绎：在明确条件下，结论由前提推出。检查前提是否成立，以及推理是否有效。 I，归纳：从多个观察或实验形成较一般的判断。记录样本、比较条件和适用范围。 A，溯因：提出有理由的候选解释或方案。本记录也用 A 标记围绕研究目标所作的方案推断；它不是唯一性或最优性证明。 讨论时使用简写：
R1: {P1, P4} —A→ P2
它表示 P1、P4 支持我们选择 P2，不表示 P2 必然成立。只有 D 才表达“在这些前提下可以推出”；不能把 A 或 I 改写成无条件必然。没有说清楚的输入条件应单独列出。不要用一句“假设如此”藏起它，也不要把希望达到的效果登记为事实。S1 是叙事，说明我们要解决什么、为什么值得做、为什么选择这条路线，以及与其他路线的取舍。S2 是方法，说明重定向保留什么关系、怎样构造数学目标与约束，以及 MPC 怎样生成机器人运动。内部论证可以有多条分支。报告从中选一条容易跟随的路径，不需要逐项宣读所有 P 和 R。先把论证讲通，再决定分页。我们希望把机器人的应用，从为特定任务布置的工位，扩展到人日常使用的环境；机器人需要适应变化的物体、布局和操作条件。性质：目标。讨论状态：已同意。依据：用户在本轮讨论中明确确认。工业工位与厨房的对照用于说明这项扩展，不表示专用自动化已经过时，也不表示所有工厂都没有变化。我们希望利用人的示范，帮助机器人获得操作技能，而不必逐个指定完整的机器人动作。性质：路线选择。讨论状态：已同意。依据：用户明确确认，并指出这一步属于溯因而不是演绎。
它是一条达到 P1 的路线，不是 P1 唯一允许的路线。若要把人的直接操作示范转成不同身体、不同布局下的机器人执行，就需要解决人体运动到机器人运动的转换。性质：有条件的任务论点。讨论状态：待讨论。依据：本轮关于“为什么不只收集数据”的讨论。这里把这种转换称为重定向。它不要求所有机器人学习都必须采用人体重定向，也没有指定某一种损失或求解器。人已经具备我们关注的操作任务的经验，例如接近、抓取、搬运和放下物体。性质：事实与观察。讨论状态：已采用的表述。依据：用户提出的日常操作与示范场景。它支持利用人的经验，不直接证明某种示范采集方法能够提高机器人学习效果。我们选择让人在自己的工作区直接示范操作，由机器人在目标工作区实时执行对应运动，并记录机器人侧的观测、命令与执行反馈。性质：采集路线与数据目标。讨论状态：已采用的表述，具体数据字段待明确。依据：用户对在线系统、源场景、目标场景和数据采集目的的说明。人的动作记录与机器人的执行记录应分开描述。直接完成遥操作任务和为后续学习收集数据，是这条路线的两种用途。源端的人与目标端的机器人具有不同的身体结构；两边物体的位置、朝向和桌面布局也可以不同。性质：输入条件。讨论状态：已采用的表述。依据：本系统的人体与 NERO 平台，以及本轮讨论中的两侧工作区实例。这些差异给重定向提出要求。不能把源端人的绝对轨迹直接当作目标端机器人的操作轨迹。人体和物体观测描述了源场景中的状态，但没有直接指定目标机器人应该执行的关节运动。性质：数据语义。讨论状态：已采用的表述。依据：人体观测与机器人执行命令的不同对象和表示。例如，记录到人伸手抓住源瓶子，不等于已经获得机器人怎样抓住另一个位置的目标瓶子的命令。我们希望采集接口低成本、减少操作者身上的装备，并适合长时间示范；不要求贴身体标记、戴 VR 设备或持续操纵 leader arm。性质：接口目标。讨论状态：已同意。依据：用户提出的设备、成本和人体工学要求。减少穿戴与持握设备不等于消除了相机布置、标定、遮挡、算力和维护负担。用户已有 leader arm，并认为长时间操作它不够容易和舒适。性质：具体使用经历。讨论状态：已采用的表述。依据：用户在本轮明确报告的个人经历。
这解释了 P8 的一个实际来源，不能推广为所有 leader 系统或所有操作者的体验。RT-COSMIK 是 CNRS 同事开发的实时、低成本、无标记人体运动估计工具，利用 RGB 相机和人体模型获得人体运动。
性质：事实，描述工具能力与来源。讨论状态：已采用的表述。依据：RT-COSMIK 官方介绍。它说明可利用的观测能力，不是本机集成版本的精度或延迟测试。手部与物体观测不能全部归为 COSMIK 的贡献。我们利用已有 COSMIK 人体观测能力，把人的身体动作作为机器人操作输入。性质：实现选择。讨论状态：已同意。依据：用户确认的 COSMIK 加 MPC 重定向路线。低成本与无身体标记是这项选择的理由。人体估计贡献属于 CNRS 同事；我们的研究需要解释这些观测怎样成为机器人运动。对于具有冗余自由度的机械臂，仅指定手腕位姿并不能唯一决定整条手臂的构型。性质：几何事实。讨论状态：已采用的表述。依据：同一手腕目标可以对应不同的手肘位置与关节配置。它说明身体信息能够区分末端目标没有区分的姿态，不证明保留这种区别一定改善操作。我们希望重定向同时考虑身体构型与手–物体关系，而不只把手腕位姿传给机器人。性质：研究目标。讨论状态：方向已采用，价值论证待补全。依据：用户希望利用人体协调方式，以及当前身体与操作关系的讨论。仍需明确：身体构型是希望数据保留的示范内容，还是改善物体操作的手段，或两者兼有。不要把“动作像人”直接当作充分理由。希望保留的身体或手–物体关系，可能要求机器人超出关节范围、运动限制，或进入碰撞区域，因此不能精确实现。性质：条件性判断。讨论状态：已采用的表述。依据：有限的机器人运动范围和场景几何。
这一条讨论目标与执行约束之间的冲突。身体构型保持与物体操作目标之间的冲突，单独记录在 P23。我们希望机器人能够在有其他人在附近的协作环境中运行，并遵守必要的安全边界。性质：应用要求。讨论状态：已同意。依据：用户在本轮明确提出的协作环境要求。这是要求，不是已完成的安全结论。身体相似、采用 MPC 或配置碰撞几何，都不能单独证明人员安全。机器人需要持续响应新观测，同时考虑关节范围、运动限制和选定的碰撞几何。性质：在线执行要求。讨论状态：已采用的表述。依据：用户确认的在线遥操作模式与机器人执行条件。在线不等于零延迟。当前建模的机器人与场景约束，也不自动覆盖周围移动人员。MPC 可以在预测窗口内共同优化一段机器人运动的目标与约束，并在收到新观测后更新。性质：方法能力。讨论状态：已采用的表述。依据：本系统采用的预测运动优化方式。这种能力仍需要具体的运动模型、目标、约束和计算预算。采用 MPC 不等于自动获得可行解，也不等于所有接触决策已经进入优化。我们选择 MPC，在线协调希望保留的几何关系与机器人执行限制。性质：方法选择。讨论状态：已同意。依据：用户确认的当前系统路线。这解释方法的用途，不证明它对所有任务都优于逐帧优化或学习式控制，也不表示无需设计损失和权重。当前固定基座双臂平台是验证阶段；长期方向包含全身重定向。全身 MPC 本身也不是最终应用目标。性质：研究范围。讨论状态：已同意。依据：用户对双臂、全身重定向与长期机器人应用的明确说明。报告需要分开当前结果与长期方向，不能把已有双臂实验描述成完整的全身操作能力。相机遥操作、人体跟随、交互关系保持和 MPC 重定向都有已有工作。
性质：文献事实。讨论状态：已采用的表述。依据：AnyTeleop、H2O、OmniRetarget、X-OP。
相关文献入口见 文献索引。比较在线与离线时，分别检查人体输入、参考构建和部署执行。这些引用说明先例，不证明某个方法在共同任务上优于另一个。我们应围绕同一组任务与需求，说明采用这套方法能获得什么、付出什么代价，以及证据支持到哪里。性质：比较原则。讨论状态：已同意。依据：用户关于“为什么采用我们的方法”和不同方法设计意图的讨论。不同方法可能服务不同目标，也可能针对同一目标采用不同解法。作者明确提出的意图与我们推测的意图，应分开记录。相机身体接口比所比较的 leader 接口更适合长时间示范采集。
性质：待检验的比较判断。讨论状态：待验证，不作为已得到的结论。依据：P8 的目标与 P9 的个人经历。
需要明确比较设备、任务、操作者和使用时长。P9 本身不是完整的对照。人体示范中的身体构型，服务于人在源场景中的操作。当机器人身体或目标物体布局不同时，保留示范的身体构型，未必能让机器人的手到达合适的操作位置。为了完成对应的物体操作，机器人可能需要改变身体构型。因此，保持身体构型与完成物体操作，是可能相互冲突的两个目标。
性质：条件性判断。讨论状态：已同意。依据：用户对身体差异、场景差异与操作目标的说明，并明确同意新增 P23。这里的身体构型不等于逐关节复制人体角度；即使保持的是经过映射的身体几何关系，也可能与目标场景所需的手–物体关系不一致。这个冲突不必等到关节限位或碰撞约束起作用才出现。
我们希望机器人能在人日常使用的环境中完成操作，适应变化的物体、布局和操作条件（P1）。人已经具备这些操作的经验（P4）。因此，我们选择利用人的示范，把人的已有经验用于帮助机器人获得操作技能，而不必逐个指定完整动作（P2）。
R1: {P1, P4} —A→ P2状态：已同意其作为路线选择。范围：不推出示范学习是唯一方案，也不推出我们的数据已经改善下游学习。
在我们选择的采集路线中，人直接操作源场景中的物体，目标机器人实时执行对应运动，并记录自己的观测、命令与执行反馈（P5）。但机器人与人的身体不同，两侧物体的布局也可以不同（P6）；观测到人的动作，还没有给出目标机器人的运动命令（P7）。因此，要完成这条采集路线，就需要把人的操作转换成目标机器人可执行的运动。这项转换就是这里所说的重定向任务（P3）。
R2: {P5, P6, P7} —D→ P3状态：连接待共同审阅。范围：这里是有条件的任务定义，不是对所有数据采集或机器人学习的要求。它不推出必须采用 COSMIK、MPC 或某种特定损失。
我们希望示范采集低成本、减少操作者身上的装备，并适合长时间使用，不要求贴身体标记、戴 VR 或持续操纵 leader arm（P8）。用户已经遇到长时间操作现有 leader 不够容易和舒适的问题（P9）。CNRS 同事开发的 COSMIK 提供已有的低成本、无标记人体运动观测能力（P10）。因此，我们利用这项能力构成身体输入接口，让人的身体动作进入机器人重定向系统（P11）。
R3: {P8, P9, P10} —A→ P11状态：选择已同意。范围：少穿戴和少持握是接口特点；总成本、标定工作量与长时间舒适性仍需各自评价。
对于有冗余自由度的机械臂，手腕达到同一个目标位姿时，整条手臂仍可以有不同的构型（P12）。只传递手腕目标，没有表达示范者使用了哪一种身体姿态。这给我们研究身体关系的保持提供了一个理由，也支持“不只传递手腕目标”的研究方向（P13）。但这一步只说明还有可以传递的身体信息；哪些信息值得保留，以及它们对操作有什么价值，仍需要说明。
R4: {P12} —A→ P13
状态：理由尚不充分。需要补全的是这些区别为什么值得保留：是示范内容、任务需要，还是动作偏好。P12 只证明还有未被指定的信息，不能证明信息越多就一定越好。
我们希望机器人同时考虑身体构型与手–物体关系（P13）。但身体和布局不同后，保持身体构型与完成物体操作可能要求不同的动作（P23）；这些目标也可能与机器人的执行约束冲突（P14）。机器人还需要在有其他人在附近的环境中遵守执行要求（P15），并持续响应新观测，考虑关节范围、运动限制和选定的碰撞几何（P16）。MPC 可以在一个预测窗口内共同优化运动目标与约束，再根据新观测更新（P17）。因此，我们选择 MPC，一方面协调不同目标之间的取舍，另一方面满足机器人执行约束（P18）。
R5: {P13, P23, P14, P15, P16, P17} —A→ P18状态：方法选择已同意，其相对优势还需具体比较。范围：安全要求支持约束与可靠执行，不证明 MPC 自动保证人员安全。MPC 也有在线计算、模型、损失设计与权重选择的代价。
相机遥操作、人体跟随、交互关系保持和 MPC 重定向都已有相关工作（P20）。所以，仅列出我们采用了这些技术，还没有解释这套方法为什么适合我们的任务。我们选择围绕具体任务与需求比较各路线，说明自己的选择获得了什么、付出了什么代价，以及效果由什么证据支持（P21）。
R6: {P20} —A→ P21状态：比较方式已同意。范围：需求组合本身也不自动成为创新；仍需具体数学差异、实验或实际使用价值。
目前没有登记一条用本轮系统对照实验完成的 I 推理。P9 是真实使用经历，可支持研究动机；它还不能推出 P22 的普遍比较判断。以后新增 I 推理时，写明记录或实验的出处、比较条件、观察结果，以及结论覆盖的范围。不能将尚未采集的数据填成前提。
对应 P8 至 P11、P22 与 R3。比较相机、身体标记、VR 和 leader 的观测能力、装备负担、成本及使用条件。
对应 P3、P6、P7、P12 至 P14、P23，以及 R2、R4。讨论手腕目标、身体构型、双臂关系、手–物体关系和场景差异。这里是问题定义与数学目标，不只是选择输入设备。
对应 P14 至 P18、P23 与 R5。比较在线优化、预测控制与学习式追踪如何处理运动、约束、训练和计算预算。重定向任务、MPC 求解、控制器跟踪和硬件执行不是同一个概念。COSMIK 主要提供人体观测；重定向定义要传递什么；MPC 是优化运动的手段；控制器与硬件负责实际执行。关系保持目标可以直接进入 MPC，不必因此在外部另做一套轨迹优化。
P2 到 P5：利用示范学习，并不必然要求在线遥操作采集。为什么本次选择机器人实时跟随，而不是仅记录人体或离线生成参考？需要比较机器人实际执行数据与现场指导的用途，不能跳过这一步。
P13 与 R4：保留身体构型的具体价值是什么？找一个“手腕到位但身体动作仍不合适”的真实例子，区分示范内容与操作效果。
P3 与 R2：进一步明确所采集的机器人数据，以及人的示范如何进入执行。不能从一般的数据需求跳到某个接口。
P22 与 R3：如何评价长期使用的操作负担？先限定设备与任务，再讨论舒适性比较。
P15 与 R5：哪些安全要求已有模型与机制覆盖，哪些还只是应用要求？人员观察、机器人避碰和身体相似应分开。
P21 与 R6：在当前任务中，哪些需求是主要的，哪些是可以接受的代价？据此选择相关工作和比较条件。 S2：冻结方法讲述前核对实际算法版本。PI 希望把更多操作决策纳入 MPC，这是发展方向，不应替代当前实现的说明。
S1 的候选主线是 P1、P2、P5、P3，再连接 P11、P13 与 P18。接口、关系保持与执行约束是三条理由分支，不是一串必然结论。每个选择都应说明它回应了哪项需求。
S2 展开 P13 与 P18：怎样表达关系、怎样处理冲突、怎样构造优化问题，以及求解与执行怎样衔接。第二页已经确认的左右对照保留：工业工位围绕固定任务布置，日常环境为人使用。相关工作服务论证，在相应选择处说明替代路线与取舍；详细比较表可以作为备用材料，不要求在主讲中逐行解释。低设备负担是系统使用价值；跨身体和场景时保留哪些关系、怎样生成可执行运动，是研究问题。二者可以共同讲述，但不能互相代替证据。
2026-10-09：保留原 P1 至 P4；登记讨论中的支持命题与研究选择，补充 R1 至 R6；把舒适性比较、身体关系价值、人员安全与方法优势列为需要继续讨论或验证的项目。
2026-10-09：R1 至 R6 改为先写完整的自然语言论证，在句子旁标出对应 P 编号，再列符号简写。编号、推理类型与讨论状态保持不变。
2026-10-09：新增 P23，将身体构型与操作目标的冲突同 P14 的目标与执行约束冲突分开，并更新 R5。文档迁入 Vault，P/R 引用改为可预览的 Obsidian 章节链接。 ]]>telecosmik-narrative-arguments.htmlpresentations/telecosmik-narrative-arguments.mdFri, 09 Oct 2026 08:35:38 GMT