Digital education

CS411 - https://moodle.epfl.ch/course/view.php?id=14248
Our project hosted at https://neuralnet.stergios.ch

Project - Kyoto, baby

AI-assisted learning for neural networks.

Team Members:

Core idea:

Learning goals:

Students will be able to implement neural network concepts.

Research question:

Task Analysis:

https://playground.tensorflow.org/ clone with specific targets.

Recruitment plan:

We record (everything, but we focus on):

Next Meeting:

Programming Neural Networks for Novice Learners

Project Overview

Project concept refined during team discussion (Group: Kyoto baby). Rather than abandoning neural networks, the project will investigate programming of neural networks tailored for novice/beginner programmers (using neural networks as the concrete applied use case).


Core Concept & Pedagogical Approach


Project Timeline & Milestone Roadmap

Target / Date Objective Details
This Week 1-Page Proposal Draft Outline hypotheses, independent/dependent variables, and study protocol for Mauro & Dominique (TA).
Lunch Today Recruitment Alignment Stergios asking Yash to contact 2nd-year Bachelor students. Master's students excluded (avoiding high baseline expertise).
October 8 (Milestone 1) Official Idea Validation Finalize recruitment forms, validate participant pipeline (~20 novices), and secure TA approval.
By Week 8 (Milestone 2) Data Collection & Initial Findings Complete ~20 participant sessions (~30 total testing hours, ~2 full days per researcher). Have preliminary results synthesized.
Milestone 3 Final Analysis & Reporting ~1.5 months dedicated to deep analytics, drawing conclusions, and drafting the project paper/Kyoto submission.

Action Items Checklist


Meeting Notes: Experimental Design & UI Specifications


Implementation Scope & Team Workstream Division


Target Publication: IJCAI 2027 (Special Track on Human-Centred AI)


Study Design Evolution & Proposal (Discussion Update - Isna)


Team Discussion: Topic Selection & Experimental Feasibility (Meeting Notes)

DigitalED | 3D Gradient Descent Gamified Lab

DigitalED | 3D Gradient Descent Gamified Lab

An interactive, gamified 3D and 2D laboratory designed to teach the mathematics and intuition of Gradient Descent algorithms in machine learning. Built as a full-stack Django application with Three.js WebGL graphics and 100% client-side computation.


🚀 Key Features

  1. Split-Screen Ergonomic Layout:

    • Narrow Left Column (≤ 25% max width): Sleek glassmorphic control center with gamification scoreboard, mission challenges, surface selector, hyperparameter sliders, optimizer switches, and step controls.
    • 3D Visualizer Canvas (75% right area): Full-viewport WebGL canvas with real-time camera controls, dynamic height colormaps, animated ball physics, glowing trajectory path ribbons, and vector field quiver plots.
  2. Gamified Educational Missions:

    • Level 1: The Parabolic Valley: Smooth convex bowl $f(x, y) = 0.5(x^2 + 2y^2)$. Tune learning rate $\alpha$ to reach the target in minimum steps.
    • Level 2: Saddle Point Pass: Hyperbolic paraboloid $f(x, y) = 0.4(x^2 - y^2)$. Demonstrates how standard GD stalls at saddle plateaus and how Momentum or Adam accelerates past.
    • Level 3: Rosenbrock Banana Trench: The famous non-convex ravine $f(x, y) = 0.08((1-x)^2 + 10(y-x^2)^2)$. Demonstrates wall oscillations vs smooth ravine navigation.
    • Level 4: Multi-Modal Peaks (Himmelblau): Landscapes with multiple local and global minima. Teaches how stochastic mini-batch noise escapes shallow basins.
    • Level 5: Rastrigin Ripple Field: Dozens of ripple barriers where pure GD gets trapped and momentum glides through.
    • 🎲 Procedural Random Landscapes: Generates random 3D surfaces dynamically.
  3. Hover Educational Explanations:

    • Hovering over any parameter reveals rich educational cards with the mathematical equation, core concept intuition, physical analogies (e.g. friction, ball inertia, stride length), and "Too Low" vs "Too High" consequences.
  4. 3D Perspective ⇄ 2D Contour Map Toggle:

    • Seamlessly switch between the 3D perspective surface and an orthographic top-down 2D contour map with isobar level curves and gradient direction vectors.
  5. Ball Drop Physics & Interactive Surface Click:

    • The ball drops from the sky onto the surface, bouncing on impact and rolling along the exact gradient descent trajectory.
    • Click anywhere on the 3D surface mesh to drop the ball at that exact coordinate.
  6. 100% Client-Side Compute:

    • All surface functions, analytical and numerical gradients ($\partial f/\partial x, \partial f/\partial y$), optimizer updates (GD, Polyak Momentum, RMSprop, Adam), stochastic noise, and WebGL rendering run completely in the browser for instant, lag-free 60fps interaction.
  7. Invisible Unique Session Tracking & Telemetry:

    • Every visitor is automatically assigned a unique persistent UUID via Django middleware.
    • User inputs, hyperparameter configurations, and simulation outcomes are asynchronously posted to /api/record-input/ and recorded in SQLite database models UserSession and UserInteraction.

🛠️ Requirements & Setup

Environment Prerequisites

As per local rule, the virtual environment is installed locally:

Installation

# If creating a fresh local environment:
python3 -m venv ~/.venvs/digitalED_gd_3d
source ~/.venvs/digitalED_gd_3d/bin/activate

# Install dependencies:
pip install -r requirements.txt

Running with Django Dev Server

python manage.py migrate
python manage.py runserver 127.0.0.1:8000

Then open http://127.0.0.1:8000 in your web browser.

Running with uWSGI (Production Mode)

A production-ready uwsgi.ini is located at the project root:

uwsgi --ini uwsgi.ini

This launches a master process with 4 worker threads serving the application and static files at http://0.0.0.0:8000.


📂 Project Architecture

digitalED_gradient_descent_3d/
├── requirements.txt            # Project dependencies (Django, uWSGI, etc.)
├── uwsgi.ini                   # Production uWSGI configuration at root
├── manage.py                   # Django management script
├── config/
│   ├── settings.py             # Settings, DB config, middleware, staticfiles
│   ├── urls.py                 # Root URL configuration
│   └── wsgi.py                 # WSGI entrypoint
├── visualizer/
│   ├── models.py               # UserSession & UserInteraction models
│   ├── middleware.py           # Invisible session tracking middleware
│   ├── views.py                # Views: index, record_input API, session_stats API
│   ├── urls.py                 # App URLs
│   └── admin.py                # Django Admin integration
├── templates/
│   └── visualizer/
│       └── index.html          # Semantic HTML5 layout, HUD, popovers
└── static/
    ├── css/
    │   └── styles.css          # Dark glassmorphism, 25% sidebar layout, HUD
    └── js/
        ├── surfaces.js         # Mathematical surfaces & random procedural generator
        ├── optimizers.js       # Client-side GD, Momentum, RMSprop, Adam solvers
        ├── visualizer3d.js     # Three.js 3D/2D renderer, ball drop & trajectory
        ├── audio.js            # Procedural Web Audio API sound synthesizer
        └── app.js              # Coordinator, UI binding & telemetry reporting

Site: gradient.stergios.ch

The Name of the Title Is Hope

[!NOTE] Overleaf Project: git.overleaf.com/6ae05e2e72446c974da5a114
Last Synced: 2026-11-03 08:01:50 (via PA Git Sync)
Source File: sigconf-authordraft.tex

The Name of the Title Is Hope

Authors: Ben Trovato, G.K.M. Tobin, Lars Th{\o, Valerie B'eranger, Aparna Patel, Huifen Chan, Charles Palmer, John Smith, Julius P. Kumquat, Brooke Aster, David Mehldau

[!ABSTRACT] A clear and well-documented \LaTeX\ document is presented as an article formatted for publication by ACM in a conference proceedings or journal publication. Based on the ``acmart'' document class, this article presents and explains many of the common variations, as well as many of the formatting elements an author may use in the preparation of the documentation of their work.


\authornote{Both authors contributed equally to this research.}

\orcid{1234-5678-9012}

\correspondingauthor \authornotemark[1]

\city{Dublin} \state{Ohio} \country{USA} }

rv{"a}ld} rv{"a}ld Group} \city{Hekla} \country{Iceland}}

\city{Rocquencourt} \country{France} }

\city{Doimukh} \state{Arunachal Pradesh} \country{India}}

\city{Haidian Qu} \state{Beijing Shi} \country{China}}

\city{San Antonio} \state{Texas} \country{USA}}

rv{"a}ld Group} \city{Hekla} \country{Iceland}}

\correspondingauthor

\city{New York} \country{USA}}

\renewcommand{\shortauthors}{Trovato et al.}

