SYLLABUS

MATH 4/5779 – Math Clinic

 Medical Image Analysis Using Artificial Neural Nets, Support Vector Machines, and Fuzzy Sets

 

Sponsor: University of Colorado Department of Radiation Oncology

                                                                                             

Fall Semester ‑ 2008

Instructors: Weldon A. Lodwick and Francis Newman

Research Assistant: Elizabeth Untiedt

Office: UC-Denver Building, Room 643, Weldon Lodwick

            UCD-AMC, Francis Newman, CP1032 (Anschutz Cancer Pavilion)

            UC-Denver Building, Room 621, Elizabeth Untiedt

Telephone: 303.556.8462 (office), 303.556.8442 (secretary), 303.556.8550 (fax)

             AMC, Francis 720.848.0134

E-Mail: UCD-DDC, Weldon Lodwick weldon.lodwick@ucdenver.edu

Web Site: Instructors’ website http://www-math.ucdenver.edu/~wlodwick

                 Clinic website http://www-math.cudenver.edu/~euntiedt/5779/

Office Hours:   M/W     10:30AM – 11:30 AM     CU-Denver Bldg 643

W           4:00 PM –   6:00 PM    CU-Denver Bldg 643

                        Other times by appointment

Text: Learning and Softcomputing: Support Vector Machines, Neural Networks, and Fuzzy Logic Models by Vojislav Kecman, MIT Press, 2001.

 

Students with Disabilities: If you have a disability that requires accommodation in this course, please see me as soon as possible.  I am happy to make appropriate accommodations, provided timely notice is received.

 

Cell Phones: You are to turn off your cell phones prior to entering class.

 
Objectives of this Mathematics Clinic: The clinic is primarily a pedagogical tool where one learns applied mathematics by solving problems faced by the Department of Radiation Oncology.  Working in research teams to develop results associated with a project (solving a set of problems and presenting the results) is an integral part of every clinic.  Thus, we will try to solve problems that are of current concern.  In particular, for this semester, our objectives will be:

1.       To develop a software system utilizing artificial neural networks, support vector machines and/or fuzzy methods for the detection of lesions or pathology from real medical images such as in lung or liver disease.

2.       To develop a software system utilizing any of the tools mentioned in 1 above that will detect the difference between the liver and the spleen in real medical images

3.       To develop a software system to differentiate between liver disease caused by obesity and pre-cirrhotic liver disease utilizing any of the tools mentioned above in 1 above.  

4.       To compare and contrast the methods developed

5.       To explore MATLAB parallelization of specified artificial neural networks using automatic differentiation where needed

6.       To explore different image representations such as statistical, Fourier, wavelet transforms, and texture transforms

7.       To explore the connection between Hilbert’s 13th problem, artificial neural networks, non-linear programming and linear programming

8.       Other objectives that emerge during the course of our work.

 

Therefore, upon completion the student should have a good foundation in the mathematics of artificial neural networks, support vector machines, fuzzy methods, and how to apply them to medical images. The “deliverable” to our sponsor is MATLAB code that (or makes good progress such that it):

 

  1. Identifies pathology from real medical images such as in the lung or liver using artificial neural networks, support vector machines, and/or fuzzy methods
  2. Extracts lesions for medical images such as brain MRIs using artificial neural networks, support vector machines and/or fuzzy methods
  3. Uses artificial neural networks, support vector machines and/or fuzzy methods to distinguish spleen from liver of a real medical image
  4. Differentiates between liver disease caused by obesity and pre-cirrhotic liver disease or between normal and abnormal liver
  5. Develops specified parallelized artificial neural network code using automatic differentiation if applicable
  6. Offers image representation such as feature extraction and texture transforms using statistical, Fourier, wavelet, or other techniques
  7. Investigates the possible link between Hilbert’s 13th problem, non-linear, and linear programming (NLP and LP)

 

To accomplish these objectives, the clinic will split up into several teams to work on a semester project. Each individual will be working on subtasks leading to the completion of the team project and each team will have a team leader to coordinate the tasks. Software development involves research to create, to test, to analyze, and to document (the software).

 

Prerequisites

Linear algebra, advanced calculus or junior level engineering mathematics or mathematical physics. The student should have some familiarity with MATLAB or be ready to learn quickly.

 

