Maestro DocsCoding and HDL
The coding workspace
The problem, editor and console, and how autosave and grading work.
Coding questions open in a full-screen workspace.
Layout
- Problem pane (left): the statement, input and output format, Examples, constraints and an optional note. You can mark the question for review from here.
- Editor (right): where you write code. On a phone the problem and code are separate tabs: Description and Code.
- Console (below the editor): collapsible, with the tabs below.
Drag the dividers to resize each part.
Editor toolbar
- Language dropdown: choose from the languages the question allows. If you haven't edited the box, switching language swaps in that language's starter code. If you already typed something, your code stays.
- Reset: puts the starter code back.
The editor colours the syntax of each language, including Verilog, Octave and SPICE.
Console tabs
| Tab | What it shows |
|---|---|
| Testcase | The sample inputs, and a Custom input switch. |
| Test Result | The results of your last run. |
| Testbench | Read-only support files for electronics questions, such as the Verilog testbench. It's called Hardware files for Embedded C. Shown only when the question has them. |
Running your code
Press Run sample tests. This runs only the visible sample cases. Turn on Custom input and the button becomes Run custom input: it runs the single input you typed and shows the output, with no pass or fail verdict. Runs never use the hidden tests.
Autosave
Your code saves automatically a moment after you stop typing, and the save indicator at the top of the test shows when it's saved. You don't need to save before leaving.
Run limits
- By default you can run your code 30 times a minute. If you go over, you'll see "Too many runs". Wait a moment.
- Free mock attempts also have a daily run limit (200 by default).
- If the runner is briefly unavailable, you'll see "Code execution is temporarily unavailable. You can still submit your answer."
See Running and errors for how to read results.