Data is the universal truth guiding today’s world of Data Science. At the same time, it is not as simple as it looks to extract actionable insights. Turning data into meaningful insights require deep insights into the domain and the environment from where the data originates.
The year 2020 turned into a painful year. Covid has changed our lives forever. These difficult times have taught us how to be resilient and empathetic. Hope is setting its foot with the arrival of Covid Vaccines. Let’s learn the power of data using Covid Trial Datasets which has led to the emergence of vaccines in record time.
We will be using R as the programming language to explore and visualize Covid Trial Datasets.
Below is a visualization of Covid Vaccine Trial Datasets in R that we will be analyzing:
CovidDF = data.frame(read.csv(“CovidTrials.csv”))
> str(COVID) ‘data.frame’: 5061 obs. of 27 variables:
There are 5061 observations(rows) with 27 variables(columns)
Analyze Gender Variable:
> unique(CovidDF$Gender) [1] “All” “Female” “Male” “” > length(which(CovidDF$Gender == “All”)) [1] 4881 > length(which(CovidDF$Gender == “Male”)) [1] 40 > length(which(CovidDF$Gender == “Female”)) [1] 131 > length(which(CovidDF$Gender == “”)) [1] 9 > nrow(CovidDF); [1] 5061
There is a total of 5061 observations (rows) with 40 males, 131females,4881 all, and 9 unspecified genders.
The value “All” for the gender variable indicates that it can be of any gender. It is hard to achieve precise results when modeling data with gender. Here comes the nightmare of every data engineer trying to deal with incomplete data.
Analyze Study Results Variable:
> unique(CovidDF$Study.Results) [1] “No Results Available” “Has Results” > length(which(CovidDF$Study.Results == “No Results Available”)) [1] 5033 > length(which(CovidDF$Study.Results == “Has Results”)) [1] 28
The above result indicates that the Covid Trial datasets were captured when the study was still happening with 5033 results under “No Results Available”.
Age variable consists of free-form values with different formats used to capture the age of volunteers in different locations.
Below is sample age values captured in trial datasets
18 Years and older (Adult, Older Adult) 18 Years and older (Adult, Older Adult) Child, Adult, Older Adult 18 Years to 48 Years (Adult)
It would have been much better if age was captured as an integer or in a range format. Since it is having different values and formats, we will use convertAge function to approximate age to a certain numeric value.
convertAge <- function(age) { newage = str_replace_all(age, “Child”, “”) newage = str_replace_all(newage, “Adult”, “”) newage = str_replace_all(newage, “Older”, “”) newage = str_replace_all(newage, “older”, “”) newage = str_replace_all(newage, “and”, “”) newage = str_replace_all(newage, “Years”, “”) newage = str_replace_all(newage, “to”, “”) newage = str_replace_all(newage, “up”, “”) newage = str_replace_all(newage, “\(“, “”) newage = str_replace_all(newage, “\)”, “”) newage = str_replace_all(newage, “,”, “”) newage = str_trim(newage, side = c(“both”, “left”, “right”)) newage = ifelse(grepl(“Months”, newage, fixed = TRUE) == TRUE,str_replace_all(newage, newage, “2”), ageStrip) newage = ifelse(grepl(“Month”, newage, fixed = TRUE) == TRUE,str_replace_all(newage, newage, “2”), ageStrip) newage = ifelse(grepl(“Days”, newage, fixed = TRUE) == TRUE,str_replace_all(newage, newage, “1”), ageStrip) newage = substr(newage, nchar(newage)-2+1, nchar(newage)) newage = as.numeric(newage) } ageVector <- sapply(CovidDF$Age, convertAge) CovidDF$NewAge =ageVector CovidDF$NewAge[is.na(CovidDF$NewAge)] <- 0 CovidDF$NewAge = as.numeric(CovidDF$NewAge)
hist(CovidDF$NewAge, xlab=”Age group”, main=”Age of Volunteers in Covid Vaccine Trails”)
The above histogram provides information about the number of volunteers grouped by age.
Box plot of the same information gives the median, 1’st, and 3’rd quartile information
Convert Variable Conditions to a factor, a vector of integer values with a corresponding set of character values. The integer value of the conditions factor can then be used to plot a scatter plot against the new age variable which is also numeric.
ConditionFactor = as.factor(CovidDF$Conditions) CovidDF$NewConditions = as.numeric(ConditionFactor) plot(x=CovidDF$NewAge, y=CovidDF$NewConditions, xlab = “Age”)
The above scatter plot shows more conditions to be registered for age groups 18 and 0. The age group 0 indicates that the trial data did not have any age value.
Data is the oil for all new-age technologies but it is also important to understand the need to properly engineer data without which highly accurate machine learning models would be near to impossible.
Follow us to keep updated on our services and solutions in the field of Data Engineering, Machine Learning and MLOps
The media shown in this article are not owned by Analytics Vidhya and is used at the Author’s discretion.
Step-by-Step Exploratory Data Analysis (EDA) us...
Detecting and Treating Outliers | Treating the ...
Analyze how the Covid-19 affected India?
Exploratory Data Analysis with an Example
Covid-19 Vaccination: Data Analysis & Visu...
A Detailed Study on Covid-19 Vaccination Data
Introduction to ANOVA for Statistics and Data S...
Cross Sell Prediction : Solution to Analytics V...
Indian Patient’s Liver Dataset Analysis a...
Analyze Covid Vaccination Progress Using Python
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