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.

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

load_path behaviour should not depend on the current namespace #5

Closed
ablaom opened this issue Dec 18, 2024 · 1 comment
Closed

load_path behaviour should not depend on the current namespace #5

ablaom opened this issue Dec 18, 2024 · 1 comment

Comments

@ablaom
Copy link

ablaom commented Dec 18, 2024

import OutlierDetectionPython, MLJBase

MLJBase.load_path(OutlierDetectionPython.COFDetector)
# "OutlierDetectionPython.COFDetector"

using OutlierDetectionPython
MLJBase.load_path(OutlierDetectionPython.COFDetector)
# "COFDetector"

The correct load path (the first one) is being written to the MLJ model registry, which will explain why we didn't hit this earlier. However, this bug cased me some grief debugging a separate issue.

It'l likely this issue persists across the OutlierDetection ecosystem.

@ablaom ablaom changed the title The value of load_path should not depend on the current namespace load_path behaviour should not depend on the current namespace Dec 18, 2024
@davnn
Copy link
Member

davnn commented Jan 5, 2025

Hi, this is fixed now in OutlierDetectionInterface 0.2.1. Publishing with OutlierDetection.jl is still open because of other maintenance issues.

@ablaom ablaom closed this as completed Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants