Improvements to support naive Bayes classification of text documents
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- julia
- Domain
- machine-learning
Research direction
Start by comparing the existing MLJNaiveBayesInterface.jl wrapper with dictionary support in NaiveBayes.jl and the text-specific classifier in TextAnalysis. Clarify whether the interface should support arbitrary Multiset inputs, sparse matrices, or both, then define the chosen scope and its completion criteria before changing code.
Written by the indexing model from the issue text.
Description
Currently we wrap NaiveBayes.jl, but only allow tabular input (internally converted to matrix) which limits application to NLP and elsewhere. However NaiveBayes.jl itself supports dictionary input.
There is also a text-specific NaiveBayes classifier in TextAnalysis, which accepts dictionaries (keyed on abstract strings).
I have never used either package seriously but my gut feeling is that there would be little difference in performance when using dictionaries, and would suggest we simply enhance the existing interface at MLJNaiveBayesInterface.jl rather than write a new interface. Also, there would be no reason I see to restrict to abstract string keys - any abstract dictionary with Integer values should be supportable. Such objects have the scientific type Multiset{S} where S is the scitype of the keys. So we could support any Multiset as input.
Another possibility might be to add support for sparse matrices, probably adjoints of julia's SparseArrayCSC matrices (input to MLJ model is n x p by convention). However this requires a small generalisation of the NaiveBayes package (needed anyway) which at the moment only supports concrete Matrix types.
Very happy to hear some different suggestions for improving naive bayes support.
@storopoli Perhaps this is something you would be interested in helping out with?
cc @pazzo83
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JuliaAI/MLJ
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Disappearing Hyperpapameter Tuning paneMay be free again @EssamWisam claimed this 593 days ago, and no pull request is open. Open
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
agent/scanner bug stage/010-actionable
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
torch-spyre/spyre-inference#1748 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
CausalForecaster fails with KeyError/IndexError on graphs that include the C nodePossibly taken @aryankalantri claimed this today. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Serialization] `load_state_dict_from_file` drops the device index of a `torch.device` map_locationPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
huggingface/huggingface_hub#5409 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
flashinfer-ai/flashinfer#9803 ·
Maintainers usually reply within 1 day