key4hep / key4hep/TrackerPerformanceScripts

Cloning in the batch jobs?

未关闭
#5 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
2
派生
10
PR 合并指标
30 天内没有已合并 PR

描述

Do you want to keep the cloning in the batch jobs? Talking mostly about ILDConfig now, but these can become quite large and cloning can take quite a bit. If it's at all possible to lift the cloning to a "general setup step" that happens before the submission, etc. happens, I would recommend doing that. The obvious disadvantage is that it becomes user responsibility to make sure that things are consistent and that the config that was used for submission is reproducible.

Potentially something for another PR.

_Originally posted by @tmadlener in https://github.com/key4hep/k4DetPerformance/pull/3#discussion_r1623916895_

贡献指南

打开贡献指南

调研方向

首先追踪在提交批处理作业期间 ILDConfig 在哪里被克隆,以及常规设置步骤是如何组织的。明确克隆是否可以在提交之前进行,然后确定如何保持所提交配置的一致性和可复现性。克隆责任和配置流程得到明确解决即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
tooling
Issue 类型
重构
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
20/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。