\begin{CCSXML} <concept_id>00000000.0000000.0000000</concept_id> <concept_desc>Do Not Use This Code, Generate the Correct Terms for Your Paper</concept_desc> <concept_significance>500</concept_significance> <concept_id>00000000.00000000.00000000</concept_id> <concept_desc>Do Not Use This Code, Generate the Correct Terms for Your Paper</concept_desc> <concept_significance>300</concept_significance> <concept_id>00000000.00000000.00000000</concept_id> <concept_desc>Do Not Use This Code, Generate the Correct Terms for Your Paper</concept_desc> <concept_significance>100</concept_significance> <concept_id>00000000.00000000.00000000</concept_id> <concept_desc>Do Not Use This Code, Generate the Correct Terms for Your Paper</concept_desc> <concept_significance>100</concept_significance> \end{CCSXML}

\ccsdesc[500]{Do Not Use This CodeGenerate the Correct Terms for Your Paper} \ccsdesc[300]{Do Not Use This CodeGenerate the Correct Terms for Your Paper} \ccsdesc{Do Not Use This CodeGenerate the Correct Terms for Your Paper} \ccsdesc[100]{Do Not Use This CodeGenerate the Correct Terms for Your Paper}

\keywords{Do, Not, Use, This, Code, Put, the, Correct, Terms, for, Your, Paper}

\begin{teaserfigure} \includegraphics[width=\textwidth]{sampleteaser} \caption{Seattle Mariners at Spring Training, 2010.} \Description{Enjoying the baseball game from the third-base seats. Ichiro Suzuki preparing to bat.} \label{fig:teaser} \end{teaserfigure}

\received{20 February 2007} \received[revised]{12 March 2009} \received[accepted]{5 June 2009}

Introduction

ACM's consolidated article template, introduced in 2017, provides a consistent \LaTeX\ style for use across ACM publications, and incorporates accessibility and metadata-extraction functionality necessary for future Digital Library endeavors. Numerous ACM and SIG-specific \LaTeX\ templates have been examined, and their unique features incorporated into this single new template.

If you are new to publishing with ACM, this document is a valuable guide to the process of preparing your work for publication. If you have published with ACM before, this document provides insight and instruction into more recent changes to the article template.

The \verb|acmart|'' document class can be used to prepare articles for any ACM publication --- conference or journal, and for any stage of publication, from review to final camera-ready'' copy, to the author's own version, with {\itshape very} few changes to the source.

Template Overview

As noted in the introduction, the \verb|acmart|'' document class can be used to prepare many different kinds of documentation --- a double-anonymous initial submission of a full-length technical paper, a two-page SIGGRAPH Emerging Technologies abstract, a camera-ready'' journal article, a SIGCHI Extended Abstract, and more --- all by selecting the appropriate {\itshape template style} and {\itshape template parameters}.

