The notebook at an itermediate stage

chiragvartak · chiragvartak · commit f367a16514c2 · 2016-03-25T01:33:45.000+05:30
diff --git a/logic.ipynb b/logic.ipynb
@@ -8,7 +8,9 @@
    "source": [
     "# Explaining the logic.py module\n",
     "*Author: Chirag Vartak*<br>\n",
-    "*Date: 23rd March 2016*"
+    "*Date: 23rd March 2016*\n",
+    "\n",
+    "---"
    ]
   },
   {
@@ -42,8 +44,8 @@
     "The class `PropKB` now.\n",
     "* `__init__(self, sentence=None)` : The constructor `__init__` creates a single field `clauses` which will be a list of all the sentences of the knowledge base. Note that each one of these sentences will be a 'clause' i.e. a sentence which is made up of only literals and `or`s.\n",
     "* `tell(self, sentence)` : When you want to add a sentence to the KB, you use the `tell` method. This method takes a sentence, converts it to its CNF, extracts all the clauses, and adds all these clauses to the `clauses` field. So, you need not worry about `tell`ing only clauses to the knowledge base. You can `tell` the knowledge base a sentence in any form that you wish; converting it to CNF and adding the resulting clauses will be handled by the `tell` method.\n",
-    "* `ask_generator(self, query)` : The `ask_generator` function is to be used by the `ask` function. It calls the `tt_entails` function, which in turn returns `True` if the knowledge base entails query and `False` otherwise. The `ask_generator` itself returns and empty dict `{}` if the knowledge base entails query and `None` otherwise. This might seem weird to you a little bit. After all, it makes more sense just to return a `True` or a `False` instead of the `{}` or `None` But this is to maintain consistency with how things are in First-Order Logic, where, an `ask_generator` function, is supposed to return all the substitutions that make the query true in a dict. I will be mostly be using the `ask` function which returns a `{}` or a `False`, but if you don't like this, you can always use the `ask_if_true` function which returns a `True` or a `False`.\n",
-    "* `retract(self, sentence)` : This function removes all the clauses of the sentence given from the knowledge base. Like the `tell` function, you don't have to explicitly pass only clauses to remove them from the knowledge base; any sentence will do fine. The function will take care of converting that sentence to clauses."
+    "* `ask_generator(self, query)` : The `ask_generator` function is used by the `ask` function. It calls the `tt_entails` function, which in turn returns `True` if the knowledge base entails query and `False` otherwise. The `ask_generator` itself returns an empty dict `{}` if the knowledge base entails query and `None` otherwise. This might seem a little bit weird to you. After all, it makes more sense just to return a `True` or a `False` instead of the `{}` or `None` But this is done to maintain consistency with the way things are in First-Order Logic, where, an `ask_generator` function, is supposed to return all the substitutions that make the query true. Hence the dict, to return all these substitutions. I will be mostly be using the `ask` function which returns a `{}` or a `False`, but if you don't like this, you can always use the `ask_if_true` function which returns a `True` or a `False`.\n",
+    "* `retract(self, sentence)` : This function removes all the clauses of the sentence given, from the knowledge base. Like the `tell` function, you don't have to pass clauses to remove them from the knowledge base; any sentence will do fine. The function will take care of converting that sentence to clauses and then remove those."
    ]
   },
   {
@@ -55,33 +57,71 @@
     "## Getting started with Propositional Logic"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": []
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### A note to delete later on\n",
+    "\n",
+    "1. Markdown is converted to HTML. It's closer to HTML than it is to Latex. Hence, to add special symbols, unicode characters etc., use HTML character reference rather than Latex symbols.\n",
+    "2. Propositional symbols in markdown\n",
+    "  * &not; &emsp; `&not;`\n",
+    "  * &and; &emsp; `&and;`\n",
+    "  * &or; &emsp; `&or;`\n",
+    "  * &rarr; &emsp; `&rarr;`\n",
+    "  * &harr; &emsp; `&harr;`\n",
+    "3. And some others\n",
+    "  * &#8872; &emsp; `&#8872;`\n",
+    "  * &equiv; &emsp; `&equiv;`"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "```python\n",
+    "def my_function(string1, string2):\n",
+    "  for in in range(42):\n",
+    "    print string1 + string2\n",
+    "```\n",
+    "\n",
+    "```python def __init__(self, sentence)```"
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": null,
    "metadata": {
     "collapsed": true
    },
    "outputs": [],
-   "source": []
+   "source": [
+    "dcsdfdsf"
+   ]
   }
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Python 3",
+   "display_name": "Python 2",
    "language": "python",
-   "name": "python3"
+   "name": "python2"
   },
   "language_info": {
    "codemirror_mode": {
     "name": "ipython",
-    "version": 3
+    "version": 2
    },
    "file_extension": ".py",
    "mimetype": "text/x-python",
    "name": "python",
    "nbconvert_exporter": "python",
-   "pygments_lexer": "ipython3",
-   "version": "3.4.4"
+   "pygments_lexer": "ipython2",
+   "version": "2.7.11"
   }
  },
  "nbformat": 4,
