Skip to content
Commits on Oct 10, 2014
  1. Version bump to 0.1.0.

    committed Oct 9, 2014
  2. Minor cleanup.

    committed Oct 9, 2014
  3. Added a travis yml file.

    committed Oct 9, 2014
Commits on Oct 9, 2014
  1. Spelling.

    committed Oct 9, 2014
Commits on Nov 5, 2012
  1. Changed the defaults.cfg back to original. Need to figure out how to …

    …properly handle the config file.
    committed Nov 4, 2012
  2. Merge pull request #11 from StefenYin/select_runs

    Added select_runs method to the DataSet object.
    committed Nov 4, 2012
Commits on Oct 31, 2012
  1. @StefenYin

    Built select_runs func

    StefenYin committed Oct 31, 2012
Commits on Oct 2, 2012
  1. @StefenYin
  2. @StefenYin

    Updated the default.cfg

    StefenYin committed Oct 1, 2012
Commits on Sep 28, 2012
  1. @StefenYin
Commits on Sep 16, 2012
Commits on Sep 15, 2012
  1. @StefenYin
  2. Mode change.

    committed Sep 15, 2012
Commits on Sep 14, 2012
  1. @StefenYin

    h5_file and defaults_config

    StefenYin committed Sep 13, 2012
Commits on Aug 27, 2012
  1. Updated the readme.

    committed Aug 27, 2012
  2. minor

    committed Aug 27, 2012
Commits on Mar 20, 2012
Commits on Mar 19, 2012
  1. Forcing recalculation of the bicycle parameter data has been turned o…

    …ff for faster loading.
    committed Mar 19, 2012
Commits on Mar 18, 2012
  1. I've added the ability to store the processed task signals in the dat…

    …abase so
    that they can more easily be retrieved. If you load the same trial twice with
    the same filter frequency, then the processed data is pulled from the database
    instead of being computed from the raw data. This speeds things up a lot. But
    it still isn't ideal. It would be better if all of the computed signals
    (calibrated, truncated, computed and task) where stored so that the comple Run
    object could be reconstructed. I'm not sure there is a solution for the
    different filter frequencies, as storing processed data for different filter
    frequencies could grow unbounded. Fixing the filter frequencies for signals
    could could solve this (i.e. not giving the user a choice in filter frequency).
    I've only tried it out on a few cases. Next step is to write some tests for
    this functionality.
    committed Mar 18, 2012
Something went wrong with that request. Please try again.