PRIME FACTOR CALCULATOR

-- The function get_name() should return a single string that is the name of the puzzle.
--
function get_name()
    return "PRIME FACTOR CALCULATOR"
end

-- The function get_description() should return an array of strings, where each string is
-- a line of description for the puzzle. Puzzle descriptions are not automatically paginated,
-- so you can use the string "<PAGE>" to start a new page. Surrounding text with asterisks
-- will cause it to be rendered in bold, something we use when mentioning a signal by name.
--
function get_description()
    return {
        "*keypad* is an XBus input connected to a numeric keypad.",
        "*factors* is an XBus output connected to a display device.",
        "When a value is received from the *keypad*, send the prime factors of that number, in increasing order, to *factors*",
        "Inputs are always between 2 and 99, inclusive.",
    }
end

-- The function get_board() allows you to specify an 18x7 "ASCII art" grid to customize
-- the layout of the board and the placement of the input and output terminals. Generally
-- speaking, inputs are placed on the left of boards, while outputs are placed on the right.
--
-- For empty space, use the '.' character.
-- For buildable board space, use the '#' character.
-- For an input or output terminal, use characters '0' through '9' no more than once each.
-- For the bottom-left corner of the radio, use the 'R' character.
-- For the bottom-left corners of dials, use characters 'A', 'B', and 'C'.
--
function get_board()
    return [[
        ...##############.
        ..################
        #################1
        ##################
        0#################
        #############.....
        #############.....
    ]]
end

-- The function get_data() is called both to establish information about the puzzle (such as what
-- the inputs and outputs are) and to generate the random test cases. Signal levels and XBus data
-- should change from call to call, but information like the names and types of terminals should
-- not change at all.
--
-- To create a standard input or output terminal, call create_terminal(). Valid terminal types are
-- TYPE_SIMPLE, TYPE_XBUS, and TYPE_XBUS_NONBLOCKING. Valid terminal directions are DIR_INPUT and
-- DIR_OUTPUT. Valid data for a simple I/O signal is an array of integers, 0 - 100 inclusive. Valid
-- data for an XBus signal is an array of integer arrays, each with values -999 to 999 inclusive.
--
--       create_terminal(name, board_character, type, direction, data)
--
-- To create a radio, call create_radio(). You may only create one radio in each puzzle. Since radios
-- are XBus-only, the only valid data for data_rx and data_tx are arrays of integer arrays, each with
-- values -999 to 999 inclusive. You cannot customize the signal names for a radio.
--
-- By default the radio will be placed in the bottom-left corner of the screen. However, if you use an
-- 'R' character in your board layout, the bottom-left corner of the radio will be placed there instead.
--
--       create_radio(data_rx, data_tx)
--
-- To create a dial, call create_dial(). You may create up to three dials in each puzzle. The names
-- of dials should be kept short, as there is not much room to display them visually. A valid value
-- is an integer between 0 and 99, inclusive.
--
-- By default dials will be placed in the bottom-left corner of the screen. However, if you use an
-- 'A', 'B', or 'C' character in your board layout, the bottom-left corners of the first, second, and
-- third dials will be placed there, respectively.
--
--       create_dial(name, value)
--
-- NOTE: To generate random values you should use math.random(). However, you SHOULD NOT seed
--       the random number generator with a new seed value, as that is how the game ensures that
--       the first test run is consistent for all users, and thus something that allows for the
--       comparison of cycle scores.
--
-- NOTE: Fun fact! Arrays in Lua are implemented as tables (dictionaries) with integer keys that
--       start at 1 by convention. Contrast this with nearly every other programming language, in
--       which arrays start with an index of 0. Because of this, the 60 "time slices" that make
--       up a test case are indexed from 1 to 60 inclusive.
--
function get_data()
    keypad = {}
    factors = {}
    time = math.random(1, 5)

    while time <= 60 do
        input = math.random(2, 99)
        keypad[time] = {input}

        current_factors = {}
        factor_index = 1
        factor = 2
        while input ~= 1 do
            if (input % factor) == 0 then
                current_factors[factor_index] = factor
                factor_index = factor_index + 1
                input = input / factor
            else
                factor = factor + 1 -- this is inefficient, but shouldn't make a difference with such tiny numbers
            end
        end

        factors[time] = current_factors

        -- Add a delay long enough to make sure there is no overlap in the output display, plus some random delay
        time = time + (factor_index - 1) + math.random(0, 3)
    end

    create_terminal("keypad", "0", TYPE_XBUS, DIR_INPUT, keypad)
    create_terminal("factors", "1", TYPE_XBUS, DIR_OUTPUT, factors)
end