This article was published as a part of the Data Science Blogathon
Illustrations of how to address traditional machine learning algorithm queries.
If you are an authorized data scientist, you may have observed any of these problems previously. However, if you are comparatively new, these use cases can prepare different data science concepts that you folks can apply beyond multiple industries.
Regrettably, data science problems usually are not well-developed so swiftly at companies. Alternatively, the use case will evolve over several conflicts depending on the necessities and expectations of the plan.
It is necessary to provide insight into prevailing use cases that can be squeezed and applied to more innovative use cases. Sometimes, you will confront entirely new situations not printed about in articles or examined at universities.
However, the charm of data science is that it is scalable and appropriate across diverse problems with a comparatively low amount of effort.
Let’s explore four use cases you can each apply straight to your job or squeeze to use for later applications — including potential characteristics of the model, as well as the algorithm practised itself.
In this case, we would be formulating a supervised model to categorize it into either fraud or no fraud. Ideally, you would have a good quantity of examples of what noise does and does not seem like in your data.
The following step is to acquire or create several characteristics that explain what a scam looks like and suspected behavior, so the algorithm can efficiently discern among the two labels.
Here are desirable points you could practice in your Random Forest algorithm:
Here is an example code to use:
#after extraction the train and test dataset rf = RandomForestClassifier() rf.fit(X_train, y_train) pred = rf.predict(X_test)
You can originate with a few characteristics and strengthen new features, such as sums or per traits (ex: money spent/day, etc.)
As opposed to the above illustration, this situation would use unsupervised learning, preferably than classification, to use clustering.
A conventional clustering algorithm would be K-Means. This problem is unsupervised because you do not own labels, and you would not understand what to group, but you would desire to find patterns of new combinations based on their shared points.
In this example, the particular purpose of using this model is to find patterns about somebody who buys specific products.
That way, you can build a targeted marketing campaign nominated just for these consumers.
Here are desirable features you could practice in your K-Means algorithm:
Here is a sample code to practice:
#after extracting data and features km = KMeans( init="random", n_clusters=6 ) km.fit(X) preds = km.fit_predict(X)
This algorithm is often practiced in the e-commerce industry, marketing, and anywhere with consumer data and marketing — management.
This scenario could profit from a family of machine learning algorithms. This query is also comparable to the credit card fraud detection query. We want to collect features about the consumers with a predefined label, precisely churn or no-churn.
You can practice Random Forest again or a complex algorithm, for illustration, XGBoost. This situation is, accordingly, a classification problem, which is practicing supervised learning.
We will be prognosticating customer churn for users on a website to purchase a product or many products.
Here are desirable characteristics you could employ in your XGBoost algorithm:
These characteristics can designate if someone is more prominent of a life-long user versus a short-time. Unique features like referral will undoubtedly prove if they like the output.
Product diversity could go each way in the classification if they ordered four separate products but did or did not apply them added times.
Here is sample code to execute once you have your inputs and features ready:
xgb = XGBClassifier() xgb.fit(X_train, y_train) pred = xgb.predict(X_test)
Possibly the most diverse from the preceding three use cases are forecasting transactions. In this sample, we can use deep learning to predict future purchases of a commodity.
The algorithm used is named LSTM, which is for Long Short-Term Memory.
Here are desirable points you could practice in your LSTM algorithm:
Here is the execution of code to use with your input data and features:
lstm= Sequential() lstm.add(LSTM(4, batch_input_shape=(1, X_train.shape[1], X_train.shape[2]))) lstm.add(Dense(1)) lstm.compile(loss='mean_squared_error') lstm.fit(X_train, y_train) preds = lstm.predict(X_test)
This article conferred everyday use cases with conventional algorithms that comprise different problems using data science. For instance, we looked at:
I hope you noticed my article both exciting and relevant. Please feel open to comment below if you employed machine learning algorithms for those use cases.
Connect with me on my social media: MEDIUM LINKEDIN GITHUB
Data Scientist and a Technical Writer! I will give you the best of Open-Source and AI.
Talks about #chatgpt, #opensource, #contentcreation, #communitybuilding, and #artificialintelligence
Technical Writer | Data Science, ML, AI, Open-Source | Do More with Data - Litmus
Top 10 Data Analytics Projects with Source Codes
Top 10 Machine Learning Algorithms You Must Know
What is Predictive Analytics | An Introductory ...
Data Science Use Cases in Retail Industry
Popular Machine Learning Applications and Use C...
A Beginners Guide to the Machine Learning Lifec...
Anomaly Detection in Credit Card Fraud
Churn Prediction- Commercial use of Data Science
4 Essential Tools any Data Scientist can use to...
Loan Status Prediction using Support Vector Mac...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s