Show More
@@ -203,13 +203,14 b' Upon initial creation, each input cell is by default a code cell.' | |||
|
203 | 203 | |
|
204 | 204 | Code cells |
|
205 | 205 | ~~~~~~~~~~ |
|
206 | A *code input cell* allows you to edit code inline within the cell, with full syntax highlighting and autocompletion. By default, the language of a code cell is Python, but other languages, such as ``julia`` and ``R``, are handled using magic commands (see below). | |
|
206 | A *code input cell* allows you to edit code inline within the cell, with full syntax highlighting and autocompletion/introspection. By default, the language of a code cell is Python, but other languages, such as ``julia`` and ``R``, are handled using magic commands (see below). | |
|
207 | 207 | |
|
208 | 208 | When a code cell is executed with :kbd:`Shift-Enter`, the code that it contains is transparently exported and run in that language |
|
209 | 209 | (with automatic compiling, etc., if necessary). The result that is returned from this computation is then displayed in the notebook space as the cell's |
|
210 | 210 | *output*. If this output is of a textual nature, then it is placed into a numbered *output cell*. |
|
211 | 211 | However, many other possible forms of output are allowed, for example, |
|
212 |
``matplotlib`` figures and HTML tables (as used, for example, in the |
|
|
212 | ``matplotlib`` figures and HTML tables (as used, for example, in the | |
|
213 | ``pandas`` data analyis package). This is known as IPython's *rich display* capability. | |
|
213 | 214 | |
|
214 | 215 | |
|
215 | 216 | Rich text using Markdown |
@@ -223,12 +224,22 b' Within Markdown cells, you can also include *mathematics* in a straightforward w' | |||
|
223 | 224 | |
|
224 | 225 | Raw cells |
|
225 | 226 | ~~~~~~~~~ |
|
226 |
Raw cells provide a place to put additional information which is not evaluated by the Notebook. This can be used, for example, for extra information |
|
|
227 | Raw cells provide a place to put additional information which is not evaluated by the Notebook. This can be used, for example, for extra information you | |
|
228 | require to be included when the notebook is exported to a certain format. | |
|
229 | ||
|
230 | Heading cells | |
|
231 | ˜˜˜˜˜˜˜˜˜˜˜˜˜ | |
|
232 | You can provide a conceptual structure for your computational document using | |
|
233 | different levels of headings; there are 6 levels available, from level 1 (main | |
|
234 | title) down to level 6 (paragraph). These can be used later for constructing | |
|
235 | tables of contents, etc. | |
|
236 | ||
|
237 | As with Markdown cells, a heading input cell is replaced by a rich text rendering of the heading when the cell is executed. | |
|
227 | 238 | |
|
228 | 239 | |
|
229 | 240 | Magic commands |
|
230 | 241 | -------------- |
|
231 |
Magic commands, or *magics*, are |
|
|
242 | Magic commands, or *magics*, are commands which begin with the symbol ``%``, which send commands to IPython itself (as opposed to standard Python commands which are exported to be run in a Python interpreter). | |
|
232 | 243 | |
|
233 | 244 | Magics control different elements of the way that the IPython notebook operates. They are entered into standard code cells and executed as usual with :kbd:`Shift-Enter`. |
|
234 | 245 |
General Comments 0
You need to be logged in to leave comments.
Login now