Support Vector Machine Prediction Model

A simple example of how to setup a Support Vector Machine predictive model using Python with Pandas, MatPlotLib, Seaborn and Scikit Learn.

This is the source code for FullStackWithLawrence Youtube Video -- "????".

Usage

I'm providing this code sample in both native Python as well as Jupyter Notebook formats. They each service their own purpose. The Jupyter Notebook is more explanatory whereas the native Python is more illustrative of a real-world production implementation.

Jupyter Notebook

I strongly recommend that you review the Jupyter notebook that is included in this repo. It provides significantly more explanation on ways to go about inspecting and analyzing your data set before attempting to create a model. Additionally, I've added a read-only copy of my output in html format which you can use as a guide, to better understand what the output of the Jupyter Notebook is supposed to look like.

Note that freely downloadable VS Code natively renders Jupyter Notebooks from inside the code editor, which is a really convenient feature.

Command Line

The included Python module scaffolds the implemntation of a model that would ostensibly be used in a production setting. Be aware that accordingly, this module excludes all code for analysis, QC and corrections to the included data set.

foo@bar:~$ git clone https://github.com/FullStackWithLawrence/007-scikit-learn-svm.git
foo@bar:~$ cd 007-scikit-learn-svm
foo@bar:~$ pip install -r requirements.txt

# run the  code from the command line
foo@bar:~$ python logistic-regression.py

If You're New to Jupyter Notebooks

There's an easy way to get Jupyter Notebooks working immediately, by downloading an application named Anaconda Navigator that is freely available for both Windows and Mac.

If You're New to Python

Note that I created this code sample using Python version 3.10. For best results I'd recommend that you create a Python Virtual Environment based on a matching Python 3.10.x engine. This helps to ensure that you run the exact same Python package versions as I've specified in requirements.txt.

If you starting from scratch then you might need to install Python on your computer, and you might also need to install a good installer. Crazy, and very meta, but yes, you might need to do that.

# 1. check if homebrew is installed on your computer
# -------------------------------------
foo@bar:~$ brew --version
Homebrew 4.0.23
Homebrew/homebrew-core (git revision 50877e2f6f7; last commit 2023-02-27)
Homebrew/homebrew-cask (git revision cf17a964ec; last commit 2023-02-28)

# 2. check if you've previously installed a python interpretter using homebrew
# -------------------------------------
foo@bar:~$ brew list

# 3. if you don't see [email protected] in the output then install it now.
# -------------------------------------
foo@bar:~$ brew install [email protected]

# 4. verify that python3.10 is in your computer's search path
# -------------------------------------
foo@bar:~$ which python3.10
/opt/homebrew/bin/python3.10

# 5. create a Python Virtual Environment using python 3.10 as your interpretter
# -------------------------------------
foo@bar:~$ mkdir fullstackwithlawrence && cd fullstackwithlawrence
foo@bar:~$ python3.10 -m venv venv
foo@bar:~$ source venv/bin/activate

# 6. verify that your Python virtual environment is activated, and
# that it is using Python version 3.10.x
# -------------------------------------
foo@bar:~$ which python
/Users/foo/fullstackwithlawrence/venv/bin/python3.10

foo@bar:~$ python --version
Python 3.10.12

Contributing

Give back to the open source community! If you have good ideas for how to improve this code then by all means, please seize the day and share your improvements by creating a pull request: fork this repo, make your changes, and then open a pull request; most of which can be done directly from Github.

Local development

This being the low budget one-man-band operation that it is, I'm reliant on the automated coding style enforcement and syntax checking capabilities of pre-commit, black and flake8, so you'll want to install these amazing tools prior to attempting a PR as I've also installed automated Github Actions CI tools that will run these tests on all commits.

foo@bar:~$ pip install -r requirements-dev.txt
foo@bar:~$ pre-commit install
pre-commit installed at .git/hooks/pre-commit
foo@bar:~$ 
foo@bar:~$ pre-commit