nextcloud / nextcloud/suspicious_login
Validate the model with realistic and strict data sets
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 106
- Forks
- 32
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 10
Description
In (machine learning) theory, there should be no intersection between the training data set and the validation training set. However, in this application the classifier does not only have to classify IPs it hasn't seen before, but also ones it sees again. Therefore I chose to not only validate on data that has only been seen recently but also IPs there have historic and recent appearance.
These results might not be a real representation of the quality of the model, so I'd like to add a second validation that only uses true recent data.
Contributor guide
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.
Research direction
Start by locating the classifier's existing validation path and the logic selecting recent and historic data. Compare the current validation with a second run using only truly recent data, and report both results so the model quality can be assessed under each dataset definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- machine-learning, php
- Domain
- machine-learning, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100