probcomp/bayeslite
View on GitHubmore expressive modelling constraints (e.g.: expected_lifetime > 0)
Open
#100 opened on Aug 3, 2015
2 comments (2 comments)0 reactions (0 reactions)0 assignees (0 assignees)Python915 stars (915 stars)63 forks (63 forks)batch import
help wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- python
- Domain
- datamachine learning
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 5
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- Bayesian statisticsPythonBayesDB internals
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 10
- Research direction
- The issue lacks a detailed description. A newcomer should first read the existing comments (if any) to understand the desired constraints. Then, explore the bayeslite codebase, particularly the constraint definition and parsing modules (e.g., bql parser, model expression). Investigate how current constraints like 'UNIQUE' or 'NOT NULL' are implemented. Finally, open a discussion with maintainers to clarify the syntax and semantics for new constraints such as 'expected lifetime > 0'.