# Qumín: from a bundle of scripts to a scientific toolkit

Sacha Beniamine, Jules Bouton

## ► To cite this version:

Sacha Beniamine, Jules Bouton. Qumín: from a bundle of scripts to a scientific toolkit. Journées scientifiques du réseau thématique LIFT2 - linguistique informatique, formelle et de terrain, Oct 2025, Paris, France. hal-05320339

HAL Id: hal-05320339

https://u-paris.hal.science/hal-05320339v1

Submitted on 20 Oct 2025

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>
## Introduction

A Python package for **typology** and **quantitative morphology**.

DOI 10.5281/zenodo.15008373

## For linguists

### 1. Morphological analogies

<figure><img src="image_2.png" /></figure>

An algorithm inspired by Albright's MGL (2003, 2006), see Beniamine (2018).

### 2. Predictability measures

<figure><img src="image_3.png" /></figure>

Using paradigm entropy as a measure of uncertainty (Ackerman et al., 2009), see Bonami and Beniamine (2016).

### 3. Inflection classes

<figure><img src="image_4.png" /></figure>

Lattices of inflection classes (Beniamine, 2021)

<figure><img src="image_5.png" /></figure>

Macroclasses (Beniamine et al., 2018)

<figure><img src="image_6.png" /></figure>

# Qumín: from a bundle of scripts to a scientific toolkit

<figure><img src="image_7.png" /></figure>

## Development history

<figure><img src="image_8.png" /></figure>

## Future plans

### Ask us about:

* How **Paralex+Qumin** enables large scale typology

* Improving **analogical patterns**

* New **complexity measures**

* The balance between **maintenance & new projects**

* Issues stemming from **software reuse** beyond its original design

<figure><img src="image_9.png" /></figure>

<figure><img src="image_10.png" /></figure>