Distribution
Declare the probability object: Gaussian, categorical, mixture, HMM, composite record, grammar, or custom family.
Concepts
mixle centers on distribution objects, estimator objects, and capabilities exposed by fitted models. Use this page as the conceptual reference before moving into code examples.
Core idea
A model shape is declared as a probability object or matching estimator. Leaves compose into records, mixtures, HMMs, grammars, and task models. Fitting, scoring, sampling, serialization, and enumeration follow that structure instead of requiring unrelated APIs.
Lifecycle
Declare the probability object: Gaussian, categorical, mixture, HMM, composite record, grammar, or custom family.
Fit the same structure by closed form, EM, MAP, hierarchical, state-space, VI, MCMC, or an explicit route.
Keep heterogeneous fields in a structured representation instead of forcing every workflow through one flat matrix.
For discrete structured models, walk support in probability order and ask rank or seek questions directly.
Evaluate, explain, calibrate, save, restore, and serve the fitted object without switching abstractions.
Scope
mixle is not meant to replace every numerical, Bayesian, or machine-learning library. It is most useful when model structure is part of the problem.
mixle-pde and serving workflows in mixle-mlops.Modules
Extras
numbaJIT hot pathstorchGPU and autograd enginejaxXLA and NumPyro backendsparkdistributed estimationdaskcluster executionmpiparallel runsdatapandas, Arrow, SQL, Mongo, Hadoopsympysymbolic exportumapmodel-based embeddingsPackage facts
The public package uses the PyPI distribution name mixle and the import name
mixle. The source repository, docs, examples, and issue tracker are open.