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

Own the fit and predict functions #13

Closed
wants to merge 1 commit into from

Conversation

nickrobinson251
Copy link
Contributor

closes #1

@codecov
Copy link

codecov bot commented Apr 21, 2020

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   93.15%   93.15%           
=======================================
  Files           3        3           
  Lines          73       73           
=======================================
  Hits           68       68           
  Misses          5        5           
Impacted Files Coverage Δ
src/Models.jl 100.00% <ø> (ø)
src/test_utils.jl 92.53% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5506930...bb5ffa9. Read the comment docs.

@oxinabox
Copy link
Member

I am just not sure.
This change is definately breaking.

Packages exporting the Models.jl interface but using the StatsBase "interface" internally will become more complex as they will use both fit functions often.

@glennmoy
Copy link
Member

Apart from fitting to some RegressionModel types - there is no particular overlap that I can see that warrants overload StatsBase.fit, StatsBase.predict. Unless RegressionModel subtypes Model in the future there shouldn't be any clashes as of now I don't think?

@oxinabox
Copy link
Member

There are loads of clashes, with Lasso for example.
But maybe those are not to bad.

@nickrobinson251
Copy link
Contributor Author

I think my gripe is that StatBase has a bunch of API stuff (like the names fit and predict) but also a ton of functionality (it's "*Base" name is a misnomer). So alternative is to move fit, predict somewhere else... but that's a whole other kettle of fish 🐟

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

Successfully merging this pull request may close these issues.

Replace StatsBase with our own Models.fit and Models.predict
3 participants