#212828 - 2017-11-05 06:00 PM
Kixgolf - Digital Root Clocks: Private Round
|
Jochen
KiX Supporter
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
=================================
The Challenge - Digital Root Clocks
=================================
The following (sparing outputs) is completely and shamelessly copied from https://projecteuler.net/problem=315 
Sam and Max are asked to transform two digital clocks into two "digital root" clocks.
A digital root clock is a digital clock that calculates digital roots step by step.
nB.: to get to the digital root of a number, sum the digits of that number and intermediate results until you end up with a number less or equal 9
When a clock is fed a number, it will show it and then it will start the calculation, showing all the intermediate values until it gets to the result.
For example, if the clock is fed the number 137, it will show: "137" -> "11" -> "2" and then it will go black, waiting for the next number.
Every digital number consists of some light segments: three horizontal (top, middle, bottom) and four vertical (top-left, top-right, bottom-left, bottom-right).
Number "1" is made of vertical top-right and bottom-right, number "4" is made by middle horizontal and vertical top-left, top-right and bottom-right. Number "8" lights them all.
The clocks consume energy only when segments are turned on/off.
To turn on a "2" will cost 5 transitions, while a "7" will cost only 4 transitions.
Sam and Max built two different clocks.
Sam's clock is fed e.g. number 137: the clock shows "137", then the panel is turned off, then the next number ("11") is turned on, then the panel is turned off again and finally the last number ("2") is turned on and, after some time, off.
For the example, with number 137, Sam's clock requires:
"137" : (2 + 5 + 4) × 2 = 22 transitions ("137" on/off).
"11" : (2 + 2) × 2 = 8 transitions ("11" on/off).
"2" : (5) × 2 = 10 transitions ("2" on/off).
For a grand total of 40 transitions.
Max's clock works differently. Instead of turning off the whole panel, it is smart enough to turn off only those segments that won't be needed for the next number.
For number 137, Max's clock requires:
"137" : 2 + 5 + 4 = 11 transitions ("137" on)
7 transitions (to turn off the segments that are not needed for number "11").
"11" : 0 transitions (number "11" is already turned on correctly)
3 transitions (to turn off the first "1" and the bottom part of the second "1";
the top part is common with number "2").
"2" : 4 transitions (to turn on the remaining segments in order to get a "2")
5 transitions (to turn off number "2").
For a grand total of 30 transitions.
Of course, Max's clock consumes less power than Sam's one.
As we are very keen on being environmentally friendly and save energy where we can, we are interested in the savings Max's clock has to offer.
Your code shall therefore return the differences between the total number of transitions needed by Sam's clock and that needed by Max's one.
So, for 137 as input the code should return 10 [ 40(Sam) - 30(Max) = 10(saving) ]
*-->A download is available at http://www.kixtart.org/forums/ubbthreads.php?ubb=download&Number=370
================
Inputs and Outputs
================
Input
String of digital root clock value
Example Input
89
Output
Integer or String of calculated savings
Example Output
20
================================================================
Notes
================================================================
- The scoring engine has added code to help diagnose which cases are failing. To see test case results:
kix32 kixgolf_drc $verbose=1 ;shows failing results
kix32 kixgolf_drc $verbose=2 ;shows all results
- The scoring engine expects your (primary) function to be named a().
=======
Scoring
=======
The solution must pass all tests in order for it's KiXgolf Score to be considered.
When posting KiXtart Golf Scores, please include the KIXGOLF_*.TXT file that is created in the script directory. It contains some basic information about the computer that the script is run on and the resulting scores.
============
Test program
============
Test cases are provided to help screen entries and to provide the Golf Score.
Any script that passes the test cases can be submitted. If you are surprised that your solution passed the test cases, please submit it anyway! That will help me identify bugs in the test program.
================================================================
KiXtart GOLF - How To Play
================================================================
Most importantly, anybody can play, no age restrictions, no penalties, no handicap!
The object in "real" golf is to hit the ball in the hole in the fewest strokes. The object in KiXtart Golf is to get from input (tee) to target (hole) in the fewest keystrokes.
Example: How many positive elements are in array $a?
Array $a could be of structure $a=[1, 2 ,-3, 4, -5, -7, 8, 9]
One approach:
for $b=0 to ubound($a)
if $a[$b]>0
$c=$c+1
endif
next
for a score of 45.
Another solution is:
DO
$b=$b+1
if $a[$b]>0
$c=$c+1
endif
UNTIL $b>(UBOUND($a)+1)
for a score of 53.
Better approach: Code sample 1
================================================================
KiXtart GOLF - The Rules
================================================================
1) The goal of KiXtart Golf is to score the lowest strokes.
2) Strokes are all characters in a piece of code except whitespace characters, unless the whitespace character is necessary for the line of code to work. Therefore, carriage returns and line feeds do not count or spaces in between the '=' sign when assigning variables, e.g. '$a = $b' scores 5.
3) Code can be constructed any way you like, as long as it does not generate syntax or other errors when running the script in KiXtart.
4) The final solution MUST pass all test scripts that are part of the KiXtart golf challenge.
7) During the private coding phase, no code is allowed to be posted. Violations result in disqualification of said player.
8) During the public coding phase, code should be posted, reused, and borrowed from other players.
9) The test script contains the official KiXgolf scoring engine
10) Only the person posting a particular score will be recognized for the score, unless the KiXtart Golf Challenge organizer or another delegate posts code on behalf of a player
11) KiXtart Golf (a.k.a KiXgolf) codes must be written inside the KiXgolf UDF collection tags, ';!' and ';!;!'
12) Parameter names of the UDF's can be changed and additional optional parameters can be added.
13) Additional helper UDFs and code can be written as long as they reside inside the ';!' and ';!;!' tags.
14) The use of '$' as a variable is allowed.
15) The UDF layout is up to coder.
16) The UDF is expected to finish in a reasonable time, that is, on modern computers inside 1 hour timeframe.
17) You can submit scores as often as you want.
18) If you reach leading score, you are obligated to post your score immediately so others can try to compete with you.
19) The UDF may only use the KiXtart/KiXforms commands/functions/macros, no other code fragments are allowed.
20) Calls to COM components that are part of a standard default Windows installation are allowed.
21) The use of the KiXforms DLL is also permitted as the KiXforms DLL can now be considered an integral part of KiXtart scripting.
22) Calls to other executables, as long as they are part of a standard default Windows installation are allowed.
23) The UDF should be self-contained (except for any I/O mentioned in the challenge). In particular, you may not do things like fetching extra data from a remote site or file.
24) You may assume ASCII as character set.
25) You may use block comments as the KiXgolf Scoring Engine now supports block comments.
26) You are allowed to only use publicly available versions of KiXtart and KiXforms, private builds or alpha builds are NOT allowed.
27) Your submitted score must include the result print of the KiXgolf test-engine.
28) The SETOPTION() parameters in the KiXgolf script may not be modified and will govern the script behavior. SETOPTION() parameters may change depending on the particular needs of the KiXgolf challenge.
29) Tokenizing the UDF, script, or portions thereof is not allowed.
30) If something is not explicitly denied by the rules, it's allowed.
31) If Confusion arises, arranger of the KiXgolf round has the final say.
32) Additional test cases can be added at any time during the KiXgolf round. The code is expected to pass based on the rules. The test cases may not include tests for all rules and exceptions. Test cases that are added during the public round will not alter the results of the private round.
================================================================
KiXtart GOLF - The Duration of the Competition
================================================================
1) Private coding phase: 2017-11-05 to 2017-11-12 (Official Count down clock will determine end time)
2) Public coding phase: 2017-11-12 to 2017-11-19
3) Final results: 2017-11-19
Attachments
kixgolf_drc.zip (288 downloads)
Description:
_________________________
|
|
Top
|
|
|
|
|
#212843 - 2017-11-08 02:22 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Jochen]
|
Allen
KiX Supporter
Registered: 2003-04-19
Posts: 4562
Loc: USA
|
Okay... so where might I be going wrong here?
Sam Max
7+5 (7+5)*2
89
5+1 (2+4)*2
17
5+4 (7)*2
8
3+4
=34 =50
|
|
Top
|
|
|
|
#212844 - 2017-11-08 02:52 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Allen]
|
Jochen
KiX Supporter
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
|
|
Top
|
|
|
|
|
#212845 - 2017-11-08 02:58 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Jochen]
|
Allen
KiX Supporter
Registered: 2003-04-19
Posts: 4562
Loc: USA
|
The 7 got me earlier... I never noticed the 9 having a bottom.
Thanks.
|
|
Top
|
|
|
|
|
#212849 - 2017-11-08 05:14 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Jochen]
|
Allen
KiX Supporter
Registered: 2003-04-19
Posts: 4562
Loc: USA
|
I already saw the similarities in Sam's and Max's scores but didn't go down that road yet because I just wanted a working function first.
Substitute Positions... that was the first thing I figured out.  It was the damn counting I had so much trouble with. 
No idea on others... I sent invites to everyone I had on my list and only heard from Jooel.
|
|
Top
|
|
|
|
|
#212850 - 2017-11-08 05:25 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Allen]
|
Allen
KiX Supporter
Registered: 2003-04-19
Posts: 4562
Loc: USA
|
FFS... where's that golfer with the head exploding avatar when you need it?
KiXtart Version = 4.66
KiXGolf Script = kixgolf_drc.KIX
Scoring Engine = 3.3
OS = Windows 10 Pro
CPU = Intel Pentium III Xeon
Speed = 3392 MHz
Memory = 16384 MB
Tournament = Digital Root Clocks
Processing Start = 2017/11/08 11:21:14.045
Processing End = 2017/11/08 11:21:15.045
Duration = 0000/00/00 00:00:01.000
# Tests Run = 10
# Tests Passed = 4
# Tests Failed = 6
Result = Failed
|
|
Top
|
|
|
|
|
#212852 - 2017-11-08 05:39 PM
Re: Kixgolf - Digital Root Clocks: Private Round
[Re: Allen]
|
Jochen
KiX Supporter
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 837 anonymous users online.
|
|
|
