Investigate regression: TTL output on channel 4 may no longer toggle during runtime
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- python
调研方向
首先，将最近与 stimulation、square 和 TTL 相关的提交与 stimulus.square.ttl_output 的有效运行时配置以及通道选择进行比较。检查 doric_light_source.py，尤其是 isTTLOutput、channelIdx 和 ttlModulation.* 字段，然后在可能的情况下使用最小 ch4 配置进行复现。完成标准是能够区分回归、配置不匹配或误报，并添加一个针对性的回归测试或验证步骤。
由索引模型根据 Issue 内容生成。
描述
Summary
As of 2026-04-15, there is a suspected regression where TTL output on channel 4 no longer behaves correctly during app-driven runs, despite the downstream electronics appearing healthy when tested directly through Doric.
Observed report:
- it was believed to be working on 2026-04-13
- it was not behaving correctly on 2026-04-14
- direct Doric-side testing on 2026-04-15 suggests the electronics path is fine
This points to either a recent software/config regression or a mismatch between intended runtime settings and what is actually being written to the device.
Why this matters
This is exactly the class of issue where we need better confidence that the app wrote the intended Doric settings, especially around TTL-related configuration.
Candidate investigation path
- compare recent commits touching stimulation / square / TTL-related code and config behavior
- verify the effective runtime config for
stimulus.square.ttl_outputand any relevant channel selection for the failing protocol - check whether channel indexing or channel-resolution behavior changed around
ch4 - inspect the exact
LightSourceSettingsfields written indoric_light_source.py, especiallyisTTLOutput,channelIdx, andttlModulation.* - compare known-good vs suspected-bad protocol overlays and session metadata
- reproduce with a minimal config targeting only
ch4if possible
Important context
Direct hardware/electronics verification through Doric appears fine, so this should be treated first as an app/runtime regression until disproven.
Follow-up data to attach later
- session metadata or CSV/TTL artifacts from a known-good run
- session metadata or CSV/TTL artifacts from a failing run
- exact overlay/config used in each case
- commit range between the last known-good and first known-bad behavior
Acceptance criteria
- identify whether this is a software regression, config mismatch, or false alarm
- if real, isolate the responsible change or code path
- add a focused regression test or validation step so channel-targeted TTL behavior does not silently drift again
- 主要语言
- Python
- 星标
- 0
- 派生
- 1
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
matiasandina/uid_python_api 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
bug
难度 3/5 1-2 天 新手友好度 55/100
-
file cleanup未关闭
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 35/100
matiasandina/uid_python_api#14 · 3 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
查看 matiasandina/uid_python_api 的全部 Issue
相似的 Issue
-
bug status/needs-triage
难度 2/5 1-3 小时 新手友好度 86/100
prowler-cloud/prowler#12887 · 1 条评论 ·
维护者通常 1 天内回复
-
area: desktop platform: macos priority: p3 status: ready type: enhancement
难度 1/5 1 小时以内 新手友好度 92/100
use-agent-os/agent-os#3484 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 86/100
open-telemetry/opentelemetry-python-contrib#5113 · 2 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
-
external
难度 2/5 1-3 小时 新手友好度 68/100
langchain-ai/docs#6255 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复