John Schlipf's home page

Professor and Associate Head, Deptartment of Computer Science

Email pattern: firstname.lastname@UC.Edu or lastname@CS.UC.Edu
Departmental FAX #: (001)513.556.7326
 
 

892 Rhodes Hall, University of Cincinnati, Cincinnati, Ohio 45221-0030. Telephone (513)-556-1812

 

Tentative Office hours Spring Quarter MMVII: Moon's, Tiwe's, Thor's, and Freya's Days, 9:30-10:30 (AM!)
and by appointment.
(or, if I'm in my office with my door open & nobody else there, just stop in to see whether I have time to talk.)

The easiest way to reach me is usually email.

-----
 

  Proposal for a CS/CS ACCEND program

Research Interests:

Logic programming & deductive databases, algorithms for satisfiability, computability & complexity, formal verification, model theory.

-----
 
 

Laboratories and Seminars

 UC Theory of Computing Laboratory & Seminar

  UKy Logic & AI Seminar

 UC LINC (laboratory for integrated networked computing)

-----
 
 

 CS major requirements, class of 2012

      Optional requirementsfor transition years, classes of 2008-2011

Note: It is always possible that there are discrepencies between the requirements here and the requirements posted on the College of Engineering web site. If you find a discrepency, please consult with an advisor to straighten it out. Warning: In case of discrepency caused by error, the requirements on the College site are by definition correct.

-----
 

Publications

-----
 
 

Jeff Ward's smodels_cc project

 Jeff Ward's home page

-----
 

  Teaching:

Caveat:Class notes are notes, not textbook pages.  They are not thoroughly proofread, and they sometimes contain errors.  When going through the notes in class I will try to correct all errors verbally, but I do not normally have time to correct the notes afterwards. 

Spring Quarter, 2008

-   Database Theory (CS 651)



Policy on plagiarism:

All work you submit as your own must be your own work.  It is legal to quote or paraphrase material
     from the 
text and from my class notes as long as you clearly credit the source.  It is legal similarly
     to quote material from 
other courses you have taken as long as this does not make the assignment
     trivial.   On work where you are told 
to research other papers/books, you must clearly cite the
     sources of all material you use.  Of couse, properly
citing the source includes not only giving the
     citation but also stating which material was quoted/paraphrased.

     Students may collaborate on principles and concepts relating to any homework or laboratory prob-
     lem or program.
  However, each student must individually design and write her(is) own answer,
     solution, algorithm, or code that is
handed in, unless I explicitly authorize you to do otherwise.
     If you feel you have accidentally gone beyond this,
say, doing part of your program design together,
     clearly explain how much of the work was done tothether and
cite your fellow students (or other
     source).  (You may lose credit for the part you did not do, but, by being honest, you are not com-

     mitting plagiarism.)

      On group assignments I of course expect students in the group to work together (although I nor-
      mally also want to know
which member(s) did each part).  For group work, turn in only one copy
      of the assignment, with all group member's 
names on it.

Allowing someone else to copy your work is also considered plagiarism.  (It is also your responsibility
       not to leave your work
in public places where copying is too easy.)

       On a programming or other homwork assignment, the first instance of plagiarism will normally
       result in a 
score of 0 on that assignment; a second instance will normally result in a grade of "F"
       for the course and likely 
further punishement as per the University's code of student conduct.
       Any plagiarism on exams and on term-length projects will normally result in a grade of "F" for
       the course and likely 
further punishment.

-----


Curriculum Vitae (.pdf)

-----
Science is an Art, not a Science.
Two qualities of a good scientist:
   1.  A wild imagination.
   2.  A  very hard-nosed standard for establishing truth.

The more abstract the topic you are writing about, the more precise you need to make your use of language.  A grunt will often suffice for discussing sports; extreme precision is needed in discussing quantum mechanics or transfinite set theory.

Quiz: Distinguish among the meanings of the following four sentences:
   1.  "Only I want to eat asparagus."
   2.  "I only want to eat asparagus."
   3.  "I want only to eat asparagus."
   4.  "I want to eat only asparagus."
(It is irrelevant that, for me, all four are false.)


Any questions or bug reports regarding the Electrical and Computer Engineering and Computer Science Information servers should go to webmaster@ece.uc.edu.

Last modified: Thor's Day 3 April MMVIII by JSS.