=============
The Challenge - Luhn's Mod
=============


In 1954, Hans Luhn of IBM proposed an algorithm to be used as a validity criterion for a given set of numbers. Almost all credit card numbers are generated following this validity criterion…also called as the Luhn check or the Mod 10 check. It goes without saying that the Luhn check is also used to verify a given existing card number. If a credit card number does not satisfy this check, it is not a valid number.

Out of the 16 numbers on a typical credit card, the set of first 6 digits is known as the issuer identifier number, and the last digit is known as the “check digit” which is generated in such a way as to satisfy the Luhn or Mod 10 check.

For a 16 digit credit card number, the Luhn check can be described as follows:

1. Starting with the check digit, double the value of every second digit (never double the check digit). For example, in a 16 digit credit card number, double the 15th, 13th, 11th, 9th…digits (digits in odd places). In all, you will need to double eight digits.

2. If doubling of a number results in a two digit number, add up the digits to get a single digit number. This will result in eight new single digit numbers.
3. Now, replace the digits in the odd places (in the original credit card number) with these new single digit numbers to get a new 16 digit number.
4. Add up all the digits in this new number. If the final total is perfectly divisible by 10, then the credit card number is valid (Luhn check is satisfied), else it is invalid.

Example:
 Code:
                           
4 5 5 2 7 2 0 4 1 2 3 4 5 6 7 8 <-starting card number, last digit is the check digit
8  10  14   0   2   6  10  14   <-doubled value of every second digit starting from right
8   1   5   0   2   6   1   5   <-if the number > 10 add up the digits to get a single digit number
8 5 1 2 5 2 0 4 2 2 6 4 1 6 5 8 <-This is the new number.  Add up the digits. 
=61                             <-61 is not perfectly divisible by 10, and fails the test.

There are many brands of credit cards, but the following are the only brands your company will accept.
 Code:
Brand        Number of Digits 	Example of a Valid Card 
--------------------------------------------------------
AmKixpress   15			373633498141735
Kixa         16			4929930484621725
MasterScript 16			5380933823620159
Dectohex     16			6011691716199864

For the purposes of this tournament, and to destinguish between brands, each company always starts it's cards with the same first digit. For example Kixa always starts with a "4".

AmKixpress only has 15 digits, however all the others have 16 digits.

The Expiration Date and CCV Number are not part of this challenge.

** These are NOT valid credit card numbers. You can't buy anything with these. They are random numbers that happen to conform to the algorithm. **

*-->A download is available at http://www.kixtart.org/forums/ubbthreads.php?ubb=download&Number=208

=============
Specification
=============


Determine whether the numbers provided in the input:
1) Passes Luhn's Check
2) Has the proper number of digits for it's issuer
3) Is a card your company accepts

=============
Inputs
=============

The input consists of a string of numbers. (The limits within Kixtart and such a large number requries that the input be a string.)

=============
Outputs
=============


0, 3, 4, 5 , or 6.

0 = Fails any test
3 = Valid AmKixPress
4 = Valid Kixa
5 = Valid MasterScript
6 = Valid Dectohex

=================================================================
Notes
===========================================================+====

- The scoring engine is based on older engine, so there may be something like block comments that are not supported.
- The scoring engine has added code to help diagnose which cases are failing. To see test case resutls: kix32 kixgolf_lm $verbose=1
- 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:
 Code:
for $b=0 to ubound($a)
  if $a[$b]>0
    $c=$c+1
  endif
next

for a score of 45.

Another solution is:
 Code:
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: 2010-08-01 to 2010-08-08 (Official Count down clock will determine end time)

2) Public coding phase: 2010-08-08 to 2010-08-15

3) Final results: 2010-08-16


*--> You will need the complete package from http://www.kixtart.org/forums/ubbthreads.php?ubb=download&Number=208.


Attachments
kixgolf_lm.zip (379 downloads)
Description: