Roman Lutz

Results 61 issues of Roman Lutz

It's sometimes useful to reference code block output in addition to produced images (using `figure`) or code lines (using `literalinclude`), so this change adds comments to the produced RST file...

I can reference code from a notebook using ``` .. literalinclude:: ../auto_examples/plot_myscript.py :start-after: [some-tag] :end-before: [another-tag] ``` and the resulting images using ``` .. figure:: ../auto_examples/images/sphx_glr_plot_myscript_001.png :target: ../auto_examples/plot_myscript.html ``` However,...

enhancement

## Description So far, we used the string `"noFlights"` to avoid providing an empty string that the route generation can't handle which is not ideal. Instead, this PR removes the...

## Description Box plots are so far only there in the binary classification case, but this PR adds a box plot for regression, too! It supports error, predicted y and...

This PR finally adds a user guide for `ThresholdOptimizer` which explains some of the pitfalls that users should be aware of when using this. If this reads like you shouldn't...

documentation

#### Describe the issue linked to the documentation Persisting metrics and loading them back into memory is often useful. We don't currently mention this anywhere but `fairlearn.metrics.MetricFrame` can be pickled...

help wanted
good first issue
documentation

Since our Azure DevOps tenant is orphaned and we can't seem to get it back we have to consider migrating to another tenant or completely off of ADO towards GitHub...

CI

The title says it all. We need to look into that and get it fixed.

help wanted
CI
test

I've noticed we that we have a few occurrences of terms like "blacks", "whites", "females", "males", and perhaps others in our documentation. This made me aware that I don't know...

documentation

Since fairlearn uses randomized classifiers we need to set expectations for what `predict`, `predict_proba` etc. return.

documentation