FIX fileIO.flist file matching
FIX fileIO.flist file matching
fileIO: fix comment parsing of key no value
experiment: turn off warning for filenames duuring loading
Merge branch 'feature-refolding' of github.com:cfperez/smbanalyze into feature-refolding
ADD calibration IPython notebook
Merge branch 'master' into feature-refolding

Adding IPython notebook folder and calibration notebook
FEATURE fitting with fec module

Moving some functionality out of experiment.py and into
fec module for fitting WLC and rips of pulling data.

Trying to take a more functional approach, passing data around
and using module function to operate on it, leaving things
like experiment.Pulling to shuttle data around.

Should that object also have things like rips added to it?
For example,

    mol.rips = fec.Rips(...) ??

This would keep all the results in one place, while keeping
the Pulling object clean of excessive methods.

TODO: remove duplication from curvefit.py and experiment.py

	modified:   browser.py
	modified:   datatypes.py
	modified:   experiment.py
	new file:   fec.py
	new file:   shell.py
Merge branch 'feature-refolding'

Incorporating improvements to FEC fitting using masks. Allows more
accurate fitting at low force with overlapping rips.

Also moving towards a less complex OO paradigm. Experiment objects
are becoming data structures with helper methods to do certain tasks.
This should simplify the addition of new functions, since these will
take trap data, fret data, or at most, the experiment object itself.

Open question: besides the usual metadata, should the experiment
data structures also be used to house results of calculations? Or is
it simply an object for transfering data around? The benefit of using
it as the single point for storing relevant info is that it will be
easier to use interactively.