Assignments

<to be given during the semester – there will be three assignment sets>

 

Topics from the Text

This semester we will cover Chapters 1-7 of the text in addition to materials that will be handed out during the semester.  Chapters 8 and 9 of our text should be read on your own.

 

 

PROPOSED COURSE OUTLINE

The proposed outline is the initial guess of the topics that will be fruitful to investigate.  Research is a process of discovery when one does not know, so the rule is that we will modify our topics during the semester.  Thus the proposed outline will undoubtedly change as we learn more during the semester.

                       

The tentative topics we will cover are:

I.                    Introduction

A.      Conduct of the course, expectations, assignments, projects

B.      History of Artificial Neural Networks (ANNs), Support Vector Machines (SVMs), and Fuzzy Sets/Logic

C.      Problem statement for this semester’s Math Clinic

II.                 Artificial Neural Networks

A.      Examples

B.      Theory

C.      Taxonomy, Functions, Complexity

D.     Applications

III.               Support Vector Machines

A.      Examples

B.      Theory

C.      Applications

IV.               Image representation

A.      Feature representation, image transforms

B.      Texture transforms

V.                  Fuzzy Sets, Fuzzy Logic, Fuzzy Neural Nets, Fuzzy Clustering

A.      Examples

B.      Theory

C.      Applications

 

Tentative Outline of the Schedule

Week of:                                   Topics Covered

August 11, 13                            Discussion of conduct of course, projects, expectations,

                                                            timetables,  assignments, motivation

                                                History of ANNs, SVMs, Fuzzy Sets and Logic, and

                                                            basic definitions

                                                Perceptrons, learning rules, convergence, multi-level

preceptrons, back propagation, SVMs

 

August 18                                  Learning Vector Quantization (LVQ), Radial basis function ANNs, Cascade correlation, Probabilistic ANNs

 

August 20                                  Fuzzy set theory, fuzzy logic

 

September 3                              Adaptive Resonance Theory (ART), Hopfield ANN,

                                                Multi-Valued Neurons (MVN), feature extraction

 

 

September 8                              Project proposal due, (initial annotated bibliography,

                                                methods, materials, schedule, division of labor)

 

September 15, 17                       Fuzzy ANNs, Fuzzy SVMs

 

September 22                             Speaker – Karen Kafaddar (?)

 

September 24                             Lyapunov Stability and LaSalle Invariance

 

September 29                             Hilbert’s 13th Problem, ANNs, and Optimization

 

October 1                                  Progress report 1 due – Written paper and a 15

                                                                        minute oral presentation  by each team

 

October 6                                  Catching up and review of ANNs and SVMs, feature

                                                extraction                     

 

October 8                                  Catching up and review of fuzzy methods

 

October 13                                Automatic Differentiation

 

October 15                                Topics in ANNs – Thermodynamics and ANNs

                                               

October 20                                Guest Speaker TBA or Progress Evaluation

 

October 22                                Guest Speaker TBA or Progress Evaluation

 

October 27                                Speaker – Masahiro Inuiguchi, Rough Sets

 

October 29                                Progress report 2 due – Written paper and a 15

minute oral presentation  by each team, annotated bibliography

 

November 3, 5 – to be specified

 

November 10, 12 – to be specified

 

November 17, 19 – to be specified

 

November 24 – 29 Fall Semester Thanksgiving Break                                

 

December 1, 3 – to be specified,

 

December 5 – Final written reports (with software) due by 5:00pm

 

December 8, 10 – Presentations, 30 minutes/group

 

 

Projects

You are to choose projects from the following list. Projects could evolve, be added, subtracted or modified during the course - not arbitrarily but as a result of circumstances.  Preferably, those interested in, for example, SVMs should collect in one group and should consider fuzzification of the SVM. Likewise, this applies to other methods. The difference between applying SVMs to distinguish liver from spleen will likely be only a feature vector away from using SVMs to distinguish diseased liver from normal liver:

Project 1: SVMs, ANNs and/or fuzzy methods applied to the image segmentation problem

Project 2: SVMs, ANNs and/or fuzzy methods applied to the lesion/pathology detection problem (also known as computer assisted diagnosis, CAD, in medical imaging) for example in lung or liver disease

Project 3: SVMs, ANNs and/or fuzzy methods to distinguish pre-cirrhosis from diffuse liver disease due to obesity or cirrhotic versus normal liver

Project 4: SVMs, ANNs and/or fuzzy methods applied to lesion detection in brain MRIs

Project 5: Image representation, image and texture transforms

Project 6: Parallelization of specified ANNs using MATLAB’s parallel computing tools

Project 7: Other, for example, Hilbert’s 13th problem and its relation to ANNs, NLP and LP

 

OUR APPROACH

We believe that teaching is a process that involves an active partnership.  Our role is that of a guide to your learning.  Therefore, we are responsible to open the way, to encourage, and to nudge you toward your own learning.  In the context of the math clinic, we will try to model the process of applying mathematics to the medical image analysis. We will help guide you toward this learning by providing mathematics for you to experience.  It is our aim to communicate mathematics in a way that is supportive and nurturing of your efforts. Your role is to find a way to experience and articulate the mathematics that is presented and that you encounter.  We believe that it is your responsibility to let us know when you find yourself not understanding mathematical concepts that are presented in class.  Once you make this known, it is our responsibility to work on trying to attain clarity.  We will try to be as proactive as possible.  We believe that results on projects give us the opportunity to clearly see where the areas of mathematical understanding are and what areas need more attention.

 

OUTCOMES

By the end of the semester you should be able to read, understand, and apply appropriate methods associated with aspects of medical image analysis we’ve studied this semester to model correctly and to solve associated problems.  Secondly, given a medical image analysis problem, you should be able to: (i) translate the description of the problem into an algorithm, (ii) choose and apply the appropriate software method(s), (iii) obtain the an appropriate solution(s), and (iv) (correctly) interpret and display results.  Lastly, by the end of the semester you should be able to judge, for yourself, the veracity of statements made in the areas of our study.

 

                                                       EVALUATION

Each person on a team will execute a project (identify a set of problems, find solution methods, present the results and write-up the results).  Individualization of grades are based on the adequacy of fulfillment of the division of labor associated with your team’s project proposal.  In particular, the following are components that will be evaluated.

  1. Participation – attendance and contributing to class interactions/discussions (10%)
  2. Annotated bibliography – Included in Report 2 (5%)
  3. Progress Reports 1, 2 (20% total)
    1. Write-up (5% each)
    2. Presentation (5% each)
  4. Final Presentation (10%)
  5. Final written report (20%)
  6. Final software (25 %) (An adjustment may be made for Hilbert’s 13th problem)
  7. Assignments 1, 2, 3 (10% total) – to be done

** Graduate students will have extended content and be held to higher standards.

The grade assignments are on the 10 percent scale (A = 90%-100%, B = 80%-89%, C = 70%-79%, D = 60-69%).

 

IMPORTANT DATES:

Group/team/project selection – on or before September 8, 2008

Report 1: Written report and presentation (15 minutes each team) – October 1, 2008

(task identification, division of labor for each group, methods, materials)

Report 2:  Written report, presentation, and annotated bibliography – October 29, 2008

Final Report: Written report and software – December 5, 2008 by 5pm

Final Report: Presentation – December 8, 10, 2008

 

General advice: Keep all materials that we turn back in case you think we have not credited you with the points you earned.  we can only correct your score if you have what we have turned back to you. It is a good idea to xerox anything that you turn in just in case we lose what you turn in.  Please check to make sure that the points you earned are the points we have recorded.  Note: The statistics that we have read about correctness of professors in recording grades state that there is a 6% error rate in our recording of your grades.  Please make sure that we have correctly recorded your points.

 

POLICIES

Adds, Drops and incomplete grades: See Schedule of Courses for the relevant dates with respect to adding dropping this course.  Given the budget cuts facing universities, you must be registered by the dates specified or you will not get credit.  The incomplete policy of the Department of Mathematical and Statistical Sciences and the College of Liberal Arts and Sciences is strictly enforced.  Incomplete grades are given only in situations in which a student who has been in good standing all semester, is prevented from completing a course assignment (for example the final exam) due to circumstances beyond her/his control (for example, hospitalization, jury duty, revised job assignments, death in the family, your own departure).

 

Legitimate Excuses: Legitimate excuses are for reasons that are beyond your control.  You may be required to produce an official, signed excuse.  If you are needed in a wedding, for example, you must talk to us prior to the (blessed) event.  If you are legally arrested, then this is not a legitimate excuse.  For matters that are within your control, the general rule is that it is not excused.  However, talk to us prior to the event or arrest or departure.

 

INSTRUCTIONS FOR PROJECTS

A project consists of:

1.       Proposal – Depending on the size of the class, projects may be coalesced or deleted. Each proposed project will be divided into tasks and assigned to each group so that the assignment is equitable.  These tasks and assignments need to be written up and submitted to us. Once the tasks have been identified, assigned, and approved, a division of labor is written by each of the groups.

2.       Division of labor – Each group must take their tasks and subdivide them into subtasks that are assigned to individuals in the group with an associated due-date.  A division of labor is a formal contract between the members of the group.  Once the tasks have been approved and a written division of labor submitted, the group needs to schedule a meeting with us so that we can go over the division of labor, its associated responsibilities and expectations.

3.       Methods and Materials

4.       Annotated Bibliography

5.              Code - the actual computer implementation of the project.  Attention must be paid to efficiency, readability, and portability.

b.       Input – the way information is passed to the software must be transparent and easily usable by the client.

c.       Execution - the algorithm as run must correctly perform what it was designed to do.

d.       Output - relevant, clear display of solution(s) such as tables, graphs, images, reports/lists.

e.       Ease – ease of use.

f.    Documentation – an in-line and hardcopy of the documentation on how to use the software needs to be written.  Moreover, help files must be part of the software.

6.       Testing and analysis

a.       Testing - this part in the context of our clinic consists of running the software developed on the test problems.

b.        Analysis - the purpose of an analysis is to get you to critically evaluate the results obtained from the software as it was run on the test problems.  Part of an analysis is a critique of the software.

 

* A caveat: Negative results are not prohibited. Negative results can be very valuable. However the negative results must be robust in that it would be novel and instructive to the expert community to avoid a particular pathway.

 

7.       Report that will be a chapter in the Clinic Report – Each team will need to be responsible for parts of the final report.  This will be done in MS-Word (needs to be translatable into PDF-Adobe) or Latex as long as we can merge the files in Latex or Adobe Acrobat. The final report will (subject to modifications we uncover) consist of:

a.       Introduction – clinic instructors

b.       Project 1

                                                              i.      Theoretical foundations – theory, application, algorithms

                                                            ii.      Software – description

                                                          iii.      Results – summary, tables, graphs, images, lists, distinguishing features, performance, and limitations

                                                           iv.      Opportunities for further research

                                                             v.      Conclusions

                                                           vi.      Bibliography

                                                         vii.      Appendices

·         Source code

·         Test problems, data, example runs

·         Documentation

·         Proofs

·         Other

c.       Project 2 (same as Project 1) …

d.       Project N (same as Project 1)

NOTE: The software from all teams needs to be burned onto one disk where each team will have a directory into which the software is stored.  At the head of each team’s directory entry, there must be a “read-me” file and the software system must have a “help” command that assists the user. 


 

Fall 2008 CLAS Academic Policies

 

The following policies pertain to all students and are strictly adhered to by the College of Liberal Arts and Sciences (CLAS).

  • Every student MUST check and verify their schedule prior to the published drop/add deadlines.  Failure to verify a schedule is not sufficient reason to justify a late add or drop later in the semester.  It is the student’s responsibility to make sure that their schedule is correct prior to the appropriate deadlines.
  • CLAS students must use their email.cudenver.edu email address.  Email is the official method of communication for all University of Colorado Denver business.  All email correspondence will take place using your CU-Denver email address.  Go to http://www.cudenver.edu/registrar to update and/or change your email address.
  • Students are NOT automatically added to a course off a wait list after wait lists are dropped.  If a student is told by a faculty member that they will be added off the wait list, it is the responsibility of the student to complete the proper paperwork to add a course.
  • Students are not automatically notified if they are added to a class from a wait-list.  Again, it is the responsibility of the student to verify their schedule prior to any official dates to drop or add courses.
  • Students must complete and submit a drop/add form to make any schedule changes.  Students are not automatically dropped from a class if they never attended, stopped attending or do not make tuition payments.  
  • Late adds will be approved only when circumstances surrounding the late add are beyond the student’s control and can be documented independently.  This will require a petition and documentation from the student.  Late adds will only be approved if the student has not taken any exams, quizzes, or has not completed any other graded assignments.  Independent verification of this from the professor of record will be required.  Please note that the signature of a faculty member on an add form does not guarantee that a late add petition will be approved.  Petitions are available in NC 2024.
  • Late drops will be approved only when circumstances surrounding the late drop have arisen after the published drop deadlines, are beyond the student’s control, and can be documented independently.  This will require a petition and documentation from the student.  Pre-existing circumstances (circumstances that existed prior to the published drop deadlines) regarding illness, work, family, or other confounding issues will not be considered adequate reason to drop or withdraw from courses after the published University and/or College drop deadlines.  Please note that the signature of a faculty member does not guarantee that a late drop petition will be approved.  Petitions are available in NC 2024.
  • Students wishing to graduate in fall of 2008 must meet with their academic advisor by the end of the drop/add period to obtain a graduation application.  This application must be completed and submitted by 5 PM on September 3, 2008.  You can obtain an application ONLY after meeting with your aca style='mso-spacerun:yes'>  Students will be responsible for all tuition and fees for courses they do not officially drop using proper drop/add procedures and forms. 

       Students who drop after the published drop/add period will not be eligible for a refund of                       the COF hours or tuition.

 

 

 

Important Dates

 

  • August 11, 2008; First day of Class
  • August 17, 2008 ; Last day to be added to a wait list using the SMART system.
  • August 17, 2008: Last day to add a course using the SMART system.
  • August 11 – September 3, 2008; Students are responsible for verifying an accurate fall 2008 course schedule via the SMART registration system.  Students are NOT notified of their wait-list status by the university.  All students must check their scheduled prior to September 3, 2008 for accuracy.
  • August 18, 2008: LAST DAY TO DROP WITHOUT DROP CHARGE.
  • August 18, 2008: Wait Lists are dropped.  Any student who was not added to a course automatically from the wait list by this date and time MUST complete a drop/add form to be added to the class.  Students are NOT automatically added to the class from the wait list after this date and time.  If your name is not on the official student roster, you are not registered for the course.
  • August 19, 2008: First day instructor may approve request to add a student to a full course with a Schedule Adjustment Form.
  • August 24-29: CAMPUS CLOSED due to Democratic National Convention.  Classes resume on September 2, 2008.
  • September 3, 2008 at 5 PM; Last day to add structured courses without a written petition for a late add.  This is an absolute deadline and is treated as such. This deadline does not apply to independent study, internships, and late-starting modular courses.
  • September 3, 2008 at 5 PM; Last day to drop a fall 2008 course with a tuition refund minus the drop charge and no transcript notation.  Drops after this date will appear on your transcript.  This is an absolute deadline and is treated as such.
  • September 3, 2008 at 5 PM; Last day to completely withdraw from all fall 2008 courses with a tuition refund and no transcript notation. Drop charge applies. Drops after this date will appear on your transcript.  This is an absolute deadline and is treated as such.
  • September 3, 2008 at 5 PM; Last day to request pass/fail option for a course.
  • September 3, 2008 at 5 PM: Last day to request a no credit option for a course.
  • September 3, 2008 at 5 PM: Last day to register for a Candidate for Degree.
  • September 3, 2008 at 5 PM: Last day to petition for a reduction in thesis or dissertation hours.
  • September 3, 2008 at 5 PM: Last day to apply for fall 2008 graduation.  You must make an appointment and see your academic advisor before this date to apply for graduation.
  • September 15, 2008: Early Alert starts for Faculty
  • September 24, 2008: Early Alters ends at 5:00 P.M.
  • October 27, 2008 at 5 PM; Last day for non CLAS students to drop or withdraw from all classes without a petition and special approval from the student’s academic Dean.  This is treated as an absolute deadline.
  • November 7, 2008 at 5 PM; Last day for CLAS students to drop or withdraw from all classes without a petition and special approval from the student’s academic Dean. Students still need signatures from the faculty and Dean.  This is treated as an absolute deadline.
  • After November 7, 2008 all schedule changes require a petition.  Petitions are available in NC 2024.
  • No schedule changes will be granted once finals week has started.  There are NO exceptions to this policy.