jinko-task-debug-solving-errors
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDebug solving errors
调试求解错误
Find the failure mechanism and validate a repair against the original scenarios.
Use for model edits and for trial mechanics. Preserve
source revisions and perform experiments on copies within the authorized scope.
jinko-modeljinko-trialPREREQUISITE: This skill needs an initializedconnection and an SDK satisfying itsjinko-sdkrange. Run themetadata.requires_sdkskill (jinko-sdk-setup) and proceed only once its check passes. Use../jinko-sdk-setup/SKILL.mdwhen it is set. Otherwise, obtain a fresh session code before this skill's SDK process, as instructed by the setup skill. Also check thatJINKO_API_KEYworks. If the command is missing, upgradepython -m jinko.cli.debug_solving --help. Do not replace the command with private transport calls.jinko-sdk
查找故障机制,并针对原始场景验证修复方案。
使用 修改模型,使用 处理 trial 机制。保留
源修订版本,并仅在授权范围内对副本进行实验。
jinko-modeljinko-trial前置条件: 此 skill 需要已初始化的连接,以及满足jinko-sdk版本范围的 SDK。运行metadata.requires_sdkskill(jinko-sdk-setup),仅在其检查通过后继续。 如果已设置../jinko-sdk-setup/SKILL.md,则使用该变量。否则,按照 setup skill 的说明, 在此 skill 的 SDK 进程启动前获取新的会话代码。 此外,检查JINKO_API_KEY是否可以正常运行。如果 缺少该命令,请升级python -m jinko.cli.debug_solving --help。不要使用私有传输调用来替代该命令。jinko-sdk
Collect before changing
更改前收集证据
Run the deterministic diagnostic command into a new directory. It does not edit
items or start trials. A model solve requires explicitly.
--run-simple-solvebash
python -m jinko.cli.debug_solving --model-sid cm-... --out debug/model
python -m jinko.cli.debug_solving --trial-sid tr-... --revision 2 \
--telemetry --out debug/trialFor one authorized model probe, select representative outputs and preserve exact
formula overrides in a JSON object. The command uses at most ten output slots.
Available telemetry fills remaining slots; absent metrics are reported as such.
bash
python -m jinko.cli.debug_solving --model-sid cm-... --revision 4 \
--run-simple-solve --timeseries-id Time --timeseries-id Drug \
--overrides-json case.json --telemetry --out debug/probeUse to retain an exact patient row from the bound population;
this reads the population. The bundle also records the bound protocol and trial
options. Reconstruct the scenario from all three. Do not assume the model head,
its default settings, or a bare patient row represents the failed trial arm.
limits telemetry downloads, not the original failure inventory.
--patient-id--arm-idRead and collection errors before interpreting the bundle. Exit
codes are 0 for successful collection without detected failure, 1 for a reported
model/solve/patient failure, and 2 for incomplete collection or invalid input.
Neither exit 0 nor finite outputs establish numerical or scientific validity.
report.json在新的目录中运行确定性诊断命令。它不会编辑条目或启动 trial。模型求解必须
显式指定 。
--run-simple-solvebash
python -m jinko.cli.debug_solving --model-sid cm-... --out debug/model
python -m jinko.cli.debug_solving --trial-sid tr-... --revision 2 \
--telemetry --out debug/trial对于一次获得授权的模型探测,请选择有代表性的输出,并将精确的公式覆盖项保存在
一个 JSON 对象中。该命令最多使用十个输出槽位。可用的遥测数据会填充剩余槽位;
缺失的指标也会如实报告。
bash
python -m jinko.cli.debug_solving --model-sid cm-... --revision 4 \
--run-simple-solve --timeseries-id Time --timeseries-id Drug \
--overrides-json case.json --telemetry --out debug/probe使用 保留绑定群体中的确切患者行;这会读取该群体。该数据包还会记录
绑定的 protocol 和 trial 选项。请结合这三部分重建场景。不要假定模型头、
其默认设置或单独的患者行能够代表发生失败的 trial 臂。
仅限制遥测数据的下载范围,不会限制原始失败清单。
--patient-id--arm-id解读数据包前,请先读取 和收集错误。退出码 0 表示收集成功且未检测到
失败,1 表示报告了模型、求解或患者失败,2 表示收集不完整或输入无效。
无论是退出码 0 还是有限值输出,都不能证明数值或科学有效性。
report.jsonChoose the investigation
选择调查方向
- Slow or timed out: separate client wall time, solver time, compilation, and incomplete evidence. Treat at least 15 seconds as a configurable signal. Inspect the solver, tolerances, state scales, maximum step, and auxiliary events before choosing a bounded experiment.
- Patient/arm subset: group raw errors by patient and arm, compare exact inputs with a successful control, and retain the full failure set. Shared derivative names can conceal different upstream causes.
- Non-finite derivative: trace upstream expressions, including division, logarithms, roots, fractional powers, and switched branches. The reported derivative is not necessarily the first invalid expression. The reported last solved time may be an earlier output point.
- Setup or export error: inspect trial-context sanity, formulaic descriptor overrides, unit mode, and event schedule. Keep unit/conversion defects separate from runtime defects. For failed exports, preserve the error and use native JSON plus options when supported.
Read investigation guidance for telemetry meaning,
controlled solver experiments, and independent replication after a full timeout.
- 缓慢或超时: 区分客户端墙钟时间、求解器时间、编译时间和不完整证据。将至少 15 秒视为可配置的信号。 在选择有边界的实验之前,检查求解器、容差、状态量尺度、最大步长和辅助事件。
- 患者或试验臂子集: 按患者和试验臂对原始错误分组,将确切输入与成功的对照进行比较,并保留完整的失败集合。共享的导数名称可能会掩盖不同的上游原因。
- 非有限导数: 向上追踪相关表达式,包括除法、对数、根、分数次幂和切换分支。报告的导数不一定是第一个无效表达式。报告的最后求解时间可能是更早的输出点。
- 设置或导出错误: 检查 trial 上下文是否合理、公式化描述符覆盖项、单位模式和事件日程。将单位或转换缺陷与运行时缺陷区分开来。对于导出失败,请保留错误,并在支持的情况下使用原生 JSON 及选项。
有关遥测数据的含义、受控求解器实验,以及完整超时后的独立复现,请阅读
调查指南。
Verify and report
验证并报告
Change one cause at a time. Compare the original failing case, a successful
control, and then all original subjects and arms. Check finite trajectories,
physiological constraints, event behavior, and numerical sensitivity. Halve the
maximum step or tighten tolerances for a justified comparison; do not call an
unconverged candidate validated merely because every subject completes.
Report evidence, hypotheses, copy-level changes, remaining failures, and open
scientific questions separately. Record pins, settings, override warnings,
metrics, and comparison tolerances. Never silently drop failing patients, loosen
accuracy to obtain completion, or apply a model-specific clamp to other models.
每次只更改一个原因。将原始失败案例与成功对照进行比较,然后再检查所有原始研究对象和试验臂。检查轨迹是否有限、生理约束、事件行为和数值敏感性。为了进行有依据的比较,可以将最大步长减半或收紧容差;不要仅仅因为所有研究对象都能完成,就将尚未收敛的候选方案判定为已验证。
分别报告证据、假设、副本层面的更改、剩余失败和尚未解决的科学问题。记录版本锁定信息、设置、覆盖警告、指标和比较容差。绝不要静默丢弃失败患者、放宽精度要求以换取运行完成,或将针对特定模型的钳制处理应用到其他模型上。