Skip to content

Conversation

satra
Copy link
Member

@satra satra commented Nov 17, 2012

No description provided.

* master: (106 commits)
  Doctest fix, better error reporting.
  fix: config updated before checking for deprecated options
  put back the n_procs docs
  Udated docs with n_procs for MultiProc
  DOC: Improve docstring for DataFinder, include example usage.
  fix: adding atlases
  fix: removing recommends
  fix: restore fsl
  fix: remove fsl for now
  fix: variable name
  fix: use neurodebian sources
  fix: add missing nibabel
  fix: install nibabel in python dir
  fix: remove easy_install suffix
  fix: testing sklearn travis fix
  BF: Fixes for last commit
  BF: Use ignore regexes instead of functions so they can pickle.
  ENH: Added DataFinder interface.
  added cmdline example
  pep8
  ...
@satra
Copy link
Member Author

satra commented Dec 8, 2012

@chrisfilo, @mwaskom : ready for review

@chrisgorgo
Copy link
Member

Please describe "stop_on_unknown_version" option in the documentation.

How hard would it be to add the following two options (related):

  1. save version at runtime in reports/prov
  2. give an option to force rerun interfaces if version change has been detected.

satra added 2 commits December 9, 2012 14:08
* master:
  fix: deprecation warning does not reset trait to Undefined - will set new value
  add support for template files
  API fix for somaworkflow
  PEP8
  Further refactoring
  Reafactoring - less redundant code between SGE and PBS.
  Respect custom execution parameters in graph based models.
  DOC: Added docstring for MpiCommandLine with example usage.
  ENH: Provide base interface for MPI capable command line software.
@satra
Copy link
Member Author

satra commented Dec 9, 2012

  1. saving version does happen with the prov branch, this now allows an explicit version for each underlying interface. (i'll make sure this is cleaned up in the prov pr).
  2. rerunning based on versions gets tricky - for example, when spm runs do you want to rerun based on spm version or matlab version or both? and in the extreme, do you want the version of the underlying libraries to also trigger reruns? i think these are questions we don't have a good answer to right now but we want to design a system that allows us to consider these options - different levels of rerunning. (again, i think this should be a different pr).

* master:
  fix: doctest carriage return
@mwaskom
Copy link
Member

mwaskom commented Dec 12, 2012

Cool! Looks good.

chrisgorgo added a commit that referenced this pull request Dec 17, 2012
added versioning to traits and interfaces
@chrisgorgo chrisgorgo merged commit dc1e3e5 into nipy:master Dec 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants