Skip to main content

Data Wrangling vs EDA

 

AspectData Wrangling (Data Preprocessing)Exploratory Data Analysis (EDA)
ObjectivePrepare raw data for modeling by cleaning, transforming, and formatting it appropriately.Explore and understand the data to gain insights, identify patterns, and make decisions on data handling and modeling.
OrderTypically performed as a preliminary step before EDA.Usually conducted after data wrangling to further investigate data characteristics.
Data HandlingFocuses on data cleaning, filling missing values, encoding categorical variables, and scaling features.Involves data visualization, statistical analysis, and summary statistics to uncover patterns, relationships, and anomalies.
TechniquesTechniques include imputation, outlier detection, feature scaling, and one-hot encoding.Techniques include histograms, scatter plots, box plots, correlation matrices, and descriptive statistics.
Data TransformationInvolves structural changes to the dataset, such as feature engineering, data normalization, and dimensionality reduction.Primarily explores existing data structures and relationships without altering the data's fundamental structure.
ToolsCommon tools include libraries like pandas and scikit-learn in Python.Utilizes tools like matplotlib, seaborn, and statistical analysis packages (e.g., R) for visualization and analysis.
OutputsThe output is a clean, preprocessed dataset ready for model training.The output includes visualizations, summary statistics, and insights used for feature selection, model choice, and problem understanding.
PurposeAims to prepare data in a format suitable for machine learning algorithms, ensuring they can effectively learn from the data.Aims to uncover data characteristics, relationships, and potential challenges to inform modeling decisions.
IterationOften an iterative process, as issues discovered during EDA may require revisiting data wrangling steps.Typically a one-time or limited iteration process to understand the data before modeling.
ExamplesRemoving duplicate records, filling missing values, scaling features, encoding categorical variables.Creating histograms to visualize data distributions, generating scatter plots to examine relationships between variables, calculating summary statistics.
Labels:

Comments

Post a Comment

Popular posts from this blog

What is the difference between Elastic and Enterprise Redis w.r.t "Hybrid Query" capabilities

  We'll explore scenarios involving nested queries, aggregations, custom scoring, and hybrid queries that combine multiple search criteria. 1. Nested Queries ElasticSearch Example: ElasticSearch supports nested documents, which allows for querying on nested fields with complex conditions. Query: Find products where the product has a review with a rating of 5 and the review text contains "excellent". { "query": { "nested": { "path": "reviews", "query": { "bool": { "must": [ { "match": { "reviews.rating": 5 } }, { "match": { "reviews.text": "excellent" } } ] } } } } } Redis Limitation: Redis does not support nested documents natively. While you can store nested structures in JSON documents using the RedisJSON module, querying these nested structures with complex condi...
Post a Comment
Read more

Error: could not find function "read.xlsx" while reading .xlsx file in R

Got this during the execution of following command in R > dat Error: could not find function "read.xlsx" Tried following command > install.packages("xlsx", dependencies = TRUE) Installing package into ‘C:/Users/amajumde/Documents/R/win-library/3.2’ (as ‘lib’ is unspecified) also installing the dependencies ‘rJava’, ‘xlsxjars’ trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/rJava_0.9-8.zip' Content type 'application/zip' length 766972 bytes (748 KB) downloaded 748 KB trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/xlsxjars_0.6.1.zip' Content type 'application/zip' length 9485170 bytes (9.0 MB) downloaded 9.0 MB trying URL 'https://cran.rstudio.com/bin/windows/contrib/3.2/xlsx_0.5.7.zip' Content type 'application/zip' length 400968 bytes (391 KB) downloaded 391 KB package ‘rJava’ successfully unpacked and MD5 sums checked package ‘xlsxjars’ successfully unpacked ...
Post a Comment
Read more

Training LLM model requires more GPU RAM than storing same LLM

Storing an LLM model and training the same model both require memory, but the memory requirements for training are typically higher than just storing the model. Let's dive into the details: Memory Requirement for Storing the Model: When you store an LLM model, you need to save the weights of the model parameters. Each parameter is typically represented by a 32-bit float (4 bytes). The memory requirement for storing the model weights is calculated by multiplying the number of parameters by 4 bytes. For example, if you have a model with 1 billion parameters, the memory requirement for storing the model weights alone would be 4 GB (4 bytes * 1 billion parameters). Memory Requirement for Training: During the training process, additional components use GPU memory in addition to the model weights. These components include optimizer states, gradients, activations, and temporary variables needed by the training process. These components can require additional memory beyond just storing th...
Post a Comment
Read more