Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Bug]: non-integer `Lbin_lo`/`Lbin_hi` are silently truncated under `Lbin_method = 1`, while method 3 raises a fatal error for the equivalent mistake

未關閉
#784 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@Rick-Methot-NOAA 已經在處理了。

開始於 2026年9月24日。

  • #785 來自 @iantaylor-NOAA —— 未關閉

評估

這個 Issue 還沒有評估資料。

描述

Describe the bug

Under Lbin_method = 1 the Lbin_lo/Lbin_hi columns of an age composition observation are population length bin indices. If a file instead contains lengths, SS3 accepts them silently and truncates them to integers, so conditional age-at-length data can be fit to the wrong bins. There is no warning in warning.sso and the run completes normally.

Method 3 searches len_bins for an exact match and calls write_message(FATAL, 0) with "L_bin_lo no match to poplenbins in age comp" if there is none. Method 1 has no equivalent check, only a clamp to [1, nlength].

Two consequences, depending on how the data is setup:

  • Lbin_lo and Lbin_hi one bin apart (e.g. 18.5 19.5, intended as the edges of one 1 cm bin) becomes index range 18..19, so the cell spans two population bins and consecutive rows overlap.
  • Lbin_hi = Lbin_lo (e.g. 34.5 34.5, a row on a 5 cm data bin grid) becomes bin 34, a single 1 cm bin one below the data's label.
To Reproduce

In any model with 1 cm population bins and Lbin_method = 1, write lengths rather than bin numbers in columns 7 and 8 of a conditional age-at-length row:

#_Lbin_method_for_Age_Data: 1=poplenbins; 2=datalenbins; 3=lengths
1
#_yr month fleet sex part ageerr Lbin_lo Lbin_hi Nsamp <data vector>
 1991   7     2    0    0     1     18.5    19.5      1  ...

Run, then compare the input against the FIT_AGE_COMPS section of Report.sso, which reports these columns converted back to actual length and so should read the same as the input:

data.ss                     1991 7 2 0 0 1  18.5 19.5  1 ...
Report.sso FIT_AGE_COMPS    ... 1991 1 2 7 1991.5 0 0 1  17.5 18.5  _ _ 1 ...

Tested on v3.30.25.1 and **v3.30.22.1 ** on the 2024 Aleutian Islands Pacific cod assessment: all 1160 CAAL redictions are one bin lower than the data. but the run exits 0, and warning.sso does not mention the Lbin truncation.

Expected behavior

A non-integer Lbin_lo or Lbin_hi under Lbin_method = 1 or 2 should produce a warning, or a fatal error, as method 3 already does for its own equivalent mistake. Anything that makes the run stop would allow users to catch this immediately.

Screenshots

No response

Which OS are you seeing the problem on?

No response

Which version of SS3 are you seeing the problem on?

v3.30.25.1 and **v3.30.22.1 **

Additional Context

Impacts all cod assessments in AK

主要語言
C++
星號
46
分支
20
平均合併
2 天 6 小時
30 天內合併 PR
1

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

nmfs-ost/ss3-source-code 的其他 Issue

查看 nmfs-ost/ss3-source-code 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。