![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 [Data Science](https://towardsdatascience.com/category/data-science/) # Using NumPy to Analyze My Daily Habits (Sleep, Screen Time & Mood) Can I use NumPy to figure out how my habits affect my mood and productivity? [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) October 28, 20258 min read ![](../images/000.jpg) I’ve been running a small NumPy project series where I try to actually _build something_ with NumPy instead of just going through random functions and documentation. I’ve always felt that the best way to learn is by doing, so in this project, I wanted to create something both practical and personal. The idea was simple: analyze my daily habits — sleep, study hours, screen time, exercise, and mood — and see how they affect my productivity and general well-being. The data isn’t real; it’s fictional, simulated over 30 days. But the goal isn’t the accuracy of the data — it’s learning how to use NumPy meaningfully. So let’s walk through the process step by step. ## Step 1 — Loading and Understanding the Data I started by creating a simple NumPy array that contained 30 rows (one for each day) and six columns — each column representing a different habit metric. Then I saved it as a `.npy` file so I could easily load it later. Learn this step by step with the interactive [AI and Data Scientist](https://roadmap.sh/ai-data-scientist) roadmap. python ``` # TODO: Import NumPy and load the .npy data file import numpy as np data = np.load(‘activity_data.npy’) ``` Once loaded, I wanted to confirm that everything looked as expected. So I checked the **shape** (to know how many rows and columns there were) and the **number of dimensions** (to confirm it’s a 2D table, not a 1D list). python ``` # TODO: Print array shape, first few rows, etc. data.shape data.ndim ``` **OUTPUT: 30 rows, 6 columns, and ndim=2** I also printed out the first few rows just to visually confirm that each value looked fine — for instance, that sleep hours weren’t negative or that the mood values were within a reasonable range. python ``` # TODO: Top 5 rows data[:5] ``` **Output:** markup ``` array([[ 1. , 6.5, 5. , 4.2, 20. , 6. ],[ 2. , 7.2, 6. , 3.1, 35. , 7. ],[ 3. , 5.8, 4. , 5.5, 0. , 5. ],[ 4. , 8. , 7. , 2.5, 30. , 8. ],[ 5. , 6. , 5. , 4.8, 10. , 6. ]]) ``` ## Step 2 — Validating the Data Before doing any analysis, I wanted to make sure the data made sense. It’s something we often skip when working with fictional data, but it’s still good practice. So I checked: * No negative sleep hours * No mood scores less than 1 or greater than 10 For sleep, that meant selecting the sleep column (index 1 in my array) and checking if any values were below zero. python ``` # Make sure values are reasonable (no negative sleep) data[:, 1] < 0 ``` **Output:** markup ``` array([False, False, False, False, False, False, False, False, False,False, False, False, False, False, False, False, False, False,False, False, False, False, False, False, False, False, False,False, False, False]) ``` This means no negatives. Then I did the same for mood. I counted to find that the mood column was at index 5, and checked if any were below 1 or above 10. python ``` # Is mood out of range? data[:, 5] < 1 data[:, 5] > 10 ``` **We got the same output.** Everything looked good, so we could move on. ## Step 3 — Splitting the Data into Weeks I had 30 days of data, and I wanted to analyze it week by week. The first instinct was to use NumPy’s `split()` function, but that failed because 30 isn’t evenly divisible by 4. So instead, I used `np.array_split()`, which allows uneven splits. That gave me: * Week 1 → 8 days * Week 2 → 8 days * Week 3 → 7 days * Week 4 → 7 days python ``` # TODO: Slice data into week 1, week 2, week 3, week 4 weekly_data = np.array_split(data, 4) weekly_data ``` **Output:** markup ``` [array([[ 1. , 6.5, 5. , 4.2, 20. , 6. ],[ 2. , 7.2, 6. , 3.1, 35. , 7. ],[ 3. , 5.8, 4. , 5.5, 0. , 5. ],[ 4. , 8. , 7. , 2.5, 30. , 8. ],[ 5. , 6. , 5. , 4.8, 10. , 6. ],[ 6. , 7.5, 6. , 3.3, 25. , 7. ],[ 7. , 8.2, 3. , 6.1, 40. , 7. ],[ 8. , 6.3, 4. , 5. , 15. , 6. ]]),array([[ 9. , 7. , 6. , 3.2, 30. , 7. ],[10. , 5.5, 3. , 6.8, 0. , 5. ],[11. , 7.8, 7. , 2.9, 25. , 8. ],[12. , 6.1, 5. , 4.5, 15. , 6. ],[13. , 7.4, 6. , 3.7, 30. , 7. ],[14. , 8.1, 2. , 6.5, 50. , 7. ],[15. , 6.6, 5. , 4.1, 20. , 6. ],[16. , 7.3, 6. , 3.4, 35. , 7. ]]),array([[17. , 5.9, 4. , 5.6, 5. , 5. ],[18. , 8.3, 7. , 2.6, 30. , 8. ],[19. , 6.2, 5. , 4.3, 10. , 6. ],[20. , 7.6, 6. , 3.1, 25. , 7. ],[21. , 8.4, 3. , 6.3, 40. , 7. ],[22. , 6.4, 4. , 5.1, 15. , 6. ],[23. , 7.1, 6. , 3.3, 30. , 7. ]]),array([[24. , 5.7, 3. , 6.7, 0. , 5. ],[25. , 7.9, 7. , 2.8, 25. , 8. ],[26. , 6.2, 5. , 4.4, 15. , 6. ],[27. , 7.5, 6. , 3.5, 30. , 7. ],[28. , 8. , 2. , 6.4, 50. , 7. ],[29. , 6.5, 5. , 4.2, 20. , 6. ],[30. , 7.4, 6. , 3.6, 35. , 7. ]])] ``` Now the data was in four chunks, and I could easily analyze each one separately. ## Step 4 — Calculating Weekly Metrics I wanted to get a sense of how each habit changed from week to week. So I focused on four main things: * Average sleep * Average study hours * Average screen time * Average mood score I stored each week’s array in a separate variable, then used `np.mean()` to calculate the averages for each metric. ### Average sleep hours python ``` # store into variables week_1 = weekly_data[0] week_2 = weekly_data[1] week_3 = weekly_data[2] week_4 = weekly_data[3] # TODO: Compute average sleep week1_avg_sleep = np.mean(week_1[:, 1]) week2_avg_sleep = np.mean(week_2[:, 1]) week3_avg_sleep = np.mean(week_3[:, 1]) week4_avg_sleep = np.mean(week_4[:, 1]) ``` ### Average study hours python ``` # TODO: Compute average study hours week1_avg_study = np.mean(week_1[:, 2]) week2_avg_study = np.mean(week_2[:, 2]) week3_avg_study = np.mean(week_3[:, 2]) week4_avg_study = np.mean(week_4[:, 2]) ``` ### Average screen time python ``` # TODO: Compute average screen time week1_avg_screen = np.mean(week_1[:, 3]) week2_avg_screen = np.mean(week_2[:, 3]) week3_avg_screen = np.mean(week_3[:, 3]) week4_avg_screen = np.mean(week_4[:, 3]) ``` ### Average mood score python ``` # TODO: Compute average mood score week1_avg_mood = np.mean(week_1[:, 5]) week2_avg_mood = np.mean(week_2[:, 5]) week3_avg_mood = np.mean(week_3[:, 5]) week4_avg_mood = np.mean(week_4[:, 5]) ``` Then, to make everything easier to read, I formatted the results nicely. python ``` # TODO: Display weekly results clearly print(f”Week 1 — Average sleep: {week1_avg_sleep:.2f} hrs, Study: {week1_avg_study:.2f} hrs, “ f”Screen time: {week1_avg_screen:.2f} hrs, Mood score: {week1_avg_mood:.2f}”) print(f”Week 2 — Average sleep: {week2_avg_sleep:.2f} hrs, Study: {week2_avg_study:.2f} hrs, “ f”Screen time: {week2_avg_screen:.2f} hrs, Mood score: {week2_avg_mood:.2f}”) print(f”Week 3 — Average sleep: {week3_avg_sleep:.2f} hrs, Study: {week3_avg_study:.2f} hrs, “ f”Screen time: {week3_avg_screen:.2f} hrs, Mood score: {week3_avg_mood:.2f}”) print(f”Week 4 — Average sleep: {week4_avg_sleep:.2f} hrs, Study: {week4_avg_study:.2f} hrs, “ f”Screen time: {week4_avg_screen:.2f} hrs, Mood score: {week4_avg_mood:.2f}”) ``` **Output:** markup ``` Week 1 – Average sleep: 6.94 hrs, Study: 5.00 hrs, Screen time: 4.31 hrs, Mood score: 6.50Week 2 – Average sleep: 6.97 hrs, Study: 5.00 hrs, Screen time: 4.39 hrs, Mood score: 6.62Week 3 – Average sleep: 7.13 hrs, Study: 5.00 hrs, Screen time: 4.33 hrs, Mood score: 6.57Week 4 – Average sleep: 7.03 hrs, Study: 4.86 hrs, Screen time: 4.51 hrs, Mood score: 6.57 ``` ## Step 5 — Making Sense of the Results Once I printed out the numbers, some patterns started to show up. My **sleep hours** were pretty steady for the first two weeks (around 6.9 hours), but in week three, they jumped to around 7.1 hours. That means I was “sleeping better” as the month went on. By week four, it stayed roughly around 7.0 hours. For **study hours** , it was the opposite. Week one and two had an average of around 5 hours per day, but by week four, it had dropped to about 4 hours. Basically, I started off strong but slowly lost momentum — which, honestly, sounds about right. Then came **screen time**. This one hurt a bit. In week one, it was roughly 4.3 hours per day, and it just kept creeping up every week. The classic cycle of being productive early on, then slowly drifting into more “scrolling breaks” later in the month. Finally, there was **mood**. My mood score started at around 6.5 in week one, went slightly up to 6.6 in week two, and then kind of hovered there for the rest of the period. It didn’t move dramatically, but it was interesting to see a small spike in week two — right before my study hours dropped and my screen time increased. To make things interactive, I thought it’d be great to visualise using matplotlib. ![Weekly Habit Trends Over 30 Days](../images/001.jpg) ## Step 6 — Looking for Patterns Now that I had the numbers, I wanted to know _why_ my mood went up in week two. So I compared the weeks side by side. Week two had decent sleep, high study hours, and relatively low screen time compared to the later weeks. That might explain why my mood score peaked there. By week three, even though I slept more, my study hours had started to dip — maybe I was resting more but getting less done, which didn’t boost my mood as much as I expected. This is what I liked about the project: it’s not about the data being real, but about how you can _use NumPy_ to explore patterns, relationships, and small insights. Even fictional data can tell a story when you look at it the right way. ## Step 7 — Wrapping Up and Next Steps In this little project, I learned a few key things — both about NumPy and about structuring analysis like this. We started with a raw array of fictional daily habits, learned how to check its structure and validity, split it into meaningful chunks (weeks), and then used simple NumPy operations to analyze each segment. It’s the kind of small project that reminds you that data analysis doesn’t always have to be complex. Sometimes it’s just about asking simple questions like _“How is my screen time changing over time?”_ or _“When do I feel the best?”_ If I wanted to take this further (which I probably will), there are so many directions to go: * Find the **best and worst days** overall * Compare **weekdays vs weekends** * Or even create a simple “wellbeing score” based on multiple habits combined But that’ll probably be for the next part of the series. For now, I’m happy that I got to apply NumPy to something that feels real and relatable — not just abstract arrays and numbers, but habits and emotions. That’s the kind of learning that sticks. **Thanks for reading.** If you’re following along with the series, try recreating this on your own fictional data. Even if your numbers are random, the process will teach you how to slice, split, and analyze arrays like a pro. ## 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-542334df68a32cd56c4a.jpeg) Written By ## [Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [See all from Ibrahim Salami](https://towardsdatascience.com/author/ibrahim.salami/) [Data Analytics](https://towardsdatascience.com/tag/data-analytics/)[Data Visualization](https://towardsdatascience.com/tag/data-visualization/)[Numpy](https://towardsdatascience.com/tag/numpy/)[Programming](https://towardsdatascience.com/tag/programming/)[Statistics](https://towardsdatascience.com/tag/statistics/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fusing-numpy-to-analyze-my-daily-habits-sleep-screen-time-mood%2F&title=Using%20NumPy%20to%20Analyze%20My%20Daily%20Habits%20\(Sleep%2C%20Screen%20Time%20%26%C2%A0Mood\)) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fusing-numpy-to-analyze-my-daily-habits-sleep-screen-time-mood%2F&title=Using%20NumPy%20to%20Analyze%20My%20Daily%20Habits%20\(Sleep%2C%20Screen%20Time%20%26%C2%A0Mood\)) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fusing-numpy-to-analyze-my-daily-habits-sleep-screen-time-mood%2F&text=Using%20NumPy%20to%20Analyze%20My%20Daily%20Habits%20\(Sleep%2C%20Screen%20Time%20%26%C2%A0Mood\)) 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/002.jpeg)](https://towardsdatascience.com/drop-rows-pandas-d1772a054f0/) ## [How To Drop a List of Rows From Pandas DataFrame](https://towardsdatascience.com/drop-rows-pandas-d1772a054f0/) [Programming](https://towardsdatascience.com/category/programming/) Removing multiple rows from a pandas DataFrame in Python [Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/) September 22, 20224 min read * [![](../images/003.png)](https://towardsdatascience.com/sample-ratio-mismatch-so-many-questions-how-to-answer-them-a86a1893e35/) ## [Sample Ratio Mismatch: So many questions. How to answer them?](https://towardsdatascience.com/sample-ratio-mismatch-so-many-questions-how-to-answer-them-a86a1893e35/) [Data Science](https://towardsdatascience.com/category/data-science/) Nothing deflates an A/B testing program quicker than data validation issues - and SRM is one of the most damaging. But how accurate is... [Iqbal Ali](https://towardsdatascience.com/author/iqbalali/) April 20, 202214 min read * [![](../images/004.jpeg)](https://towardsdatascience.com/predicting-the-price-of-the-beyond-meat-stock-using-random-forest-in-python-ebeae6aa9d49/) ## [Predicting the Price of the Beyond Meat Stock Using Random Forest in Python](https://towardsdatascience.com/predicting-the-price-of-the-beyond-meat-stock-using-random-forest-in-python-ebeae6aa9d49/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) In this post we will predict the price of the Beyond Meat stock using random forest. Beyond Meat is a producer of plant-based meat... [Sadrach Pierre, Ph.D.](https://towardsdatascience.com/author/spierre91/) November 3, 20192 min read * [![](../images/005.jpeg)](https://towardsdatascience.com/get-started-with-mlops-fd7062cab018/) ## [Get started with MLOps](https://towardsdatascience.com/get-started-with-mlops-fd7062cab018/) [Data Science](https://towardsdatascience.com/category/data-science/) A comprehensive MLOps tutorial with open source tools [Mathias Gruber](https://towardsdatascience.com/author/nanomathias/) May 9, 202124 min read * [![](../images/006.jpg)](https://towardsdatascience.com/predicting-customer-churn-using-logistic-regression-9543c60f6d47/) ## [Predicting Customer Churn using Logistic Regression](https://towardsdatascience.com/predicting-customer-churn-using-logistic-regression-9543c60f6d47/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) My first exposure to the Logistic Regression algorithm The churn rate, also known as the... [Shaunak Varudandi](https://towardsdatascience.com/author/shaunakvarudandi/) November 3, 20206 min read * [![](../images/007.jpg)](https://towardsdatascience.com/how-to-find-probability-from-probability-density-plots-7c392b218bab/) ## [How To Find Probability From Probability Density Plots](https://towardsdatascience.com/how-to-find-probability-from-probability-density-plots-7c392b218bab/) [Data Science](https://towardsdatascience.com/category/data-science/) To understand the distribution of data by knowing the actual probability within a range [Admond Lee](https://towardsdatascience.com/author/admond1994/) May 17, 20195 min read * [![](../images/008.jpeg)](https://towardsdatascience.com/7-examples-to-master-line-plots-with-python-seaborn-42d8aaa383a9/) ## [7 Examples to Master Line Plots With Python Seaborn](https://towardsdatascience.com/7-examples-to-master-line-plots-with-python-seaborn-42d8aaa383a9/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Practical data visualization guide. [Soner Yıldırım](https://towardsdatascience.com/author/sonery/) September 11, 20215 min read * [![](../images/009.jpg)](https://towardsdatascience.com/ai-is-working-against-your-job-application-bec65d496d22/) ## [Using NLP to improve your Resume](https://towardsdatascience.com/ai-is-working-against-your-job-application-bec65d496d22/) [NLP](https://towardsdatascience.com/category/artificial-intelligence/nlp/) Performing keyword matching and text analysis on job descriptions [David Moore](https://towardsdatascience.com/author/cognitivedave/) February 16, 202110 min read * [![](../images/010.jpeg)](https://towardsdatascience.com/generative-adversarial-networks-in-python-73d3972823d3/) ## [Generative Adversarial Networks in Python](https://towardsdatascience.com/generative-adversarial-networks-in-python-73d3972823d3/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Introduction to GANs in Python [Sadrach Pierre, Ph.D.](https://towardsdatascience.com/author/spierre91/) June 11, 20208 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/4970/image?etag=1780565225463&width=500&height=500) Productivity Tips, Data Career Insights, and Other Recent Must-Reads ](https://towardsdatascience.com/productivity-tips-data-career-insights-and-other-recent-must-reads-5c47eb7a2fe0/ "Productivity Tips, Data Career Insights, and Other Recent Must-Reads") * [ ![](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?")