-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make whole database run up to centerlines step #15
Comments
You could also create a directory, name for example |
francoisdh
added a commit
that referenced
this issue
Jun 22, 2016
- renamed *.py scripts to *.py.in. - edited all these scripts and replaced hardcoded paths by cmake variables - edited CMakeLists.txt to add installation instructions for these scripts. **About issue #14 (changes in master.py.in and createAsciidocDB.py.in) For a given run, we have several informations: date and time, database, system, user, python/paraview versions, number or found/processed files, number of complete/incomplete/failed reconstructions, total time and a link to the run's results html page For a given pipeline step: -> (i.e a table cell), 'success' variable is used to color background (which means a red cell indicates a failed step.) -> the complete command is included in plain text -> execution times are rounded to the thousandth **About issue #13 (changes in master.py.in and creation of createAsciidocSummary.py.in) A new, global table is produced (asciidoc+html), summarizing runs. - Runs are identified by their date and time of execution. For each run: - We present system informations, statistics and a link to the run's results page. ** About issue #15 (slight changes in master.py.in and creation of Examples/MeshFromMRI/generic/rorpo.cfg) - Whole databases can be processed (e.g. /data/vivabrain) via master.py --inputpath. - The generic directory is now used as a default directory for .cfg files. For now, only rorpo.cfg is present. - Therefore, the whole database can only be run up to the RORPO step.
is it done ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: