The temperature correction inflates the signal-to-noise ratio of the LEDs: the noise is not divided by the reduction factor
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 ExtinctionCoefficients.apply_temperature_correction 开始,追踪它如何更新参考强度和噪声列;然后检查 calc_and_set_coefficients 和 calc_and_set_coefficients_mp,了解 SNR 是如何形成的。添加一个测试,使用相同的提取数据分别进行温度校正和不进行温度校正,并确认传递给 calc_coefficients_of_img 的 SNR 保持不变。
由索引模型根据 Issue 内容生成。
描述
ExtinctionCoefficients.apply_temperature_correction divides the reference property by the reduction factor of every value, but leaves its noise column as it was extracted:
corrected_intensities = self.calculated_img_data[self.reference_property] / factors
self.calculated_img_data = self.calculated_img_data.assign(
**{self.reference_property: corrected_intensities})
The signal-to-noise ratio that weights the LEDs in the linear solver is then formed from the corrected intensity and the uncorrected noise (calc_and_set_coefficients and calc_and_set_coefficients_mp):
snr = single_img_array / single_img_data[self.noise_property].to_numpy()
So with a temperature correction every SNR comes out too high by 1/factor. The correction rescales the signal, it does not add any: the SNR of a measured value is I/σ before and after it. The weight min(1, SNR / snr_full_weight) is meant to be the inverse standard deviation of the optical depth -ln(I_e/I_0), and the correction does not change that either.
Effect
Only LEDs below snr_full_weight are affected, because the weight is capped at 1. With a reduction factor of 0.8 and the default snr_full_weight = 10:
| true SNR | weight now | correct weight |
|---|---|---|
| 8 | 1.0 | 0.8 |
| 4 | 0.5 | 0.4 |
| 1 | 0.125 | 0.1 |
The min_layer_weight cut-off is computed from the same weights, so layers are set to NaN later than they should be. The error grows with the reduction, i.e. with the LED temperature, which is highest where the smoke is densest and the LEDs approach the noise floor, so it hits exactly the LEDs the weighting exists for.
Runs without a temperature correction, and runs of a reference property without a noise column, are not affected.
Fix
Divide noise_sum_col_val by the same factors in apply_temperature_correction whenever self.noise_property is loaded. The moving average runs before the correction for both columns, so they stay consistent.
A test: for the same extracted data, the SNR passed to calc_coefficients_of_img should be the same with and without a temperature correction.
- 主要语言
- Python
- 星标
- 7
- 派生
- 4
- 平均合并
- 3 小时 58 分钟
- 30 天内合并 PR
- 35
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
FireDynamics/LEDSmokeAnalysis 的其他 Issue
-
-s3_fast with -r, -g or -b also runs the full step 3 with LED fits可能已有人在做 @imshah-id 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
FireDynamics/LEDSmokeAnalysis#176 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 55/100
FireDynamics/LEDSmokeAnalysis#177 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 15/100
FireDynamics/LEDSmokeAnalysis#98 ·
维护者通常 1 天内回复
-
enhancement
难度 3/5 1-2 天 新手友好度 25/100
FireDynamics/LEDSmokeAnalysis#91 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 25/100
FireDynamics/LEDSmokeAnalysis#90 ·
维护者通常 1 天内回复
查看 FireDynamics/LEDSmokeAnalysis 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
-
[Bug]: Responses API 500s on assistant message with empty content list可能已有人在做 @shadowmodder 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 66/100
vllm-project/vllm#64940 ·
维护者通常 1 天内回复
-
limits
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
agent-ready area: docs documentation good first issue
难度 2/5 1-3 小时 新手友好度 78/100
Soneso/stellar-agent-wallet#524 ·
维护者通常 1 天内回复
-
Status: Triage Type: Quest
难度 2/5 1-3 小时 新手友好度 66/100
GTNewHorizons/GT-New-Horizons-Modpack#27490 ·
维护者通常 1 天内回复