Skip to main content

MILP-based scheduling for graduate visit days

Project description

Graduate Visit Scheduler

Docs Latest Docs Stable CI codecov Open In Colab

MILP-based scheduling utilities for graduate visit days. Created by Alex Dowling and Jeff Kantor at the University of Notre Dame.

Motivation

Most chemical engineering graduate programs in the U.S. host admitted or prospective students for a visit or open house. A core part of those events is one-on-one or small-group meetings with individual faculty members. Building a fair, feasible schedule is challenging: faculty availability, room locations, and student preferences must all be respected simultaneously.

This package is the meeting scheduler used by Notre Dame Chemical and Biomolecular Engineering, released as a general-purpose, open-source tool. Under the hood, it formulates a mixed-integer linear program (MILP) in Pyomo, solves it with a standard solver, visualizes the results, and can export customized student schedules to DOCX.

Data Gathering

Each visitor is asked to rank up to four faculty members for meetings and to choose up to two topic areas within the department. Likewise, faculty are asked to provide any afternoon meeting conflicts. This information is used to generate three key input files:

  • A faculty catalog YAML file (names, buildings, rooms, areas, status, and optional aliases).
  • A run configuration YAML file (time slots by building, breaks, area weights, and any faculty availability constraints).
  • A visitor preferences CSV file.

Research areas are department-specific. In the included example data, they are represented as simple labels such as Area1 and Area2, but you can define any set of areas in your faculty catalog.

What It Produces

  • An optimal assignment of visitors to faculty across time slots.
  • Visual summaries (plots) of the resulting schedule.
  • Optional DOCX exports with individualized visitor schedules.

Install

pip install grad-visitor-scheduler

Solver setup:

  • HiGHS is installed by default via the highspy dependency.
  • To use CBC, install the solver binary with conda:
conda install -c conda-forge coincbc

CI and Coverage

GitHub Actions runs the test suite on pushes to main and on pull requests targeting main. Coverage is uploaded to Codecov from the Python 3.11 job. For this public repository, coverage upload uses GitHub OIDC (no CODECOV_TOKEN secret required).

Automated PyPI Releases

Releases are tag-driven via GitHub Actions:

  • Push a semantic version tag like v0.2.0.
  • Workflow .github/workflows/release.yml runs tests, builds sdist/wheel, and checks package metadata.
  • Package is published to TestPyPI first.
  • CI performs a smoke install of that exact tagged version from TestPyPI.
  • If smoke install passes, CI publishes the same artifact to PyPI.

Publishing uses PyPI Trusted Publishing (OIDC), so no API token secret is required. Configure both PyPI and TestPyPI trusted publishers to point to this repository and the release.yml workflow file. Detailed release instructions are in docs/releasing.md.

Manual release workflow runs are also supported (workflow_dispatch):

  • target=testpypi: build, publish to TestPyPI, smoke install, stop.
  • target=pypi: run the full pipeline (TestPyPI + smoke + PyPI publish).
  • Optional version input lets smoke install pin a specific version.

Quickstart

from pathlib import Path
from grad_visit_scheduler import scheduler_from_configs, Mode, Solver

root = Path("examples")

s = scheduler_from_configs(
    root / "faculty_example.yaml",
    root / "config_basic.yaml",
    root / "data_fake_visitors.csv",
    mode=Mode.NO_OFFSET,
    solver=Solver.HIGHS,
)

s.schedule_visitors(
    group_penalty=0.1,
    min_visitors=0,
    max_visitors=4,
    min_faculty=1,
    max_group=2,
    enforce_breaks=True,
    tee=False,
    run_name="demo",
)

if s.has_feasible_solution():
    s.show_visitor_schedule(save_files=True)

Note: the examples/ folder referenced above is included in the repository, but it is not packaged on PyPI. If you installed from PyPI, clone the repo to access the example files.

Buildings

Notre Dame CBE is split across two buildings (Nieuwland Science Hall and McCourtney Hall) separated by about a 7-minute walk. A key aspect of the scheduler is to ensure that any visitor who needs to move buildings does so during their break slot. A typical schedule uses six meeting slots, and each visitor and faculty member gets at least one middle-slot break.

The run config defines exactly two buildings, and building_order declares which one is Building A versus Building B. Mode controls how movement between buildings is constrained:

  • Mode.BUILDING_A_FIRST: visitor starts in Building A, then may move to B
  • Mode.BUILDING_B_FIRST: visitor starts in Building B, then may move to A
  • Mode.NO_OFFSET: visitor may move either direction, but only with an empty slot

Refine the Schedule

The solver exposes several tunable parameters on schedule_visitors to refine the schedule:

  • group_penalty: penalize group meetings to bias toward one-on-one meetings; higher values discourage multi-visitor meetings.
  • min_visitors: minimum number of visitors each available faculty member must meet.
  • max_visitors: maximum number of visitors each faculty member may meet.
  • min_faculty: minimum number of faculty each visitor must meet.
  • max_group: maximum size of a meeting group at any time slot.
  • enforce_breaks: force breaks for visitors and faculty during the configured break window.
  • tee: print solver output for debugging.
  • run_name: label used when saving plots/exports.

To generate multiple ranked schedules, use no-good cuts:

top = s.schedule_visitors_top_n(n_solutions=3, enforce_breaks=True)
report = top.summarize(ranks_to_plot=(1, 2), show_solution_rank=True)
print(report["summary"])
print(report["compact"])

Export DOCX

You can optionally export customized visitor schedules to a DOCX file. This facilitates easy copy/paste into individualized agendas for each visitor.

from grad_visit_scheduler import export_visitor_docx

export_visitor_docx(s, "visitor_schedule.docx")

License

This software is released under the BSD-3-Clause license. Please adapt it to your needs and share.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

grad_visitor_scheduler-0.2.0.tar.gz (37.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

grad_visitor_scheduler-0.2.0-py3-none-any.whl (25.3 kB view details)

Uploaded Python 3

File details

Details for the file grad_visitor_scheduler-0.2.0.tar.gz.

File metadata

  • Download URL: grad_visitor_scheduler-0.2.0.tar.gz
  • Upload date:
  • Size: 37.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for grad_visitor_scheduler-0.2.0.tar.gz
Algorithm Hash digest
SHA256 a1d5ba159a8bcc86a0b88883a8864e664887ad57ff46de5b99a87d510df72025
MD5 dc07c50fe104de13dcf670c80a974aee
BLAKE2b-256 941e8ca6f68ef8fcd1e8442709ca51cdd186bbeef0cff0a3ae463c8f7bdfe307

See more details on using hashes here.

Provenance

The following attestation bundles were made for grad_visitor_scheduler-0.2.0.tar.gz:

Publisher: release.yml on dowlinglab/grad-visit-scheduler

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file grad_visitor_scheduler-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for grad_visitor_scheduler-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 966c121f53b49e483884ddda21b4d8a33e16acb7f2f823ecb63afbbca0473b8c
MD5 58863863af962445ae32671f415b9af8
BLAKE2b-256 ef46ad2607bb2f7f994d55ab640407e53a63001842f2658c02d6cc997720fe22

See more details on using hashes here.

Provenance

The following attestation bundles were made for grad_visitor_scheduler-0.2.0-py3-none-any.whl:

Publisher: release.yml on dowlinglab/grad-visit-scheduler

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page