-- The function get_name() should return a single string that is the name of the puzzle.
--
function get_name()
    return "MOTORISED COORDINATE TRACKER"
end

-- The function get_description() should return an array of strings, where each string is
-- a line of description for the puzzle. Surrounding text with asterisks will cause it to
-- be rendered in bold, something we use when mentioning a signal by name.
--
-- By using the syntax that we use in our puzzle descriptions, you can also create tables:
--
--       "| This is a table. | This is a second column. | This is a column with "
--       "|                  |                          | multiple line of text."
--       "----------------------------------------------------------------------"
--       "| This is a second |                          | More text here!       "
--       "| table row.       |                          |                       "
--
-- Puzzle descriptions are not automatically paginated, so you can use the string "<PAGE>"
-- to start a new page of text. If you don't it will overflow and make Zach sad.
--
function get_description()
    return {
        "*MotorA* and *MotorB* are simple inputs connected to the left and right tracks of the bot.",
        "*coord-X* and *coord-Y* are XBus outputs connected to a map grid system.",
        "The motors have 0, 50 and 100 outputs to control reverse, halt and forward functions respectively.",
        "For each time unit, track the position of the bot.",
        "The Bot starts facing up (North).",
        "Turning does not change the coordinates.",
        "<PAGE>",
        "HALTING means the bot does not move or turn.",
        "Moving FORWARD means moving the bot one unit in the direction it is facing.",
        "Moving BACKWARD means moving the bot one unit in the opposing direction it is facing.",
        "Turning LEFT means changing the direction the bot is facing 90 degrees anti-clockwise from Bird's Eye.",
        "Turning RIGHT means changing the direction the bot is facing 90 degrees clockwise from Bird's Eye.",
        "Table on next page >>>",
        "<PAGE>",
        "| Function | MotorA | Motor B",
        "-----------------------------",
        "| HALT | 50 | 50",
        "-----------------------------",
        "| MOVE FORWARD | 100 | 100",
        "-----------------------------",
        "| MOVE BACKWARD | 0 | 0",
        "-----------------------------",
        "| TURN LEFT | 0 | 100",
        "-----------------------------",
        "| TURN RIGHT | 100 | 0",
    }
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 [[
        #################.
        0################2
        ##################
        ##################
        ##################
        1################3
        ################..
    ]]
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 (C2S-RF901), 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 (N4DL-1000), 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 Turn(n, left)
    if left then
        return (n-1)%4
    end
    return (n+1)%4
end



function get_data()
    inputA = {}
    inputB = {}
    X = {}
    Y = {}
    time = 1

    BiasMove = math.random(100, 200)
    BiasTurn = math.random(50, 100)

    BiasLeft = math.random(0, 99)
    BiasForward = math.random(0, 99)

    Direction = 0
    x = 0
    y = 0


    while time <= 60 do
        instr = math.random(0, 300)
        move = false
        if BiasMove >= instr then
            move = true
            if BiasForward > math.random(0, 99) then
                inputA[time] = 100
                inputB[time] = 100
            else
                inputA[time] = 0
                inputB[time] = 0
            end
        elseif BiasMove + BiasTurn >= instr then
            if BiasLeft > math.random(0, 99) then
                inputA[time] = 0
                inputB[time] = 100
                Direction = Turn(Direction, true)
            else
                inputA[time] = 100
                inputB[time] = 0
                Direction = Turn(Direction, false)
            end
        else
            inputA[time] = 50
            inputB[time] = 50
        end

        if move then
            Ahead = (inputA[time]==100)
            if Direction > 1 then
                Ahead = not Ahead
            end
            if Direction%2 == 0 then
                if Ahead then
                    y = y + 1
                else
                    y = y - 1
                end
            else
                if Ahead then
                    x = x + 1
                else
                    x = x - 1
                end
            end
        end

        X[time] = {x}
        Y[time] = {y}

        time = time + 1
    end

    create_terminal("MotorA", "0", TYPE_SIMPLE, DIR_INPUT, inputA)
    create_terminal("MotorB", "1", TYPE_SIMPLE, DIR_INPUT, inputB)
    create_terminal("coord-X", "2", TYPE_XBUS, DIR_OUTPUT, X)
    create_terminal("coord-Y", "3", TYPE_XBUS, DIR_OUTPUT, Y)
end