+load it with PyYAML_::
+
+ $ python
+ >>> import yaml
+ >>> import hooke.util.yaml
+ >>> mylist = yaml.load(open('mylist.hkp', 'r'))
+
+navigate to your curve,::
+
+ >>> mylist.jump(1234)
+
+and extract your parameter.::
+
+ >>> mylist.current().data[1].info['polymer peak 0']['contour length (m)']
+ 2.124...e-08
+
+You can also get a list of all available parameters::
+
+ >>> mylist.current().data[1].info['polymer peak 0'].keys()
+ ['model', 'contour length (m)', 'temperature (K)', 'fit',
+ 'persistence length (m)']
+
+or just pprint_ the whole thing::
+
+ >>> from pprint import pprint
+ >>> pprint(mylist.current().data[1].info['polymer peak 0'])
+ {'contour length (m)': 2.1248220207858103e-08,
+ 'fit': {'active fitted parameters': 3.7024307200788127,
+ 'active parameters': 3.7024307200788127,
+ 'convergence flag': 1,
+ 'covariance matrix': None,
+ 'data scale factor': 5.2716380732198972e-10,
+ 'fitted parameters': -2.5663294148411571,
+ 'info': {'fjac': None,
+ 'fvec': None,
+ 'ipvt': None,
+ 'nfev': 16,
+ 'qtf': None},
+ 'initial parameters': [-0.69314718055994529],
+ 'message': 'Both actual and predicted relative reductions in the sum of squares\n are at most 0.000000',
+ 'rescaled': True,
+ 'scale': None},
+ 'model': u'WLC',
+ 'persistence length (m)': 4.0000000000000001e-10,
+ 'temperature (K)': 301.0}
+
+.. _PyYAML: http://pyyaml.org/
+.. _pprint: http://docs.python.org/library/pprint.html
+
+.. todo:: UI access to block (and curve?) info dicts. Someone should
+ make a tree-based object browser ;).
+
+.. todo:: Playlists currently drop all :class:`~hooke.curve.Data`
+ instances when they are unloaded, so you can't extract the fitted
+ parameters from unloaded curves. We'll need a way to export chosen
+ curve attributes to file.
+
+Command stacks
+~~~~~~~~~~~~~~
+
+Since you are likely to apply similar analysis to several curves,
+Hooke provides :mod:`command stacks <hooke.command_stack>` for
+bundling groups of commands.::
+
+ hooke> start_command_capture
+ hooke> zero_surface_contact_point --block retract
+ hooke> flat_filter_peaks --block retract --min_points 1
+ ...
+ hooke> stop_command_capture
+
+You can check the state of the command stack with
+``get_command_stack`` and the state of capture with
+``get_command_capture_state``. If you make mistakes, you can pop
+commands from the stack with ``pop_command_from_stack``. If you stop
+capturing a command stack (e.g. to test a complicated command before
+continuing), you can continue adding to the same stack with
+``restart_command_capture.``
+
+To execute a command stack, run::
+
+ hooke> execute_command_stack
+
+To execute a command stack on every curve in a playlist, run::
+
+ hooke> apply_command_stack_to_playlist
+
+If you decide that there are commands in a curve's stack that you
+don't want, you can clear the stack with::
+
+ hooke> clear_curve_command_stack
+
+You can also save command stacks to disk (and reload them later,
+potentially in a different Hooke session).::
+
+ hooke> save_command_stack --output my_stack
+ hooke> load_command_stack --input my_stack