SHENZHEN I/O

SHENZHEN I/O

HANDHELD GEIGER COUNTER
11 条留言
BtB 2017 年 2 月 12 日 上午 1:59 
Resetting the counter, then adding the current count, is counterinuitive, I tried both subtracting the limit and setting to zero after the click, but neither was correct. Basically, this version records the counts on a click cycle twice.

Otherwise it was a neat project.
Shadowwolf0357 2017 年 1 月 26 日 下午 2:12 
For anyone wanting help here is my solution. 5 yen, 565 power, 10 lines of code.

add p0
mov acc x2
mov dat acc
add p0
tgt acc x0
- mov acc dat
mov p0 acc
- slp 1
+ mov 0 dat
+ gen p1 1 0
Shadowwolf0357 2017 年 1 月 26 日 下午 2:10 
Great puzzle mate. Only complaint would be the slightly unclear specifications but other than that it's great.
Nickardson 2016 年 12 月 3 日 下午 12:33 
This was a joy to optimize. The ¥5 one especially.
Tzaphqiel 2016 年 12 月 3 日 上午 11:40 
@Javarra: Thanks for the clarification. Considering that the sum of the current and previous time slices is also a sort of cumulative total it wasn't quite clear from the original specification that those were supposed to be separate processes.
grasspound 2016 年 12 月 3 日 上午 8:58 
Subscribe to the steam workshop version, not the custom spec you uploaded. It should be there when you solve it
BlaXpirit 2016 年 12 月 3 日 上午 8:45 
@The Slothful Pixie, what histograms? I'm not seeing any histograms for Workshop puzzles :(
The Slothful Pixie 2016 年 12 月 3 日 上午 8:43 
Once I figured out quite what the specification meant by looking at the verification panel I managed 5¥ - histograms say everyone else went for 6¥ solutions with 2xMC4000
BlaXpirit 2016 年 12 月 3 日 上午 2:29 
It's true that the description is confusing. It is not entirely clear that the speaker output depends on "total number of particles so far" and is completely separate from the other output. You also fail to mention that the total should be reset when the speaker clicks.
I actually had to look at the source code to figure this out.
Javarra  [作者] 2016 年 12 月 3 日 上午 2:22 
@Tzaphqiel: You're conflating the two outputs; the speaker is based on the total count since the previous click (or since the start of the test run). The first click in the first test run happens at a total of of 133, the second at 121, the third at 113, etc.
Tzaphqiel 2016 年 12 月 2 日 下午 8:42 
The speaker output seems off. It starts with a sensitivity of 83 but the verification feed tells me to send a click to the speaker when the cumulative totals are 75, 77, and 62 while not sending clicks when the cumulative totals are 104, 93, and 97. I'm not quite sure what the error is, as it also correctly expects clicks with totals at 113, 94, and 85 and expects no clicks with totals at 12, 29, and 82. There's also two different cases where the cumulative total is 81: one which (correctly) expects no click and one which (incorrectly) expects a click.