![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) # Common Causes of Data Leakage and how to Spot Them Let's learn how to identify and deal with the common causes of data leakage in ML models [Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/) May 17, 20248 min read ![Image by realaxer @Unsplash.com](../images/000.jpg) Image by [realaxer](https://unsplash.com/pt-br/@realaxer) @Unsplash.com One of a Data Scientist's worst nightmares is data leakage. And why is data leakage so harmful? **Because the ways your models may suffer from it are designed to convince you that your model is excellent and that you should be expecting awesome results in the future.** As you may know, the primary goal of every machine learning model is to generalize the patterns it learns for the future data. As we can't really access future data (without making a time machine first), the best way to simulate this during model development is to set aside a test and a validation set to be used to assess model performance. During development, data scientists aim to improve the model's test and validation performance. If results are satisfactory, then data scientists assume that their models are ready for production. And that's why data leakage is so dangerous. As it's able to hide itself in seemingly innocent behaviors, it can lurk in the background, waiting for you to put that model into production and just find out that the performance in real life is way worse than the one on the test set. Normally, data leakage involves the process of polluting our train set with things that will end up violating one or more parameters of "future dataset" rule. And it's one of the most major causes of unsuccessful model deployments. Learn this step by step with the interactive [AI Engineer](https://roadmap.sh/ai-engineer), [AI and Data Scientist](https://roadmap.sh/ai-data-scientist) and [Machine Learning](https://roadmap.sh/machine-learning) roadmaps. In this blog post, we'll discuss some of the most common data leakage sources and some tips on how to spot them! Let's dive in! * * * ## Feature Leakage Probably the most famous data leakage source (and the easiest to spot, as well). Feature leakage happens when we have features that are directly related to the target often being a result of the target event. Normally, feature leakage happens because the feature value is updated in a point in time after the target event. Let's see some examples: * 1) You are trying to predict loan default of a certain customer and one of your features is the number of outbound calls that the customer had in past 30 days. What you don't know is that in this fictional bank the customer only receives outbound calls if it has already entered into a default scenario. * 2) You are trying to predict a certain disease of a patient and are using the number of times the patient went through a specific diagnostic test. However, you later find that this test is only prescribed to people that have a high likelihood of having the disease. * 3) You are using a feature with the name days_finish_contract* as a feature to predict if a customer will churn or not. > *days after the last contract of the customer with a specific company finished (for example, in a telco business). If the customer does not renew, this is, indeed, the churn event. These three examples also show different levels of feature leakage. For example, in 1) and 3), there is a direct correlation between target and features and it's very likely that 100% of the target will have these variables as non-null values. However, 2) is harder to spot, because other patients may have gone through the diagnostic test and didn't have the disease making this leakage source less obvious. One way to spot feature leakage is via _feature importance_ data obtained in different models. **For me, what works very well is fitting an extremely shallow decision tree and checking if one of the features has an enormous difference, in terms of importance, compared to others.** When I find that a feature is overly indexed, those features are normally related to leakage problems. To solve these problems, it's recommended that you look into how these features that have leakage were generated so that you can: * Remove the feature if there's no other way to generate it. * Change the feature so that no information from the future leaks into the target. * * * ## Time Correlated Data using Random-Test Split Funny story - I've learned this the hard way. In the past, I've developed machine learning models to predict soccer games' results and ended up having a betting system that was completely flawed. Probably you've felt something along these lines before - have you ever trained a time-series model and had spectacular results on the test set? That's quite common when you perform a **random train-test** split on your dataset when rows have a time-dependence. Even if you are not training a time series model, but your rows are time-dependent, you should always perform a continuous train-test split based on time and not a random train-test split. Time-dependent data is a tricky thing to model, particularly because covariates and data distribution shifts as time goes by. If you hint any portion of the new distributions to the train set, your model will be flawed. The recommendation for time-dependent data is to perform assessments on a continuous cross-validation (CV) mechanism, similar to the one below: ![Appropriate Train and Test for Time-Dependent Data - Image by Author](../images/001.png) Appropriate Train and Test for Time-Dependent Data - Image by Author So, yeah.. never use random train-test split on time-dependent data! * * * ## Hinting Something to the Test Set via Scaling and Preprocessing This is a trickier one has even sometimes even experienced data scientists end up falling for it. When performing outlier analysis, scaling, missing value imputation, always make sure that you perform those analysis on the train set and after train-test splitting. Sometimes people confuse this sentence with **applying** the same transformations to the test set - while that is completely true (your test set needs to mimic your training set's scale and not contain missing values), you shouldn't give any hint of the distribution of the test set to the train one. For example, imagine you are applying a Standard Scaler (that uses a Z-Score with mean and standard deviation). You want this standard scaler to memorize the average and standard deviation of the **train set. After that set you will apply the same scaler with the fixed statistics from the training set to the test set.** Take another famous preprocessing step: removing outliers. Does it make sense to remove outliers from the test set? Well, if you know what will be an outlier in the future (remember that test sets are just really poor simulations of a future dataset where the model will be used on) then tell me please, because you have just invented a time machine! As it's not possible to remove outliers in the future (of course, **you can remove obvious outliers from being scored by your model)** , you generally lack information about what a "future" outlier will look like. If you do remove outliers in the test set, you should expect a larger drift between the test set performance and real world deployment. To avoid this type of leakage, perform train-test split before you do anything on the data. ![A Data Scientist finding out their model is wrong in Production - Image by AI generated by Microsoft Design](../images/002.jpg) A Data Scientist finding out their model is wrong in Production - Image by AI generated by Microsoft Design * * * ## Leakage from Data Generation and Sources This one is trickier to spot. Feature leakage from data generation and/or data sources is normally tied with how data is collected. You probably won't have full control of it as a data scientist. Let's take the customer default example that we pointed out in the **Feature Leakage -** imagine you are building a predictive model that wants to find out if a customer will default in the next installment and you find out that the number of outbound calls to the customer is a great feature to predict this. You speak with people who are actively doing these phone calls and you find out that the process is fair. They actually call riskier customers and it may make sense that you include this feature in the model. But, after sitting down with them, you find out that there are certain calls that happen after they are certain that the customer will default. What happens is that your IT systems only log defaults one day after they actually happened so some of these calls are actually calls to ask customer why they defaulted. If you use this feature (call is done on day _x_ , default is logged on day _x_ +1), you'll actually be adding leakage to your model's prediction as a feature is leaking information into the target. This is the hardest leakage to spot as it requires that you deeply know how your features were generated and good data governance models. Nevertheless, using the technique we spoke about in the **Feature Leakage** section can be a quick and raw way to understand if you have obvious leakage from the generation and sourcing of your data. * * * ## Feature Engineering Another common way to generate data leakage is during the feature engineering process. Although this is just a subset of **Feature Leakage,** it's so common that I needed to point it out. One common example is when creating moving averages in time-series. Often, people may confuse time intervals and add periods that you are supposed to predict on the average value. When overlooked, this will create an enormous distortion on the time series model. Another example is when using features that were themselves generated by other machine learning models. Using these features is always risky as these models have uncertainty (and may have leakage) inside them. Building these features based on other models can have a high impact and "seemingly" create a much better model that loses its generalization power. ## Conclusion And that's it! These are the most common data leakage problems that I've found in my career as a data scientist. In a nutshell, data leakage is the silent killer of machine learning models. It's designed to make you feel that you have a great model but whose performance is highly influenced by leakage problems. Data leakage issues can be so bad that they can impact your model as soon as you get it into production. Identifying leakage as soon as possible will not only make your model more stable but also more accurate in the real world. Do you know any other data leakage causes that I didn't mention here? Point them out in the comments! Also, feel free to check me out on my Youtube Channel: ![](../images/body-12553483658cd4fc0345.jpeg) You can subscribe to my channel "[_The Data Journey_](https://www.youtube.com/channel/UCq-1TNG9csV4AVa0i6AU5rw)" here. Or my [Udemy ](https://www.udemy.com/user/ivo-bernardo/)page here. ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-6f351be10c9e83aa9f9d.jpeg) Written By ## [Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/) [See all from Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/) [Artificial Intelligence](https://towardsdatascience.com/tag/artificial-intelligence/)[Data Leakage](https://towardsdatascience.com/tag/data-leakage/)[Data Science](https://towardsdatascience.com/tag/data-science/)[Machine Learning](https://towardsdatascience.com/tag/machine-learning/)[Mlops](https://towardsdatascience.com/tag/mlops/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fcommon-causes-of-data-leakage-and-how-to-spot-them-17113406f9f8%2F&title=Common%20Causes%20of%20Data%20Leakage%20and%20how%20to%20Spot%20Them) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fcommon-causes-of-data-leakage-and-how-to-spot-them-17113406f9f8%2F&title=Common%20Causes%20of%20Data%20Leakage%20and%20how%20to%20Spot%20Them) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fcommon-causes-of-data-leakage-and-how-to-spot-them-17113406f9f8%2F&text=Common%20Causes%20of%20Data%20Leakage%20and%20how%20to%20Spot%20Them) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/003.jpg)](https://towardsdatascience.com/ive-done-80-data-science-interviews-here-s-what-works-ae8053f79a6d/) ## [I’ve Done 80+ Data Science Interviews – Here’s What Works](https://towardsdatascience.com/ive-done-80-data-science-interviews-here-s-what-works-ae8053f79a6d/) [Data Science](https://towardsdatascience.com/category/data-science/) 3 years of data science interview experience [Egor Howell](https://towardsdatascience.com/author/egorhowell/) December 24, 20246 min read * [![](../images/004.png)](https://towardsdatascience.com/rethinking-data-science-interviews-in-the-age-of-ai/) ## [Rethinking Data Science Interviews in the Age of AI](https://towardsdatascience.com/rethinking-data-science-interviews-in-the-age-of-ai/) [Data Science](https://towardsdatascience.com/category/data-science/) How AI is transforming data science interviews—and what hiring managers and candidates should do to adapt [Yu Dong](https://towardsdatascience.com/author/ydong029/) July 4, 202510 min read * [![](../images/005.jpeg)](https://towardsdatascience.com/im-a-self-taught-data-scientist-here-are-my-3-suggestions-for-newcomers-5f5d54e597a8/) ## [I'm a Self-Taught Data Scientist. Here Are My 3 Suggestions for Newcomers](https://towardsdatascience.com/im-a-self-taught-data-scientist-here-are-my-3-suggestions-for-newcomers-5f5d54e597a8/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Make your learning journey more efficient. [Soner Yıldırım](https://towardsdatascience.com/author/sonery/) April 13, 20225 min read * [![](../images/006.png)](https://towardsdatascience.com/dont-miss-out-on-pub-sub-5dbfa15cf3d0/) ## [Don't Miss Out on Pub/Sub](https://towardsdatascience.com/dont-miss-out-on-pub-sub-5dbfa15cf3d0/) [Programming](https://towardsdatascience.com/category/programming/) A high-level overview of the Pub/Sub pattern and why you should be incorporating it into your projects. [Andrew Didinchuk](https://towardsdatascience.com/author/appliedarchitect/) February 15, 20213 min read * [![](../images/007.png)](https://towardsdatascience.com/understanding-morphological-image-processing-and-its-operations-7bcf1ed11756/) ## [Understanding Morphological Image Processing and Its Operations](https://towardsdatascience.com/understanding-morphological-image-processing-and-its-operations-7bcf1ed11756/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) This article illustrates Morphological Image Processing in more straightforward terms; readers can understand how Morphology works in... [Prateek Chhikara](https://towardsdatascience.com/author/prateekchhikara/) March 30, 20225 min read * [![](../images/008.png)](https://towardsdatascience.com/kickstart-your-data-science-journey-a-guide-for-aspiring-data-scientists-96e5072bd19a/) ## [Kickstart Your Data Science Journey - A Guide for Aspiring Data Scientists](https://towardsdatascience.com/kickstart-your-data-science-journey-a-guide-for-aspiring-data-scientists-96e5072bd19a/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Key Technical Skills You Need to Kick-start Your Career in Data Science [Saankhya Mondal](https://towardsdatascience.com/author/saankhya/) November 6, 202416 min read * [![](../images/009.jpg)](https://towardsdatascience.com/data-science-for-the-heart-c654135ceee5/) ## [Data Science for the Heart](https://towardsdatascience.com/data-science-for-the-heart-c654135ceee5/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Cardiovascular Disease Data Analysis and Predictive Modeling [Suleman Bazai](https://towardsdatascience.com/author/sulemanbazai/) May 17, 202112 min read * [![](../images/010.jpeg)](https://towardsdatascience.com/why-do-you-need-to-use-sql-grouping-sets-for-aggregating-data-3d172ff5c088/) ## [Why Do You Need to Use SQL Grouping Sets for Aggregating Data?](https://towardsdatascience.com/why-do-you-need-to-use-sql-grouping-sets-for-aggregating-data-3d172ff5c088/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Efficiency, readability, and scalability [Soner Yıldırım](https://towardsdatascience.com/author/sonery/) April 20, 20233 min read * [![](../images/011.jpg)](https://towardsdatascience.com/artificial-intelligence-is-transforming-modern-education-d95bf8d19acd/) ## [Artificial Intelligence is Transforming Modern Education](https://towardsdatascience.com/artificial-intelligence-is-transforming-modern-education-d95bf8d19acd/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) A commentary piece on how AI is being used in today's classrooms as well as discussion on the path forward. [Sanjay Adhikesaven](https://towardsdatascience.com/author/sanjay.adhikesaven/) September 11, 202210 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ "How Relevance Models Foreshadowed Transformers for NLP") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?")