<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://servo.ad.wlu.edu/dokuwiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://servo.ad.wlu.edu/dokuwiki/feed.php">
        <title>W&amp;L Computer Science Wiki - courses:cs211:winter2011:journals:camille</title>
        <description></description>
        <link>http://servo.ad.wlu.edu/dokuwiki/</link>
        <image rdf:resource="http://servo.ad.wlu.edu/dokuwiki/lib/exe/fetch.php/wiki/dokuwiki-128.png" />
       <dc:date>2026-04-22T11:23:08+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter1?rev=1296442025&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter2?rev=1296442067&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter3?rev=1297520938&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter4?rev=1298329259&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter5?rev=1300054682&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter6?rev=1301791201&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter7?rev=1301978394&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/home?rev=1302232997&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/npproblem?rev=1302233610&amp;do=diff"/>
                <rdf:li rdf:resource="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/preface?rev=1295365769&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://servo.ad.wlu.edu/dokuwiki/lib/exe/fetch.php/wiki/dokuwiki-128.png">
        <title>W&L Computer Science Wiki</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/</link>
        <url>http://servo.ad.wlu.edu/dokuwiki/lib/exe/fetch.php/wiki/dokuwiki-128.png</url>
    </image>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter1?rev=1296442025&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-31T02:47:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter1</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter1?rev=1296442025&amp;do=diff</link>
        <description>Chapter 1: Introduction

Section 1: Stable Matching

	*  Summary: 

This section discusses the stable matching problem. This problem was introduced in 1962 to solve/think about the matching process of students to schools in the college admissions process. It can also help solve other matching problems like patients to hospitals, and applicants to jobs or internships. According to our text book, an unstable matching means two people/groups (ex. a university and a student) could agree to make swit…</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter2?rev=1296442067&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-31T02:47:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter2</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter2?rev=1296442067&amp;do=diff</link>
        <description>Chapter 2: Basics

Section 1: Computational Tractability

	*  Summary: 

This section is about the importance of finding efficient algorithms and what it means for an algorithm to be efficient. This book focuses on time efficiency, but also notes that efficient use of space (memory) is also important. We want a definition of efficiency that is platform-independent, instance-independent, and able to predict how the running time changes with increasing input sizes. When we analyze the running time…</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter3?rev=1297520938&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-12T14:28:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter3</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter3?rev=1297520938&amp;do=diff</link>
        <description>Chapter 3: Graphs

Section 1: Basic Definitions and Applications

	*  Summary: 

Graphs are useful in discrete math, and they show up EVERYWHERE if you&#039;re looking at things that way! A graph (a.k.a. Undirected Graph) consists of a collection V of nodes (a.k.a. vertexes) and a collection E of edges (each edge joins two nodes and is represented by a two-element subset of V). Edges indicate a symmetric relationship. Directed graphs have asymmetric relationships (directed edges represented by ordere…</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter4?rev=1298329259&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-02-21T23:00:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter4</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter4?rev=1298329259&amp;do=diff</link>
        <description>Chapter 4: Greedy Algorithms

Section 1: Interval Scheduling: The Greedy Algorithm Stays Ahead

	*  Summary: 

Sometimes greed works. An algorithm is greed if it builds up a solution in small steps, choosing a decision at each step myopically to optimize some underlying criterion. When algorithms work to give an optimal or almost optimal solution, it says something about the problem&#039;s underlying structure. Problem: how to find cases where greedy works and prove that it works. First way: greedy s…</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter5?rev=1300054682&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-13T22:18:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter5</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter5?rev=1300054682&amp;do=diff</link>
        <description>Chapter 5: Divide and Conquer

Section 1: A First Recurrence: The Mergesort Algorithm

	*  Summary: 

Divide and conquer - break the input into several parts, solve the problem in each part recursively, combine the solutions to the subproblems into an overall solution. Recurrence relations are necessary to discuss the running time of these algorithms. These algorithms might not improve running time as much as in the previous section (because they&#039;re reducing the degree of a polynomial running ti…</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter6?rev=1301791201&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-03T00:40:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter6</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter6?rev=1301791201&amp;do=diff</link>
        <description>Chapter 6: Dynamic Programming

Intro

	*  Summary:

There isn&#039;t always a Greedy Algorithm or a Divide and Conquer Algorithm to solve a problem efficiently. Dynamic programming is a faster and more subtle technique. “...the basic idea is drawn from the intuition of divide and conquer and is essentially the opposite of the greedy strategy: one implicitly explores the space of all of the possible solutions, by carefully decomposing things into a series of subproblems, and then building up correct …</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter7?rev=1301978394&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-05T04:39:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>chapter7</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/chapter7?rev=1301978394&amp;do=diff</link>
        <description>Section 1: The Max-Flow Problem and the Ford-Fulkerson Algorithm

	*  Summary: 

This chapter goes back to the bipartite matching problem from the beginning of the term. One problem is to determine the size of the largest matching in a bipartite graph, which needs new techniques to solve. They develop a new class of problems - network flow problems - that include bipartite matching as a special case. They develop a polynomial-time algorithm for the Maximum-Flow Problem and show how it works for …</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/home?rev=1302232997&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-08T03:23:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>home</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/home?rev=1302232997&amp;do=diff</link>
        <description>Camille&#039;s Journal

	*  Preface
	*  Chapter 1: Introduction
	*  Chapter 2: Basics
	*  Chapter 3: Graphs
	*  Chapter 4: Greedy Algorithms
	*  Chapter 5: Divide and Conquer
	*  Chapter 6: Dynamic Programming
	*  Chapter 7: Network Flow
	*  The P versus NP Problem</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/npproblem?rev=1302233610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-08T03:33:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>npproblem</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/npproblem?rev=1302233610&amp;do=diff</link>
        <description>The Status of the P versus NP Problem

	*  Overview: 

The P versus NP problem is still open. It seems like there is not a polynomial time solution to these problems, but this hasn&#039;t been proven. Either way (whether there is a polynomial time solution or not), there would be major implications to our world.</description>
    </item>
    <item rdf:about="http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/preface?rev=1295365769&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-01-18T15:49:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>preface</title>
        <link>http://servo.ad.wlu.edu/dokuwiki/doku.php/courses/cs211/winter2011/journals/camille/preface?rev=1295365769&amp;do=diff</link>
        <description>Preface

	*  Summary: 

Algorithms are important because all kinds of problems (both in computer science and outside of computer science) can be modeled as algorith problems/solved using algorithms. Deeper than that, algorithms provide a language for expressing problems and a way to make the problems/solutions clean and precise. There are two steps/components to algorithms: getting to the</description>
    </item>
</rdf:RDF>
