• View
• Edit
• History
• Print

Subnotebook

< Mujpy.Dashboard | Index | Mujpy._add_multirun_ >

Plans to use https://github.com/davidbrochart/subnotebook/ by davidbrochart

• use a notebook to run mudash, a pure gui based on ipywidget within jupyterlab
• use subnotebook to avoid littering the gui notebook: send all output to a second notebook, in a second displayed jupyterlab tab, as console
• separate execution from ipywidget rendering
  • rendering happens in nb 1, including storing, reading and writing files, conversion from json to iminuit input.
  • musuite mufit mufitplot happens in nb 2
  • fit results must be passed back to nb1 with Return

No other way round:

• a fit is a notebook that
  • runs suite
• opens a second nb by subnotebook that contains the ipywidget gui. Therefore this is standard, always the same.
  • The user plays with the gui to set up the fit, then press fit button.
  • The fit button writes the json, passes plot range, plot=Ture and returns control to the first nb.
  • The fft button in fft tab passes .... fft=True and returns control to the first nb.
  • The multiplot button in multiplot tab passes .... multiplot=True and returns control to the first nb.
  • The plotpar button in plotpar tab passes .... plotpar=True and returns control to the first nb.
• The first nb executes the fit.
• if Return plot=True it executes the fitplot.
• if Return fft=True it executes the fftplot (to be done)
• if Return Multiplot = True multiplot
• if Return Plotpar = True plots parameters
• the nb itself is the log

< Mujpy.Dashboard | Index | Mujpy._add_multirun_ >