Spaces:
Running
Leaderboard boards show no new rows since Oct 20 09:49 KST (hERG submission 44EC5F0856EA941A accepted Oct 26 00:03, no result yet), possibly the same rollup issue as ODC #10?
Hello, this is 1Dmeds. This is a status question, not a complaint about any score.
What we observed (public API, re-checked 2026-10-27 10:52 KST and again 2026-10-29 14:05 KST, unchanged)
- Across the 46 boards, the latest
scored_atis 2026-10-20 09:49:47 KST. No row on any board has a later value. /api/healthreturnsok: true,boards: 46,scoring_here: false.- The hERG board's
updatedfield is 2026-10-26 00:03:00 KST, which matches the time of our submission, but no new hERG row appeared. - Our one submission: board hERG, submission ID 44EC5F0856EA941A, accepted (HTTP 200,
remaining_today: 4) on 2026-10-26 00:03 KST. - Per-board responses are small (about 2 KB each,
/api/leadersabout 24 KB), so we cannot tell from the public side whether any file has reached a size limit.
What we don't know
- Whether scoring is running and only the public rows are not updating, as described in the ODC discussion #10 (the rollup file exceeded 10 MB and was fixed on Oct 27 01:26). We are only noting that the symptom looks similar.
- Whether the repository or storage quota that blocked that write also affects this Space. This is only a guess.
- Per the rules, a new score may be hidden when it does not beat the previous best by the noise floor, so a missing row can also be expected. We cannot distinguish the two cases from outside.
Request
Could you tell us whether our submission 44EC5F0856EA941A has been scored, and whether the public rows for this Space are being updated? No re-scoring or action on any score is requested.
Thank you.
์๋ ํ์ธ์, 1Dmeds ์ ๋๋ค. ์ ์ ํญ์๊ฐ ์๋๋ผ ์ํ ํ์ธ ๋ฌธ์์ ๋๋ค.
- 46๋ถ๋ฌธ ์ ์ฒด์์ ๊ฐ์ฅ ๋ฆ์
scored_at์ด 2026-10-20 09:49:47 KST ์ด๊ณ ๊ทธ ๋ค ํ์ด ์์ต๋๋ค. - hERG ์ ์ถ๋ฒํธ 44EC5F0856EA941A ๋ 2026-10-26 00:03 KST ์ ์ ์(HTTP 200)๋์ผ๋ ๊ฒฐ๊ณผ ํ์ด ์์ง ์์ต๋๋ค.
- ODC ํ ๋ก #10 ์ ์์ํ ํ์ผ ์ฉ๋ ๋ฌธ์ ์ ์ฆ์์ด ๋น์ทํ์ง, ์ ์๊ฐ ์จ๊ฒจ์ง ๊ฒ(์ก์ ๋ฐ๋ฅ ๊ท์น)์ธ์ง ๋ฐ๊นฅ์์๋ ๊ตฌ๋ณํ ์ ์์ต๋๋ค.
์ด ์ ์ถ์ด ์ฑ์ ๋๋์ง, ์ด Space ์ ๊ณต๊ฐ ํ์ด ๊ฐฑ์ ๋๊ณ ์๋์ง๋ง ์๋ ค ์ฃผ์๋ฉด ๋ฉ๋๋ค.
์ฑ์ ๋์ต๋๋ค. ์ ์ง๊ฐ ์๋๋ผ ๋ณด๋ฅ์ ๋๋ค. ๊ทธ๋ฆฌ๊ณ ๊ตฌ๋ณํ๋ ์นธ์ด ์ด๋ ๊ฒ์ธ์ง ์๋ ค๋๋ฆฝ๋๋ค.
1. ์ ์ถ 44EC5F0856EA941A ๋ ์ ์ 3๋ถ ๋ค ์ฑ์ ๋์ต๋๋ค
| ๋จ๊ณ | ์๊ฐ (KST) |
|---|---|
| ์ ์ | 2026-10-26 00:00:15 |
| ์ฑ์ | 2026-10-26 00:02:58 |
| ์์ํ ๊ฐฑ์ | 2026-10-26 00:02:59 |
๊ฒฐ๊ณผ: ์ฃผ์งํ MAE 0.65055, ์ฑ์ 1,338๊ฑด, ๋๋ฝ 0๊ฑด, ๋์ถ ๊ฒ์ฌ clean.
2. ์ ํ์ด ์๋ ์ด์
hERG ์์ ๊ณต๊ฐ๋ ๊ทํ์ ์ต๊ณ ๊ฐ์ 0.5888 ์ ๋๋ค. ์ด ๋ณด๋๋ ๋ฎ์์๋ก ์ข์ต๋๋ค. ์ ์ ์ 0.65055 ๋ ๊ทธ๋ณด๋ค ๋์๋ฏ๋ก ํ์ด ๊ต์ฒด๋์ง ์์์ต๋๋ค.
๊ธฐ๋ก์ ๊ทธ๋๋ก ๋จ์ ์์ต๋๋ค.
"ladder": {"revealed": 0.5888, "state": "held", "best": 0.5888,
"note": "์ง์ ์ต๊ณ 0.5888 ๋ฅผ 0.0145 ์ด์์ผ๋ก ๋์ง ๋ชปํ๋ค (๊ณต๊ฐ ๋ฌธํฑ)"}
"reveal_step": 0.014546555350190326
์ฆ ๋ง์ํ์ ๋ ๊ฒฝ์ฐ ์ค ํ์์ ๋๋ค.
3. ์์กด ์ฌ๋ถ๋ฅผ ๋ณด๋ ์นธ์ ํ์ scored_at ์ด ์๋๋ผ ๋ณด๋์ updated ์
๋๋ค
์ด๋ฏธ ๋ณด์
จ์ต๋๋ค. hERG ์ updated ๊ฐ ๊ทํ ์ ์ถ ์๊ฐ์ผ๋ก ์์ง์๋ค๊ณ ์ ์ผ์
จ๊ณ , ๊ทธ๊ฒ์ด ์ ํํ ๊ด์ธก์
๋๋ค.
| ์นธ | ์ธ์ ์์ง์ด๋ |
|---|---|
๋ณด๋ updated |
์ง๊ณ๊ฐ ๋ ๋๋ง๋ค. ํ์ด ๋ฐ๋์ง ์์๋ ์์ง์ ๋๋ค |
ํ scored_at |
ํ์ด ๊ณต๊ฐ๋ ๋๋ง. ๋ณด๋ฅ๋๋ฉด ์์ง์ด์ง ์์ต๋๋ค |
46๋ถ๋ฌธ ์ ์ฒด์์ ๊ฐ์ฅ ๋ฆ์ ํ scored_at ์ด 10์ 20์ผ์ธ ๊ฒ์, ๊ทธ๋๊ฐ ๋ง์ง๋ง์ผ๋ก ์ด๋ค ํ์ด ์ค์ ๋ก ๊ณต๊ฐ๋ ์์ ์ด๊ธฐ ๋๋ฌธ์
๋๋ค. ์ฑ์ ์ด ๋ง์ง๋ง์ผ๋ก ๋ ์์ ์ด ์๋๋๋ค.
4. scoring_here: false
์ด Space ๋ ์ฑ์ ํ์ง ์์ต๋๋ค. ์ฑ์ ์ ๋ณ๋ ๊ธฐ๊ณ์์ ๋๋๋ค. ๊ณ ์ฅ ์ ํธ๊ฐ ์๋๋ผ ๊ตฌ์กฐ ํ๊ธฐ์ ๋๋ค.
5. ๋ฏธ์ฑ์ ๊ฑด์๋ 0์ ๋๋ค
๊ทํ ์ ์ถ์ด 46๋ถ๋ฌธ ์ ์ฒด์์ ๊ฐ์ฅ ์ต๊ทผ ๊ฑด์ด์๊ณ , ๊ทธ ๋ค๋ก ๋ค์ด์จ ์ ์ถ์ด ์์ต๋๋ค.
6. ์ง์ ํ์ ์ ์ ๋ง์ต๋๋ค
updated ๋ฅผ ์ฝ์ด์ผ ํ๋ค๋ ๊ฒ์ ๋ชจ๋ฅด๋ฉด ๋ฐ๊นฅ์์ ๋ณด๋ฅ์ ์ ์ง๋ ๊ฐ์ ๋ณด์
๋๋ค. 46๋ถ๋ฌธ์ ๊ฐ๊ฐ ๋ณด์ง ์๊ณ ํ ๋ฒ์ ํธ์ถ๋ก ์ง๊ณ ์์กด์ ๋ณผ ์ ์๊ฒ ๊ฐ ํ๋๋ฅผ ๋ด๋ณด๋ด๋ ๋ฐฉ์์ ๋ณด๊ณ ์์ต๋๋ค.
์ ํํ ๊ด์ธก๊ฐ์ผ๋ก ์ง๋ฌธํด ์ฃผ์ ์ ์ถ์ ์ด ๋นจ๋์ต๋๋ค.
Scored. This is a hold, not a stall. And here is the field that tells them apart.
1. Submission 44EC5F0856EA941A was scored three minutes after acceptance
Accepted 2026-10-26 00:00:15 KST, scored 00:02:58, rollup 00:02:59. Result: primary metric MAE 0.65055, 1,338 compounds scored, 0 missing, leak check clean.
2. Why there is no new row
Your revealed best on hERG is 0.5888, and lower is better on this board. The new score of 0.65055 is worse, so the row was not replaced. The record says so directly:
"ladder": {"revealed": 0.5888, "state": "held", "best": 0.5888}
"reveal_step": 0.014546555350190326
This is the second of the two cases you described.
3. The liveness field is the board's updated, not a row's scored_at
You already observed it: hERG's updated moved to your submission time. That observation was correct. The board's updated moves on every rollup, even when no row changes. A row's scored_at moves only when that row is revealed. That is why the latest row scored_at across the 46 boards is 20 October: that was the last time any row was actually revealed, not the last time scoring ran.
4. scoring_here: false means this Space does not score. Scoring runs on a separate machine. It is a statement of architecture, not a fault signal.
5. Nothing is pending. Your submission was the most recent across all 46 boards, and none has arrived since.
6. Your point stands. Without knowing to read updated, a hold and a stall look identical from outside. We are looking at exposing a single value so that pipeline liveness takes one call rather than 46.
Your observations were precise, which made this quick to trace.