Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| playground:test_jupyter [2020/04/02 09:29] – hnagel | playground:test_jupyter [2020/05/11 20:11] (current) – hnagel | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Polymake jupyter tutorials ====== | + | <code perl> |
| + | > $f = $s-> | ||
| + | > $f-> | ||
| + | </ | ||
| + | < | ||
| + | type: PolyhedralFan< | ||
| - | ===== Creating a notebook that should end up on the Polymake website ===== | + | MAXIMAL_CONES |
| + | {0 1 2} | ||
| + | {0 1 3} | ||
| + | {1 2 4} | ||
| + | {0 2 5} | ||
| - | The goal is to automate the conversion process from ipynb markdown, | ||
| - | What is added automatically by dokuwiki: | + | RAYS |
| + | 0 1 1 | ||
| + | 1 0 1 | ||
| + | 1 1 0 | ||
| + | 0 0 1 | ||
| + | 1 0 0 | ||
| + | 0 1 0 | ||
| + | </ | ||
| + | <code perl> | ||
| + | > $f-> | ||
| + | </ | ||
| - | the table of content based on markdown titles and subtitles (TODO: how extactly) | + | looks like this till now: |
| - | ==== What the ipynb2dokuwiki script does: ==== | + | <code perl> |
| + | > $f = $s-> | ||
| + | > $f-> | ||
| + | type: PolyhedralFan< | ||
| - | Markdown cells will be converted with pypandoc. Code source and output in text format are put in a code frame. Output svgs are extracted\\ | + | MAXIMAL_CONES |
| - | Extracts all attached media from and replaces the links | + | {0 1 2} |
| + | {0 1 3} | ||
| + | {1 2 4} | ||
| + | {0 2 5} | ||
| - | ==== What the ipynb2dokuwiki script should optimally do ==== | ||
| - | Use nbconvert preprocessor to run all cells and create the output beforehand? Add preamble with a link to the ipynb file. Add a cd command so that the following notebook code also works in the shell? | + | RAYS |
| + | 0 1 1 | ||
| + | 1 0 1 | ||
| + | 1 1 0 | ||
| + | 0 0 1 | ||
| + | 1 0 0 | ||
| + | 0 1 0 | ||
| - | ==== Miscellaneous ==== | + | > $f-> |
| - | + | ||
| - | When multiple people work on one tutorial it is easier to solve merge conflicts or comprehend changes when ipynbs are committed with output cells cleared and no base64 attachements yet. | + | |
| - | + | ||
| - | Before merging to the master, however, images should be base64 attached (we might want to change this with a seperate folder for each tutorial?). This can be easily done with drag& | + | |
| - | + | ||
| - | roblems with pypandoc, which converts ipynb markdown to dokuwiki markdown: 1. enumerations? | + | |
| - | ==== Embedded images ==== | + | |
| - | + | ||
| - | After conversion the caption " | + | |
| - | ==== Code and code output ==== | + | |
| - | <code perl> | + | |
| - | > application ' | + | |
| - | > # we might need to | + | |
| - | > # reconfigure(" | + | |
| - | > # one svg output | + | |
| - | > svg(cube(3)-> | + | |
| - | > print "SVG output above"; | + | |
| - | </ | + | |
| - | {{ media: | + | |
| - | <code perl> | + | |
| - | SVG output above | + | |
| - | > # multiple svg outputs in a scrollable window | + | |
| - | > svg(cube(3)-> | + | |
| - | > svg(cube(3)-> | + | |
| - | </ | + | |
| - | {{ media: | + | |
| - | + | ||
| - | {{ media: | + | |
| - | <code perl> | + | |
| - | > # a threejs output | + | |
| - | > cube(3)-> | + | |
| </ | </ | ||