This document will explain the major features of the document class. For further information, the {\itshape \LaTeX\ User's Guide} is available from https://www.acm.org/publications/proceedings-template.

Template Styles

The primary parameter given to the ``\verb|acmart|'' document class is the {\itshape template style} which corresponds to the kind of publication or SIG publishing the work. This parameter is enclosed in square brackets and is a part of the {\verb|documentclass|} command: \begin{verbatim} \documentclass[STYLE]{acmart} \end{verbatim}

Journals use one of three template styles. All but three ACM journals use the {\verb|acmsmall|} template style:

The majority of conference proceedings documentation will use the {\verb|acmconf|} template style.

Template Parameters

In addition to specifying the {\itshape template style} to be used in formatting your work, there are a number of {\itshape template parameters} which modify some part of the applied template style. A complete list of these parameters can be found in the {\itshape \LaTeX\ User's Guide.}

Frequently-used parameters, or combinations of parameters, include:

This document uses the following string as the first command in the source file: \begin{verbatim} \documentclass[sigconf,authordraft]{acmart} \end{verbatim}

Modifications

Modifying the template --- including but not limited to: adjusting margins, typeface sizes, line spacing, paragraph and list definitions, and the use of the \verb|\vspace| command to manually adjust the vertical spacing between elements of your work --- is not allowed.

{\bfseries Your document will be returned to you for revision if modifications are discovered.}

Typefaces

The \verb|acmart|'' document class requires the use of the Libertine'' typeface family. Your \TeX\ installation should include this set of packages. Please do not substitute other typefaces. The \verb|lmodern|'' and \verb|ltimes|'' packages should not be used, as they will override the built-in typeface families.

Title Information

The title of your work should use capital letters appropriately - https://capitalizemytitle.com/ has useful rules for capitalization. Use the {\verb|title|} command to define the title of your work. If your work has a subtitle, define it with the {\verb|subtitle|} command. Do not insert line breaks in your title.

If your title is lengthy, you must define a short version to be used in the page headers, to prevent overlapping text. The \verb|title| command has a ``short title'' parameter: \begin{verbatim}

\end{verbatim}

Authors and Affiliations

Each author must be defined separately for accurate metadata identification. As an exception, multiple authors may share one affiliation. Authors' names should not be abbreviated; use full first names wherever possible. Include authors' e-mail addresses whenever possible.

Grouping authors' names or e-mail addresses, or providing an ``e-mail alias,'' as shown below, is not acceptable: \begin{verbatim}

\end{verbatim}

The \verb|authornote| and \verb|authornotemark| commands allow a note to apply to multiple authors --- for example, if the first two authors of an article contributed equally to the work.

If your author list is lengthy, you must define a shortened version of the list of authors to be used in the page headers, to prevent overlapping text. The following command should be placed just after the last \verb|\author{}| definition: \begin{verbatim} \renewcommand{\shortauthors}{McCartney, et al.} \end{verbatim} Omitting this command will force the use of a concatenated list of all of the authors' names, which may result in overlapping text in the page headers.

The article template's documentation, available at https://www.acm.org/publications/proceedings-template, has a complete explanation of these commands and tips for their effective use.

Note that authors' addresses are mandatory for journal articles.

Rights Information

Authors of any work published by ACM will need to complete a rights form. Depending on the kind of work, and the rights management choice made by the author, this may be copyright transfer, permission, license, or an OA (open access) agreement.

Regardless of the rights management choice, the author will receive a copy of the completed rights form once it has been submitted. This form contains \LaTeX\ commands that must be copied into the source document. When the document source is compiled, these commands and their parameters add formatted text to several areas of the final document:

Rights information is unique to the work; if you are preparing several works for an event, make sure to use the correct set of commands with each of the works.

The ACM Reference Format text is required for all articles over one page in length, and is optional for one-page articles (abstracts).

CCS Concepts and User-Defined Keywords

Two elements of the ``acmart'' document class provide powerful taxonomic tools for you to help readers find your work in an online search.

The ACM Computing Classification System --- https://www.acm.org/publications/class-2012 --- is a set of classifiers and concepts that describe the computing discipline. Authors can select entries from this classification system, via https://dl.acm.org/ccs/ccs.cfm, and generate the commands to be included in the \LaTeX\ source.

User-defined keywords are a comma-separated list of words and phrases of the authors' choosing, providing a more flexible way of describing the research being presented.

CCS concepts and user-defined keywords are required for for all articles over two pages in length, and are optional for one- and two-page articles (or abstracts).

Sectioning Commands

Your work should use standard \LaTeX\ sectioning commands: \verb|\section|, \verb|\subsection|, \verb|\subsubsection|, \verb|\paragraph|, and \verb|\subparagraph|. The sectioning levels up to \verb|\subsubsection| should be numbered; do not remove the numbering from the commands.

Simulating a sectioning command by setting the first word or words of a paragraph in boldface or italicized text is {\bfseries not allowed.}

Below are examples of sectioning commands.

Subsection

\label{sec:subsection}

This is a subsection.

Subsubsection

\label{sec:subsubsection}

This is a subsubsection.

Paragraph:

This is a paragraph.

\subparagraph{Subparagraph}

This is a subparagraph.

Tables

The \verb|acmart|'' document class includes the \verb|booktabs|'' package --- https://ctan.org/pkg/booktabs --- for preparing high-quality tables.

Table captions are placed {\itshape above} the table.

Because tables cannot be split across pages, the best placement for them is typically the top of the page nearest their initial cite. To ensure this proper ``floating'' placement of tables, use the environment table to enclose the table's contents and the table caption. The contents of the table itself must go in the tabular environment, to be aligned properly in rows and columns, with the desired horizontal and vertical rules. Again, detailed instructions on tabular material are found in the \LaTeX\ User's Guide.

Immediately following this sentence is the point at which Table [tab:freq] is included in the input file; compare the placement of the table here with the table in the printed output of this document.

\begin{table} \caption{Frequency of Special Characters} \label{tab:freq} \begin{tabular}{ccl} \toprule Non-English or Math&Frequency&Comments\ \midrule \O & 1 in 1,000& For Swedish names\ $\pi$ & 1 in 5& Common in math\ $ & 4 in 5 & Used in business\ $\Psi^2_1$ & 1 in 40,000& Unexplained usage\ \bottomrule \end{tabular} \end{table}

To set a wider table, which takes up the whole width of the page's live area, use the environment table* to enclose the table's contents and the table caption. As with a single-column table, this wide table will ``float'' to a location deemed more desirable. Immediately following this sentence is the point at which Table [tab:commands] is included in the input file; again, it is instructive to compare the placement of the table here with the table in the printed output of this document.

\begin{table*} \caption{Some Typical Commands} \label{tab:commands} \begin{tabular}{ccl} \toprule Command &A Number & Comments\ \midrule {\char'134author} & 100& Author \ {\char'134table}& 300 & For tables\ {\char'134table*}& 400& For wider tables\ \bottomrule \end{tabular} \end{table*}

Always use midrule to separate table header rows from data rows, and use it only for this purpose. This enables assistive technologies to recognise table headers and support their users in navigating tables more easily.

Math Equations

You may want to display math equations in three distinct styles: inline, numbered or non-numbered display. Each of the three are discussed in the next sections.

Inline (In-text) Equations

A formula that appears in the running text is called an inline or in-text formula. It is produced by the math environment, which can be invoked with the usual {\char'134begin,\ldots{\char'134}end} construction or with the short form $\,\ldots$. You can use any of the symbols and structures, from $\alpha$ to $\omega$, available in \LaTeX [Lamport:LaTeX]; this section will simply show a few examples of in-text equations in context. Notice how this equation: \begin{math} \lim_{n\rightarrow \infty}x=0 \end{math}, set here in in-line math style, looks slightly different when set in display style. (See next section).

Display Equations

A numbered display equation---one set off by vertical space from the text and centered horizontally---is produced by the equation environment. An unnumbered display equation is produced by the displaymath environment.

Again, in either environment, you can use any of the symbols and structures available in \LaTeX@; this section will just give a couple of examples of display equations in context. First, consider the equation, shown as an inline equation above: \begin{equation} \lim_{n\rightarrow \infty}x=0 \end{equation} Notice how it is formatted somewhat differently in the displaymath environment. Now, we'll enter an unnumbered equation: \begin{displaymath} \sum_{i=0}^{\infty} x + 1 \end{displaymath} and follow it with another numbered equation: \begin{equation} \sum_{i=0}^{\infty}x_i=\int_{0}^{\pi+2} f \end{equation} just to demonstrate \LaTeX's able handling of numbering.

Figures

The ``\verb|figure|'' environment should be used for figures. One or more images can be placed within a figure. If your figure contains third-party material, you must clearly identify it as such, as shown in the example below. \begin{figure}[h] \centering \includegraphics[width=\linewidth]{sample-franklin} \caption{1907 Franklin Model D roadster. Photograph by Harris & Ewing, Inc. [Public domain], via Wikimedia Commons. (https://goo.gl/VLCRBB).} \Description{A woman and a girl in white dresses sit in an open car.} \end{figure}

Your figures should contain a caption which describes the figure to the reader.

Figure captions are placed {\itshape below} the figure.

Every figure should also have a figure description unless it is purely decorative. These descriptions convey what’s in the image to someone who cannot see it. They are also used by search engine crawlers for indexing images, and when images cannot be loaded.

A figure description must be unformatted plain text less than 2000 characters long (including spaces). {\bfseries Figure descriptions should not repeat the figure caption – their purpose is to capture important information that is not already provided in the caption or the main text of the paper.} For figures that convey important and complex new information, a short text description may not be adequate. More complex alternative descriptions can be placed in an appendix and referenced in a short figure description. For example, provide a data table capturing the information in a bar chart, or a structured list representing a graph. For additional information regarding how best to write figure descriptions and why doing this is so important, please see https://www.acm.org/publications/taps/describing-figures/.

The ``Teaser Figure''

A ``teaser figure'' is an image, or set of images in one figure, that are placed after all author and affiliation information, and before the body of the article, spanning the page. If you wish to have such a figure in your article, place the command immediately before the \verb|| command: \begin{verbatim} \begin{teaserfigure} \includegraphics[width=\textwidth]{sampleteaser} \caption{figure caption} \Description{figure description} \end{teaserfigure} \end{verbatim}

Citations and Bibliographies

The use of \BibTeX\ for the preparation and formatting of one's references is strongly recommended. Authors' names should be complete --- use full first names (Donald E. Knuth'') not initials (D. E. Knuth'') --- and the salient identifying features of a reference should be included: title, year, volume, number, pages, article DOI, etc.

The bibliography is included in your source document with these two commands, placed just before the \verb|