Mach 30 #EngineerSpeak Hangout Aug 06, 2015
Discussion Topic: Sprint 2 Stand Up 2
Attending: J, Chris, Jeremy, Juli,
Start: 2205 Eastern
End: 2235 Eastern
Summary:
Working through various challenges moving from Sage to IPython. Results are promising but there are critical export issues to resolve.
Minutes:
- Did - Drafted two demo notebooks (format test & units test); format test shows the exported PDF has report like section numbering and PDF bookmarks; units test shows exported PDF does not pick up the Python Markdown output; both tests combined demonstrate the PDF export engine is pretty far removed from the notebook rendering engine; clearly we need to address the lack of value from the Python Markdown; do we need to also address the lack of section numbering in the notebooks?
- Chris - at some point we will need to fix the section numbers not rendering in the notebooks, but not right now (we are the only users)
- Jeremy - would be nice if the section numbers showed up, and clearly the calculated values need to show up
- J - ditto
- Will do - Investigate how the PDF export works in an attempt to get similar results in the PDF export as the Python Markdown did for the notebook rendering
- Blocks? - not yet (need to see how the PDF export works)
- Did -
- Will do -
- Blocks? -
- Did - worked on the MTK Linux install script, last test showed that it installed all of the extensions, the PDF export, Pint, etc; was able to open J’s test notebooks and get the same results as J
- Will do - next pass at installer per conversation below (/opt and config.js stuff)
- Blocks? - don’t think there are any
- Did - didn’t really do anything
- Will do - will also look at why the PDFs are not getting the calculated values in markdown cells (piling on with J; part of MTK-07)
- Blocks? - none
- ---
- J - want to also discuss installing notebook extensions in a shared location and setting up a template config file to pre-load the ones we need…
- J - unlike a lot of IPython notebook users, we are not configuring notebook extensions here and there; the ones we are setting up are required to make MTK go, so we need to have a common location to keep everything straight
- Chris - that makes sense
- Jeremy - http://stackoverflow.com/questions/27263620/how-to-install-anaconda-python-for-all-users
- <some discussion about long term installation plans - MTK using its own anaconda vs more of a required packages approach and using system copies of anaconda, etc>
- J - also think we should edit the template for config.js to point at the common extensions path (if needed) and to load the required MTK extensions (Python Markdown for example)