[GH-ISSUE #1317] [Bug] Labs lab01 #4372

New Issue

GiteaMirror · 2026-04-19T12:23:36-05:00

GiteaMirror commented

2026-04-19 12:23:36 -05:00

Originally created by @asgalon on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1317

Area

Other

Location

Labs Vol1 lab01_ml_intro

Description

part[ABC]_prediction ui radio elements are defined, but never rendered, so the values are never set.

Expected Behavior

Working through the lab until the complete flow seems correct.

Environment (TinyTorch bugs only)

No response

Originally created by @asgalon on GitHub (Apr 10, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1317 ### Area Other ### Location Labs Vol1 lab01_ml_intro ### Description - part[ABC]_prediction ui radio elements are defined, but never rendered, so the values are never set. ### Expected Behavior Working through the lab until the complete flow seems correct. ### Environment (TinyTorch bugs only) _No response_

GiteaMirror added the area: book type: bug labels 2026-04-19 12:23:36 -05:00

GiteaMirror closed this issue

2026-04-19 12:23:37 -05:00

GiteaMirror commented

2026-04-19 12:23:39 -05:00

@asgalon commented on GitHub (Apr 10, 2026):

"Part C - The Triad across Targets"

There seems to be a discrepancy between the question (512KB SRAM) for the prediction and the evaluation below (7812 KB SRAM):

Also: Below it says "Correct 6x" while above Prediction "200x":

@asgalon commented on GitHub (Apr 10, 2026): "Part C - The Triad across Targets" There seems to be a discrepancy between the question (512KB SRAM) for the prediction and the evaluation below (7812 KB SRAM): <img width="1614" height="901" alt="Image" src="https://github.com/user-attachments/assets/5a7ad88f-b79c-4779-93ac-9e0a909d4215" /> Also: Below it says "Correct 6x" while above Prediction "200x": <img width="1614" height="835" alt="Image" src="https://github.com/user-attachments/assets/848339f4-cbed-40d9-bece-300a6ca7f1c9" />

GiteaMirror commented

2026-04-19 12:23:39 -05:00

@asgalon commented on GitHub (Apr 10, 2026):

The tabs below seem to have the prediction radios that are needed in the first cells above to unlock the rest, so clicking on a radio button there jumps back to one of the top cells, this look a bit odd too.

I notice the ledger below does not show the track selection I made yesterday with lab00, but I probably did that in a different browser profile. Something to check later.

@asgalon commented on GitHub (Apr 10, 2026): The tabs below seem to have the prediction radios that are needed in the first cells above to unlock the rest, so clicking on a radio button there jumps back to one of the top cells, this look a bit odd too. I notice the ledger below does not show the track selection I made yesterday with lab00, but I probably did that in a different browser profile. Something to check later.

GiteaMirror commented

2026-04-19 12:23:39 -05:00

@asgalon commented on GitHub (Apr 10, 2026):

Need to resolve evaluation issues with #1306 before adding more PRs...

@asgalon commented on GitHub (Apr 10, 2026): Need to resolve evaluation issues with #1306 before adding more PRs...

GiteaMirror commented

2026-04-19 12:23:40 -05:00

@asgalon commented on GitHub (Apr 14, 2026):

PR check fails for unknown reason. This is either some error introduced with the changes or the automated test itself has some issue that needs to be resolved. In the former case, it is not clear to me how it should be tested locally before pushing the branch, in the latter, the labs processing in the github PR task has insufficient log output, or the decisive parts are not visible to me...
The trouble seems to be the "run quarto render" phase building the labs site. The error message of the next step (validation) is not very helpful. Perhaps it is possible to Increase the log level here? It could be something simple with the quarto command

@asgalon commented on GitHub (Apr 14, 2026): PR check fails for unknown reason. This is either some error introduced with the changes or the automated test itself has some issue that needs to be resolved. In the former case, it is not clear to me how it should be tested locally before pushing the branch, in the latter, the labs processing in the github PR task has insufficient log output, or the decisive parts are not visible to me... The trouble seems to be the "run quarto render" phase building the labs site. The error message of the next step (validation) is not very helpful. Perhaps it is possible to Increase the log level here? It could be something simple with the quarto command

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#4372