plom-new-demo

usage: plom-new-demo [-h] [--version] [--port PORT]
                     [--length {quick,normal,long,plaid}] [--solutions]
                     [--no-solutions] [--versioned-id] [--multiversion]
                     [--no-multiversion] [--half-marks] [--muck] [--no-muck]
                     [--stop-after {users,spec,sources,populate,papers-built,bundles-created,bundles-uploaded,bundles-pushed,rubrics,qtags,auto-id,randoiding,randomarking,tagging,spreadsheet,reassembly,reports} | --wait-after {users,spec,sources,populate,papers-built,bundles-created,bundles-uploaded,bundles-pushed,rubrics,qtags,auto-id,randoiding,randomarking,tagging,spreadsheet,reassembly,reports}]
                     [--development | --production]

Named Arguments

--version

show program’s version number and exit

--port

Port number on which to launch server

Default: 8000

--length

Possible choices: quick, normal, long, plaid

Describe length of demo

Default: 'normal'

--solutions

Upload solutions to demo server

Default: True

--no-solutions

Default: True

--versioned-id

Default: False

--multiversion

Run the demo with multiple-versions (ie 3) when true (which is default) or only a single version of the assessment when false.

Default: True

--no-multiversion

Default: True

--half-marks

Default: False

--muck

Run pdf-mucking to simulate poor scanning of papers (not functional yet)

Default: True

--no-muck

Default: True

--stop-after

Possible choices: users, spec, sources, populate, papers-built, bundles-created, bundles-uploaded, bundles-pushed, rubrics, qtags, auto-id, randoiding, randomarking, tagging, spreadsheet, reassembly, reports

Stop the demo sequence at a certain breakpoint. Leave the server running.

--wait-after

Possible choices: users, spec, sources, populate, papers-built, bundles-created, bundles-uploaded, bundles-pushed, rubrics, qtags, auto-id, randoiding, randomarking, tagging, spreadsheet, reassembly, reports

Stop the demo sequence at a certain breakpoint. Terminate the server.

--development

Run the Django development webserver (this is the default for the demo but do not use this in production).”

Default: True

--production

Run a production Gunicorn server.

Default: True

The –stop-after and –wait-after options take many possible values. If both are omitted, the code behaves like –wait-after rubrics.

  • users = the basic plom-system (server, db, etc) are set up, and demo-users are created.

  • spec = a demo assessment specification is uploaded.

  • sources = demo assessment sources are uploaded. Also a classlist and (if selected) solutions.

  • populate = the database is populated with papers.

  • papers-built = assessment PDFs are created from the sources.

  • bundles-created = PDF bundles are created to simulate scanned student work.

  • bundles-uploaded = those PDF bundles are uploaded and their qr-codes read (but not processed further).

  • bundles-pushed = those bundles are “pushed” so that they can be graded.

  • rubrics = system and demo rubrics are created for marking.

  • qtags = demo question-tags are created.

  • auto-id = run the auto-id-reader

  • randoiding = run rando-id’er to identify papers, will use best predictions to ID papers and else random. You will need to have the plom-client installed.

  • randomarking = several rando-markers are run in parallel to leave comments and annotations on student work. You will need to have the plom-client installed.

  • tagging = (future/not-yet-implemented) = pedagogy tags will be applied to questions to label them with learning goals.

  • spreadsheet = a marking spreadsheet is downloaded.

  • reassembly = marked papers are reassembled (along, optionally, with solutions).

  • reports = (future/not-yet-implemented) = instructor and student reports are built.