Characteristics of ID3 Algorithm & Advantages and Disadvantages of ID3 Algorithm

 Characteristics of ID3 Algorithm

Major Characteristics of the ID3 Algorithm are listed below:

  • ID3 uses a greedy approach that's why it does not guarantee an optimal solution; it can get stuck in local optimums.
  • ID3 can overfit the training data (to avoid overfitting, smaller decision trees should be preferred over larger ones).
  • This algorithm usually produces small trees, but it does not always produce the smallest possible tree.
  • ID3 is harder to use on continuous data (if the values of any given attribute is continuous, then there are many more places to split the data on this attribute, and searching for the best value to split by can be time-consuming).

Advantages and Disadvantages of ID3 Algorithm

Advantages

  • Inexpensive to construct
  • Extremely fast at classifying unknown records Easy to interpret for small-sized trees.
  • Robust to noise (especially when methods to avoid over-fitting are employed)
  • Can easily handle redundant or irrelevant attributes (unless the attributes are interacting)

Disadvantages

  • The space of possible decision trees is exponentially large. Greedy approaches are often unable to find the best tree.
  • Does not take into account interactions between attributes
  • Each decision boundary involves only a single attribute



Comments

Popular posts from this blog

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?