Feature request: Coverage in DifferentiationInterfaceTest

未关闭
#1,024 9 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
julia
领域
testing

调研方向

首先阅读 DifferentiationInterfaceTest (DIT) 的场景,以及 issue 中描述的现有 CI、文档和基准测试入口点。确定是否可以在受支持的 AD 后端之间一致地定义覆盖率,以及它将如何与共享场景连接。完成的标准是:有一个已记录且可工作的覆盖率工作流,或有一份清楚论证其不可行原因的说明。

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

描述

documentation

To preface, this may be impossible and I really like DIT as it stands.

Ask

I would like to be able to use DifferentiaionInterfaceTest as my unit testing interface, benchmarking tool, and code coverage generator when creating packages meant to work well with AD (both a specific AD package and for multiple as far as I am aware, none of them has good tools for this). Related package level issue: https://github.com/EpiAware/CensoredDistributions.jl/issues/272

The missing part of this is having an understanding of what is being covered by my DIT scenarios which it seems code coverage is designed for.

The reason I want this is we are moving towards making a larger Julia ecosystem of packages and we really want them on a firm base/with some good practices established before hand.

What we are doing at the moment:

We currently run DIT in our CI per benchmark, in our docs (https://censoreddistributions.epiaware.org/stable/getting-started/tutorials/ad-backends) and in our benchmarking suite from a shared set of scenarios. Early days but very happy with DIT as it stands. The only additional nice to have would be a shared way to test rules but that seems like the real wild west so I imagine is out of scope.

Solution

I don't know. I don't know anything about how the AD version of the code interacts with the original version or if there is enough commonality between backends to make this a thing that is plausible to do across backends.

主要语言
Julia
星标
317
派生
38
平均合并
7 小时 36 分钟
30 天内合并 PR
4

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

JuliaDiff/DifferentiationInterface.jl 的其他 Issue

查看 JuliaDiff/DifferentiationInterface.jl 的全部 Issue

相似的 Issue

更多 Julia Issue

把新 issue 发到你的邮箱

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