ov VS fastText

Many code reviews Upgrade code to respect new conventions. #111 ccoVeille posted on Apr 13, 2024 go.mod refers to 1.17, so we can use os.ReadFile and os.WriteFile instead of ioutil.ReadFile and ioutil.WriteFile that are now deprecated. We should use errors.As since go 1.13 otherwise any wrapped errors won't be caught. View on GitHub Use JSONL format for New Line Delimited JSON #112 ccoVeille posted on Apr 13, 2024 https://en.wikipedia.org/wiki/JSON_streaming View on GitHub receiver cleanup #522 ccoVeille posted on Apr 05, 2024 Refactor to use consistent parserState receiver Clean unused receivers View on GitHub Fix test helpers #523 ccoVeille posted on Apr 05, 2024 Test helpers should use t.Helper() This way if an error occurs it would be reported outside the helper View on GitHub

ov is a terminal pager. It supports only UTF-8.

- trained with cross-entropy, meaning that model scores can be used more effectively as a 'confidence' - e.g. for spam if you want to say something like "if prediction score > X, then filter", Naive Bayes is not ideal due to the 'naive' assumption which makes the scores very un-calibrated (it tends to give extremely high or low confidence scores for most things).

disclaimer: I haven't really thought about NLP for about 3 years so there may be something better than this now

[1] https://github.com/facebookresearch/fastText

fasttext 50

https://github.com/facebookresearch/fastText the readme may have what I need built in. But not sure. I hate ML documentation. I would love to see data input to data output examples because people expect us to understand their line of thought, and it just doesn't work out that way. This looks like what I need, but I've completely misinterpreted ML documentation many times. Ha

To use the model trained with FastText from the browser, it is necessary to load it via WebAssembly. However, you don't require a WebAssembly knowledge as you can use the fasttext.js file which has all the glue code.

Having the backend code in the plugin repo, and in python held me off. I wrote it to split vimscript/python from the command that finds the info, as it allows to use powerful tools like fasttext rather than a dictionary.