1 / 21

CS 4620 Intelligent Systems

CS 4620 Intelligent Systems. What we want to do today. SHORT course introduction Make sure you know the schedule for the next two weeks Talk Poker!. How 4620 is different from 3610. 3610 Was about a teacher and a textbook teaching you about a number of specific topics

aadi
Download Presentation

CS 4620 Intelligent Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 4620Intelligent Systems

  2. What we want to do today • SHORT course introduction • Make sure you know the schedule for the next two weeks • Talk Poker!

  3. How 4620 is different from 3610 • 3610 • Was about a teacher and a textbook teaching you about a number of specific topics • Was mainly about general techniques of AI which we applied in small, “toy” problems. • 4620 • Will focus on you teaching yourself and your classmates on topics that will depend on you. • Will focus on a “large” systems of knowledge and managing that knowledge to actually do something

  4. Course Goals • The first goal, is for you to explore the idea of intelligent systems in some depth. • In this course, we will define intelligence as "the capacity to acquire and apply knowledge"  thus intelligent systems are those which modify their actions based on prior interactions.  • In this course you will study the techniques and concepts common to this sub-discipline of AI by constructing a non-trivial intelligent system.

  5. Course Goals • The second goal of the course is to provide a capstone experience to your undergraduate computer science curriculum. • To this end, the course provides an opportunity for you, as a part of a software development team in a studio format in conjunction with your instructor, to construct a large software system.  • The concept of a software studio may be new to you.  You should make yourself familiar with the online description of this process.

  6. Software Studio Quick Intro • Takes it’s main idea from the concept of an art or architecture class taught in studio. • Students are given an assignment. • The teacher moves around asking and answering questions. • After a certain length of time some or all of the students gather for a “design critique” • Gather around one student’s project. • That student explains what they did, and answers questions from his/her peers about why they did it that way. • Meant to be a chance for students to REFLECT on their PRODUCT as well as the PROCESS.

  7. Software Studio Quick Intro • We will blend that idea with “Agile Software Development with Scrum” • Once we get started with the project you will complete four, two-week cycles of development and testing (called Sprints) • Each sprint will be followed by a design crit.

  8. Daily Formats • Guided Practice (GP) • These are somewhat related to the "free work days" you might have in other courses.  However, there are some differences and that is why I don't use that term.  • On GP days you and your team are expected to be in class and working on your project.  • I will frequently move around asking questions and expect that you should feel free to ask questions of both me and your classmates.  • You will receive points based on how well you are engaged with your teammates, classmates, and the projects.

  9. Daily Formats • Design Crits (DC) • If we were going to compare this to some of the other courses you have had then these might be labeled "presentation days."  • But it isn’t as PASSIVE as “presentation days” in other courses. • On DC days one or more teams will be expected to explain to the rest of the class where their project is at and/or where their project is going.  • Members of the audience should be actively engaged in asking the other groups questions about decisions and helping consider problems. • You will receive points based on your participation from BOTH sides of the podium

  10. Daily Formats • Readings Discussion (RD) • In the early part of the semester we will spend several class sessions discussing readings which will be selected to give you an introduction to the idea of intelligent/expert systems based on the course needs.  • Most of these discussion will be "led" by the student members of the class, not the instructor.  • You will receive points based on your preparation to participate in a meaningful discussion on the readings.

  11. Grading

  12. For Wednesday • Read materials about the course on the class website ( www.cs.uni.edu/~schafer/4620 ) • Syllabus • Information about the Software Studio Approach • The deliverable schedule for the course project

  13. For Friday • Read two “chapter one” chapters from two different textbooks we COULD have used for this type of course: • PDF files posted online • Paper printouts hanging by my office door if you want to borrow them and photocopy

  14. For next week • Start to brainstorm ideas you have for projects that would interest you.

  15. Types of projects you might consider • Diagnostic system (take in information about a situation and diagnose what is wrong/what to test next) • Filtering System (Classify images, text, email, etc.  Preferably one which learns) • Design systems (know rules for construction of an object and propose new objects to generate given the rules) • Design aids (Merge of several of above.  As the human does the design, suggests next steps) • Schedulers/Planners for any number of domains (faculty course scheduler, lab worker scheduler, etc) • Learning Agent for a particular game • Intelligent tutoring system.

  16. Examples of previous projects • Agents to play a variety of board and computer games • Poker *** • Super Mario Brothers • Medical diagnostic system with a learning component • Neural network based OCR • NLP story problem solver

  17. Poker • In addition to your group project, each student will be working on an agent to play Structure Limit Texas Hold Em poker

  18. The Poker Hands

  19. Texas Hold Em Basics • Each Player makes the best FIVE card poker hand possible from SEVEN cards • Two are unique to the player • Five are community cards shared by everyone

  20. A hand of Structured Limit Texas Hold Em • Every player at the table puts in an Ante ($1) • Every player gets their unique POCKET cards • Betting Round($1 bet/raise) • Three cards are turned up on the board (FLOP) • Betting Round ($1 bet/raise) • One additional card is turned up on the board (TURN) • Betting Round ($2 bet/raise) • One final card is turned up on the board (RIVER) • Betting Round ($2 bet/raise)

  21. A betting round • FOLD – drop out of this hand immediately without needing to pay any more money that may be owed. • CHECK – if no one has bet yet you can choose to stay in without adding money to the pot. • BET – if no one has bet yet you can be the FIRST person to add a bet to the pot. • CALL – if some one has bet you can MATCH the bet to stay in the hand. • RAISE – if someone has bet, and there are still raises remaining, you can elect to MATCH the bet and add an additional bet to the pot.

More Related