Assessment framework doc for 2026/27

.gitignore

@@ -89,3 +89,321 @@ Gemfile.lock
 polynomials.svg
 contents/
 .jupyterlite.doit.db
+
+.vscode
+
+# LATEX
+# Created by https://www.toptal.com/developers/gitignore/api/latex
+# Edit at https://www.toptal.com/developers/gitignore?templates=latex
+
+### LaTeX ###
+## Core latex/pdflatex auxiliary files:
+*.aux
+*.lof
+*.log
+*.lot
+*.fls
+*.out
+*.toc
+*.fmt
+*.fot
+*.cb
+*.cb2
+.*.lb
+
+## Intermediate documents:
+*.dvi
+*.xdv
+*-converted-to.*
+# these rules might exclude image files for figures etc.
+# *.ps
+# *.eps
+# *.pdf
+
+## Generated if empty string is given at "Please type another file name for output:"
+.pdf
+
+## Bibliography auxiliary files (bibtex/biblatex/biber):
+*.bbl
+*.bcf
+*.blg
+*-blx.aux
+*-blx.bib
+*.run.xml
+
+## Build tool auxiliary files:
+*.fdb_latexmk
+*.synctex
+*.synctex(busy)
+*.synctex.gz
+*.synctex.gz(busy)
+*.pdfsync
+
+## Build tool directories for auxiliary files
+# latexrun
+latex.out/
+
+## Auxiliary and intermediate files from other packages:
+# algorithms
+*.alg
+*.loa
+
+# achemso
+acs-*.bib
+
+# amsthm
+*.thm
+
+# beamer
+*.nav
+*.pre
+*.snm
+*.vrb
+
+# changes
+*.soc
+
+# comment
+*.cut
+
+# cprotect
+*.cpt
+
+# elsarticle (documentclass of Elsevier journals)
+*.spl
+
+# endnotes
+*.ent
+
+# fixme
+*.lox
+
+# feynmf/feynmp
+*.mf
+*.mp
+*.t[1-9]
+*.t[1-9][0-9]
+*.tfm
+
+#(r)(e)ledmac/(r)(e)ledpar
+*.end
+*.?end
+*.[1-9]
+*.[1-9][0-9]
+*.[1-9][0-9][0-9]
+*.[1-9]R
+*.[1-9][0-9]R
+*.[1-9][0-9][0-9]R
+*.eledsec[1-9]
+*.eledsec[1-9]R
+*.eledsec[1-9][0-9]
+*.eledsec[1-9][0-9]R
+*.eledsec[1-9][0-9][0-9]
+*.eledsec[1-9][0-9][0-9]R
+
+# glossaries
+*.acn
+*.acr
+*.glg
+*.glo
+*.gls
+*.glsdefs
+*.lzo
+*.lzs
+*.slg
+*.slo
+*.sls
+
+# uncomment this for glossaries-extra (will ignore makeindex's style files!)
+# *.ist
+
+# gnuplot
+*.gnuplot
+*.table
+
+# gnuplottex
+*-gnuplottex-*
+
+# gregoriotex
+*.gaux
+*.glog
+*.gtex
+
+# htlatex
+*.4ct
+*.4tc
+*.idv
+*.lg
+*.trc
+*.xref
+
+# hyperref
+*.brf
+
+# knitr
+*-concordance.tex
+# TODO Uncomment the next line if you use knitr and want to ignore its generated tikz files
+# *.tikz
+*-tikzDictionary
+
+# listings
+*.lol
+
+# luatexja-ruby
+*.ltjruby
+
+# makeidx
+*.idx
+*.ilg
+*.ind
+
+# minitoc
+*.maf
+*.mlf
+*.mlt
+*.mtc[0-9]*
+*.slf[0-9]*
+*.slt[0-9]*
+*.stc[0-9]*
+
+# minted
+_minted*
+*.pyg
+
+# morewrites
+*.mw
+
+# newpax
+*.newpax
+
+# nomencl
+*.nlg
+*.nlo
+*.nls
+
+# pax
+*.pax
+
+# pdfpcnotes
+*.pdfpc
+
+# sagetex
+*.sagetex.sage
+*.sagetex.py
+*.sagetex.scmd
+
+# scrwfile
+*.wrt
+
+# svg
+svg-inkscape/
+
+# sympy
+*.sout
+*.sympy
+sympy-plots-for-*.tex/
+
+# pdfcomment
+*.upa
+*.upb
+
+# pythontex
+*.pytxcode
+pythontex-files-*/
+
+# tcolorbox
+*.listing
+
+# thmtools
+*.loe
+
+# TikZ & PGF
+*.dpth
+*.md5
+*.auxlock
+
+# titletoc
+*.ptc
+
+# todonotes
+*.tdo
+
+# vhistory
+*.hst
+*.ver
+
+# easy-todo
+*.lod
+
+# xcolor
+*.xcp
+
+# xmpincl
+*.xmpi
+
+# xindy
+*.xdy
+
+# xypic precompiled matrices and outlines
+*.xyc
+*.xyd
+
+# endfloat
+*.ttt
+*.fff
+
+# Latexian
+TSWLatexianTemp*
+
+## Editors:
+# WinEdt
+*.bak
+*.sav
+
+# Texpad
+.texpadtmp
+
+# LyX
+*.lyx~
+
+# Kile
+*.backup
+
+# gummi
+.*.swp
+
+# KBibTeX
+*~[0-9]*
+
+# TeXnicCenter
+*.tps
+
+# auto folder when using emacs and auctex
+./auto/*
+*.el
+
+# expex forward references with \gathertags
+*-tags.tex
+
+# standalone packages
+*.sta
+
+# Makeindex log files
+*.lpz
+
+# xwatermark package
+*.xwm
+
+# REVTeX puts footnotes in the bibliography by default, unless the nofootinbib
+# option is specified. Footnotes are the stored in a file with suffix Notes.bib.
+# Uncomment the next line to have this generated file ignored.
+#*Notes.bib
+
+### LaTeX Patch ###
+# LIPIcs / OASIcs
+*.vtc
+
+# glossaries
+*.glstex
+
+# End of https://www.toptal.com/developers/gitignore/api/latex

grade-calculation/coursework.tex

@@ -0,0 +1,52 @@
+
+\subsection{Group Coursework Component}
+
+\begin{itemize}
+  \item When: Term 1 (concurrent with classes and lectures). Vivas are planned for either before Christmas or the January assessment period, depending on where UCL's Christmas break falls.
+        \begin{itemize}
+          \item The coursework briefing / task document will be released as soon as it is ready.
+          \item You will be assigned your working groups in the week prior to reading week.
+          \item Note that group work will be baked in to the assignment tasks.
+                Even though you will have the full brief available to you before your are assigned your groups, you will not be able to attempt the majority of the tasks, though will be able to prepare ideas on implementation and design.
+        \end{itemize}
+  \item What: A group project requiring you to develop a piece of software in Python.
+  \item Number of submissions: 3
+        \begin{itemize}
+          \item Your group's codebase and project repository.
+          \item Your \href{https://app.ipac-app.education/website/}{IPAC peer-evaluation} review.
+          \item Your attendance and performance at the group viva.
+        \end{itemize}
+\end{itemize}
+
+The coursework component of the module runs concurrently with the lectures and classes, in term 1.
+Partway through the year, you will be assigned to a group of 4-5 members, and will be asked to develop a piece of software in Python as detailed in the assignment's document.
+You will be expected to develop this software collaboratively with your group, and engage in good development practices as you have seen and learnt from the lectures and course notes.
+
+Your group will submit the final state of your project's repository via moodle.
+An automated marker will then examine your repository against a marking rubric (made public to you in the briefing document) to determine how many marks your group will be awarded, based on whether your project meets the specifications set out by the briefing document.
+This will give you a score $\codebaseGrade$, awarded to all members of your group, reflecting how well you addressed the functionality requirements of the assignment.
+$\codebaseGrade$ will have a maximum value of 50\% (of the overall component's marks).
+
+After the project repository is submitted, each member of your group will also submit an IPAC peer-evaluation, where you will provide feedback to your group members and discuss how well you felt the group worked together.
+The IPAC will then calculate an individual weight for you $\ipacWeight$, which is typically in the range $0.8$-$1.2$.
+Note that your IPAC weight may be different from that of your group-mates, but your group's weights will always average out to 1.
+
+Finally, your group will be required to attend an in-person viva.
+In this viva you will be asked a series of questions about the work you submitted, your contributions to the software development workflow that your group undertook, and reflect on alternative approaches or generalisations that you considered.
+In particular, in your group viva you will be expected to be able to:
+
+\begin{itemize}
+  \item Highlight and discuss any contributions you made to design decisions during the project; such as your contribution to issue discussions, or suggestions during your pull-request reviews.
+  \item Explain your contributions to the codebase through any pull-requests you authored, as well as evaluate and discuss alternatives that you (or your group) considered.
+  \item Justify your software development practices, and any contributions to the repository that reflect this.
+\end{itemize}
+
+You will be given an individual score $\vivaGrade$ from your performance in the viva, which will have a maximum value of 50\% (of the overall component's marks).
+
+Your grade for the coursework component $\courseworkGrade$ is then calculated as
+
+\begin{align*}
+  \courseworkGrade = (\codebaseGrade \times \ipacWeight) + \vivaGrade,
+\end{align*}
+
+being capped at $100\%$ in the event of overflow.