Skip to main content



Machine Learning Part 1

Machine learning uses algorithms to find patterns in data, and then uses a model that
recognizes those patterns to make predictions on new data.

Machine learning may be broken down into -

  1. Supervised learning algorithms use labeled data - Classification, Regression.
  2. Unsupervised learning algorithms find patterns in unlabeled data - Clustering, Collaborative Filtering, Frequent Pattern Mining
  3. Semi-supervised learning uses a mixture of labeled and unlabeled data.
  4. Reinforcement learning trains algorithms to maximize rewards based on feedback.
Classification - Mailing Servers like Gmail uses ML to classify if an email is Spam or not based on the data of an email: the sender, recipients, subject, and message body. Classification takes a set of data with known labels and learns how to label new records based on that information. For example- An items is important or not. A transaction is fraud or not based upon known labeled examples of transactions which were classified fraud or not.

Regression - Like Linear Regression predicts a numerical value. Example - A person car got damaged and he claimed 1000$ to insurance company. And, historically company has seen or settled insurance amounts up to 800$. Thus, amount of 1000$ can be a fraud amount.

Clustering - Google News uses a technique called clustering to group news articles into different categories based on title and content. Clustering algorithms discover groupings that occur in collections of data.

Collaborative Filtering - Amazon uses a machine learning technique called collaborative filtering (commonly referred to as recommendation) to determine which products users will like, based on their history and similarity to other users. For example - Recommendation : A person buying this Shampoo also purchased Comb & Hair Conditioner.


Supervised algorithms use labeled data - in which both the input and target outcome, or label, are provided to the algorithm.


Supervised Learning is also called predictive modeling or predictive analytics, because you build a model that is capable of making predictions.

Classification and Regression take a set of data with known labels and pre-determined features and learns how to label new records based on that information. Features are the “if questions” that you ask. The label is the answer to those questions. For example - if it is a Fruit, Red or Green in color, Sweet in Taste, Farmed in Cold Regions, Having seeds but not more than 5... then it must be an Apple (Label).
So, if a fruit is orange in color it might not classify as an Apple. It might be orange.

Multiple linear regression models the relationship between two or more “Features” and a response “Label.” For example, if we wanted to model the relationship between the amount of fraud and the age of the claimant, the claimed amount, and the severity of the accident, the multiple linear regression function would look like this:

Amount Fraud = intercept + (coefficient1 * age) + (coefficient2 * claimed Amount) +
(coefficient3 * severity) + error.

Logistic regression measures the relationship between the Y “Label” and the X “Features” by estimating probabilities using a logistic function. The model predicts a probability, which is used to predict the label class. For example - Label can be "Probability of Fraud" and Features can be "Transaction amount, merchant type, time location, and time difference since last transaction"

Classification:Logistic regression, Decision tree classifier, Random forest classifier, Gradient-boosted tree classifier, Multilayer perception classifier, Linear Support Vector Machine, Naive Bayes

Regression:Linear regression, Generalized linear regression, Decision tree regression, Random forest regression, Gradient-boosted tree regression, Survival regression, Isotonic regression.

--------------

Unsupervised learning, also sometimes called descriptive analytics, does not have labeled data provided in advance. These algorithms discover similarities, or regularities, in the input data. An example of unsupervised learning is grouping similar customers, based on purchase data.

Clustering- an algorithm classifies inputs into categories by analyzing similarities between input examples. Ex- Grouping similar customers, Text categorization, Network Security Anomaly detection (anomalies find what is not similar, which means the outliers from clusters)

The k-means algorithm groups observations into k clusters in which each observation belongs to the cluster with the nearest mean from its cluster center.

Clustering with unsupervised learning is often combined with supervised learning in order to get more valuable results.

Collaborative Filtering - Frequent Pattern Mining, Association, Co-Occurrence, Market Basket Recommendations - Frequent pattern or association rule mining finds frequent co-occurring associations among a collection of items, such as products often purchased together.  Ex - beer and diaper story.

Clustering: k-means, Latent Dirichlet allocation (LDA), Gaussian mixture model (GMM)
Collaborative Filtering: Alternating least squares (ALS)
Frequent Pattern Mining: FP-Growth Algorithm

-----------
Deep learning is the name for multilayered neural networks, which are networks composed of several “hidden layers” of nodes between the input and output. Each node takes input data and a weight and outputs a confidence score to the nodes in the next layer, until the output layer is reached, where the error of the score is calculated. With backpropagation inside of a process called gradient descent, the errors are sent back through the network again and the weights are adjusted, improving the model. This process is repeated thousands of times, adjusting a model’s weights in response to the error it produces, until the error can’t be reduced any more.

During this process the layers learn the optimal features for the model, which has the advantage that features do not need to be predetermined. However, this has the disadvantage that the model’s decisions are not explainable.

Deep learning libraries or frameworks that can be leveraged with Spark include: BigDL, Spark Deep Learning, Pipelines, TensorFlowOnSpark, dist-keras, H2O Sparkling Water, PyTorch, MXNet, Caffe

Part2 - https://techdevins.blogspot.com/2019/12/machine-learning-part-2.html

Comments

Popular posts

Python [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier

  Error requests.exceptions.SSLError: HTTPSConnectionPool  Max retries exceeded with url:  (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)'))). Analysis & Solution Recently, we updated from Python 3.11 to 3.13, which resulted in error above. We did verify AKI = SKI in chain of certificates. Also, imported chain of certificates into certifi. Nothing worked for us. Seemingly, it is a bug with Python 3.13. So, we downgraded to Python 3.12 and it started working. Other problems and solution -  '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)'))) solution  pip install pip-system-certs [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired  (_ssl.c:1006) solution  1# openssl s_client -showcerts -connect  signin.aws.amazon.com:443  </dev/...




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...




MongoDB Regex Query taking more time in Production but same query perform well in UAT

   We came across a situation where-in, MongoDB Query was taking more time in Production like 10 seconds and 4.2 seconds but same query performed well in UAT taking under 400 ms. The very first thought that was evident to us that it is because of amount of data which differed in UAT and Production. Then we ran following to see the execution plan -   db.collection.aggregate(<queries>).explain() This gave us Winning and Rejected Plans. Under which, we analyzed that although it was using 'IXSCAN.' But, it was incorrect index- as we had one compound index built on time field and other fields, and there was other index just on time field for TTL purposes. Winning plan picked TTL index rather than compound index. Thus, we dropped TTL index and built TTL index on a different time field.  That got our query performance time from 10 seconds to 726 ms. Also, for other query the performance came down from 8 seconds to 4.3 seconds. Then, we ran following -  ...




What is Leadership

 




Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...