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://querydb.blogspot.com/2019/12/machine-learning-part-2.html

Comments

Popular posts

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...




Scala Spark building Jar leads java.lang.StackOverflowError

  Exception -  [Thread-3] ERROR scala_maven.ScalaCompileMojo - error: java.lang.StackOverflowError [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.TraversableForwarder$class.isEmpty(TraversableForwarder.scala:36) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.isEmpty(ListBuffer.scala:45) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.toList(ListBuffer.scala:306) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.ListBuffer.result(ListBuffer.scala:300) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:31) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.mutable.Stack$StackBuilder.result(Stack.scala:27) [Thread-3] INFO scala_maven.ScalaCompileMojo - at scala.collection.generic.GenericCompanion.apply(GenericCompanion.scala:50) [Thread-3] INFO scala_maven.ScalaCompile...




MongoDB Chunk size many times bigger than configure chunksize (128 MB)

  Shard Shard_0 at Shard_0/xyz.com:27018 { data: '202.04GiB', docs: 117037098, chunks: 5, 'estimated data per chunk': '40.4GiB', 'estimated docs per chunk': 23407419 } --- Shard Shard_1 at Shard_1/abc.com:27018 { data: '201.86GiB', docs: 116913342, chunks: 4, 'estimated data per chunk': '50.46GiB', 'estimated docs per chunk': 29228335 } Per MongoDB-  Starting in 6.0.3, we balance by data size instead of the number of chunks. So the 128MB is now only the size of data we migrate at-a-time. So large data size per chunk is good now, as long as the data size per shard is even for the collection. refer -  https://www.mongodb.com/community/forums/t/chunk-size-many-times-bigger-than-configure-chunksize-128-mb/212616 https://www.mongodb.com/docs/v6.0/release-notes/6.0/#std-label-release-notes-6.0-balancing-policy-changes




AWS EMR Spark – Much Larger Executors are Created than Requested

  Starting EMR 5.32 and EMR 6.2 you can notice that Spark can launch much larger executors that you request in your job settings. For example - We started a Spark Job with  spark.executor.cores  =   4 But, one can see that the executors with 20 cores (instead of 4 as defined by spark.executor.cores) were launched. The reason for allocating larger executors is that there is a AWS specific Spark option spark.yarn.heterogeneousExecutors.enabled (exists in EMR only, does not exist in Open Source Spark) that is set to true by default that combines multiple executor creation requests on the same node into a larger executor container. So as the result you have fewer executor containers than you expected, each of them has more memory and cores that you specified. If you disable this option (--conf "spark.yarn.heterogeneousExecutors.enabled=false"), EMR will create containers with the specified spark.executor.memory and spark.executor.cores settings and will not co...




Hive Count Query not working

Hive with Tez execution engine -  count(*) not working , returning 0 results.  Solution -  set hive.compute.query.using.stats=false Refer -  https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties hive.compute.query.using.stats Default Value:  false Added In: Hive 0.13.0 with  HIVE-5483 When set to true Hive will answer a few queries like min, max, and count(1) purely using statistics stored in the metastore. For basic statistics collection, set the configuration property  hive.stats.autogather   to true. For more advanced statistics collection, run ANALYZE TABLE queries.