When using Relate with online proctoring (e.g. proctor.io<http://proctor.io> or the CBTF) does anyone have any experience with spotting internet access? For example, if a student’s internet goes down for a flash or for a minute, with they be able to reconnect to the exam? Also, is there any documentation on setting up the in-facility section for this scenario?
"Koyejo, Sanmi" <sanmi(a)illinois.edu> writes:
> Thoughts on how easy/hard it might be to integrate nbgrader into relate? I really like the
> notebook feature: https://github.com/jupyter/nbgrader
You're not alone! I've been hoping to more seamlessly integrate
(Jupyter) notebooks into Relate. The ideal-world version would be to
have a page in a flow be a fully interactive notebook (which could be
graded in conjunction with nbgrader). A simpler version might be for a
student to just upload a notebook they worked on outside of relate, and
for nbgrader to run on that inside of a container that Relate launches
through its Docker integration. The least fancy version (which is
possible to day) is for you to just feed submitted files that you
batch-download from Relate to nbgrader.
So, in short, it's definitely in the plan, and it'll happen sooner if
you can find a way to contribute dev time. :)
(cc'ing the Relate list)
i am trying to create an exam ticket but I am not able to, under the
participation column i am not sure what to add.
I tried adding user names, my own name or the roles but it's not working.
Can you tell me what I am supposed to add?
It will be helpful because i am doing this project, to creating contents.
where can I control pagination for the flows? if I want to display 10 pages
in a single flow, i have 20 questions which i want to display but i want to
show only 1-10 on display, rest can be accessed when you click next button.
Based on feedback from Luke, it's now possible to write flows with a
little less clutter:
(1) If you only have a single page group in your flow, you can now skip
mentioning it, and just specify 'pages:' in the root, like this:
/!\ Do not change existing flows in this manner if they contain graded
student input. Unless your group was called 'main', your pages will have
different IDs after the change, and it will look to your students as
though their input is gone.
(2) YAML is now processed through Jinja by default. None of the
"[JINJA]"/"[/JINJA]" markers are needed any more.
This feature is a bit more complicated than it seems--but for the most
part, I think it does what it needs to. The reason for the complication
is that Jinja can mess up the indentation, which YAML relies on for
document structure. To avoid this, block literals, i.e. these things:
are not processed through (the first round of) Jinja. They can (of
course) be the result of a Jinja expansion, but Jinja directives within
them are ignored by (the first round of) Jinja.
*If* the block literal contains Markdown, then it (with the indentation
removed) is separately processed through Jinja.
A quick survey of your sites didn't reveal anything outrageously broken
by these changes, but if there is something, please let me know.
Room 4318 (Siebel Center), University of Illinois at Urbana-Champaign