Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Optional prediction column: the return #381

Merged
merged 5 commits into from
Apr 30, 2024
Merged

Optional prediction column: the return #381

merged 5 commits into from
Apr 30, 2024

Commits on Apr 25, 2024

  1. Make y_pred column optional for estimated and realized performance + … 

    …tests
    @nnansters
    nnansters committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    8dabdcd View commit details
    Browse the repository at this point in the history

  2. Update data requirements docs

    @nnansters
    nnansters committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    cb6e6b3 View commit details
    Browse the repository at this point in the history

  3. Fix _list_missing issues + add "run with prediction" tests

    @nnansters
    nnansters committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    4eb8cb8 View commit details
    Browse the repository at this point in the history

Commits on Apr 29, 2024

  1. Fix flake8 issues

    @nnansters
    nnansters committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    b6d8bdf View commit details
    Browse the repository at this point in the history

  2. Metric classes were not able to deal with optional predictions yet. 

    Updated the base class and (unfortunately) added asserts to keep mypy from complaining. Didn't want that logic to leak into remove_nans
    @nnansters
    nnansters committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    bdeac0a View commit details
    Browse the repository at this point in the history