playground:test_jupyter

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
playground:test_jupyter [2020/04/02 09:29] hnagelplayground:test_jupyter [2020/05/11 20:11] (current) hnagel
Line 1: Line 1:
-====== Polymake jupyter tutorials ======+<code perl> 
 +> $f $s->SECONDARY_FAN; 
 +> $f->properties; 
 +</code> 
 +<code> 
 +type: PolyhedralFan<Rational>
  
-===== 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,code and code output to dokuwiki. 
  
-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> 
 +<code perl> 
 +> $f->VISUAL; 
 +</code>
  
-the table of content based on markdown titles and subtitles (TODOhow extactly)+looks like this till now:
  
-==== What the ipynb2dokuwiki script does====+<code perl> 
 +> $f $s->SECONDARY_FAN; 
 +> $f->properties; 
 +typePolyhedralFan<Rational>
  
-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->VISUAL;
- +
-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&drop. +
- +
-roblems with pypandoc, which converts ipynb markdown to dokuwiki markdown: 1. enumerations? 2. +
-==== Embedded images ==== +
- +
-After conversion the caption "Polymake logo" will be displayed as a tooltip in dokuwiki. {{media:tutorial:jupyter_tutorials:logo.png|Polymake logo}} +
-==== Code and code output ==== +
-<code perl> +
-> application 'polytope'; +
-> # we might need to  +
-> # reconfigure("common::svg.rules"); +
-> # one svg output +
-> svg(cube(3)->HASSE_DIAGRAM->VISUAL); +
-> print "SVG output above"; +
-</code> +
-{{ media:tutorial:jupyter_tutorials:output_0.svg }} +
-<code perl> +
-SVG output above +
-> # multiple svg outputs in a scrollable window +
-> svg(cube(3)->HASSE_DIAGRAM->VISUAL); +
-> svg(cube(3)->HASSE_DIAGRAM->VISUAL); +
-</code> +
-{{ media:tutorial:jupyter_tutorials:output_0.svg }} +
- +
-{{ media:tutorial:jupyter_tutorials:output_0.svg }} +
-<code perl> +
-> # a threejs output +
-> cube(3)->VISUAL;+
 </code> </code>
  • playground/test_jupyter.txt
  • Last modified: 2020/05/11 20:11
  • by hnagel