Joining a class and submitting work

The code, the assignment list, and the Submit button in the editor.

Joining

Your teacher gives you a six-character code. Go to /class, type it in and press the button. That is the whole thing.

The code is upper case and has no O, I, L, 0 or 1 in it, so if you are looking at something that could be a letter O it is a zero, and it is not.

You need an account to join a class, because a class is a roster and a roster needs names. You do not need one to use Mokxi: the simulator works signed out and always will. See signing in.

Your class page

/class/<id> lists the work your teacher has assigned: each assignment with its title, its due date if it has one, and an Open button.

Opening one puts you in the editor with the circuit or the lesson already loaded.

Parts that will not move

Some assignments come with part of the circuit held in place. A held part wears a small padlock, a held wire is drawn a shade back, and the cursor over either one is a no-drop. Select one and the properties panel shows its fields switched off over a line saying Locked. Only the person who set this work can unlock it.

That is on purpose, and it is only the starter. You can still do everything the work asks of you: add parts, wire into a locked part's pins, name nets, change anything you added, run it and read all of it.

Sometimes the code is held too. The file strip says Locked by whoever set this work. You can read it and run it.

Copying a locked part gives you one of your own. A copy is yours, so it pastes unlocked. Forking the assignment into your own project does not unlock it: the copy is the same work, and owning it is not being the person who set it. Ask your teacher if something is held that should not be.

Submitting work

Build the thing, then open the Save menu in the editor's header. With an assignment open there is one extra item in it, and pressing that submits the saved project to the class.

You can submit again. The latest one is what your teacher sees.

For a lesson, your progress goes with it, so passing seven of nine steps shows as seven of nine rather than as nothing.

Checking your own work

Some work is set with checks on it: things your teacher expects your circuit to do, written once and run on everybody's. Where there are any, your class page has a Check my work button under that piece of work.

Pressing it runs your own circuit, here in your browser, on the same simulator the editor uses, and tells you how each check went with the number it measured beside the number that was wanted: it toggled every 1462 ms; expected every 1000 ms, within 50. That is a thing you can go and fix. You can press it as often as you like, and what it finds goes to your teacher with your submission, so they see what you saw.

It is grading the simulation, which is not a bench: the timing is ideal and there is no analog noise, and the panel says so. And it never shows you your teacher's circuit or anybody else's, only your own.

What your teacher can see

The work you submitted to that class, and how far through a lesson you got.

Not your other projects. A project is private when you make it and stays private until you make it public, whether or not you are in a class.

Leaving

Leave this class on the class page. Your own projects stay in your account. The submissions you made to that class do not.

Getting your work out

Any project saves to a file and opens again anywhere, with no account. That is worth doing at the end of a course, so what you built does not depend on a class you are no longer in.

Earning something for it

Passing a lesson step earns XP, and the steps the simulator actually checks are worth more than the ones you tick. See XP and levels and streaks and badges. Joining a class is itself a badge.