Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add an option to control the maximum marginal degree in AIM workload construction

Aperta
  • Qualcosa non va?
#199 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@ArijanaBohr ci sta già lavorando.

Dal 30/9/2026.

  • #222 di @ArijanaBohr — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai-infra-agents, data, machine-learning

Direzione di ricerca

Look at the AIM workload construction code, likely in a file like aim.py or workload.py. The current fixed degree of 3 needs to be made a configurable parameter. Understand how max_marginal_size is used to filter marginals. The DPMM implementation linked shows the pattern. Add a degree parameter, integrate it with the existing filtering, and ensure it works with the two-column case from issue #196. Test by constructing workloads with different degree limits.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

AIM currently exposes max_marginal_size, which limits the size of marginal queries considered when constructing the workload. However, the maximum degree of the automatically constructed default workload is currently fixed at 3 and is not exposed as a configurable hyperparameter.

This is also related to the two-column case addressed in #196, where the number of available columns in the dataset necessarily results in a smaller degree than the current default workload construction.

In the DPMM implementation of AIM, these are exposed as two separate controls: degree (default 2) controls the maximum number of columns in a marginal, while max_cells constrains the size of the resulting marginal. max_cells therefore serves a similar purpose to max_marginal_size here.

It would be useful to expose the same distinction in this implementation. degree could determine the maximum number of columns considered together, while max_marginal_size could continue to filter these marginals based on the size of their joint domain. For example, a degree-3 marginal over three binary columns has only 8 cells, whereas a degree-2 marginal over two high-cardinality columns may be much larger.

The choice of degree and max_marginal_size, and the interaction between them, is an interesting hyperparameter trade-off.

If this sounds useful, I’d be happy to implement it and submit a PR.

Lingua principale
Python
Stelle
32
Fork
13
Merge medio
1g 19h
PR unite (30g)
20

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di google/dpsynth

Tutte le issue di google/dpsynth

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.