Bandit Learning in Matching Markets: Utilitarian and Rawlsian Perspectives

Hadi Hosseini, Duohan Zhang
11/30/2024
cs.LGcs.GT

No confident code implementation found for this paper.

Abstract

Two-sided matching markets have demonstrated significant impact in many real-world applications, including school choice, medical residency placement, electric vehicle charging, ride sharing, and recommender systems. However, traditional models often assume that preferences are known, which is not always the case in modern markets, where preferences are unknown and must be learned. For example, a company may not know its preference over all job applicants a priori in online markets. Recent research has modeled matching markets as multi-armed bandit (MAB) problem and primarily focused on optimizing matching for one side of the market, while often resulting in a pessimal solution for the other side. In this paper, we adopt a welfarist approach for both sides of the market, focusing on two metrics: (1) Utilitarian welfare and (2) Rawlsian welfare, while maintaining market stability. For these metrics, we propose algorithms based on epoch Explore-Then-Commit (ETC) and analyze their regret bounds. Finally, we conduct simulated experiments to evaluate both welfare and market stability.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{hosseini2024bandit,
  title  = {Bandit Learning in Matching Markets: Utilitarian and Rawlsian Perspectives},
  author = {Hadi Hosseini and Duohan Zhang},
  year   = {2024},
  eprint = {2412.00301},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2412.00301v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2412.00301.svg)](https://codeofpaper.com/paper/2412.00301)

Discussion