Notice: update of the CMP !

89 views
Skip to first unread message

Alessandra Griffa

unread,
Apr 20, 2012, 9:16:47 AM4/20/12
to cmtk-...@googlegroups.com
Dear cmtk-users,

in the new version of DiffusionToolkit (0.6.2), the order by which the voxel dimensions of the reconstructed data are stored in the images' header is changed.
For this reason, we updated the CMP to handle this issue.

You can download the updated CMP from github ( https://github.com/LTS5/ ).

Please, note that the DTB_dtk2dir and DTB_gfa scripts have been re-compiled for linux 64bit only.
If you need the 32bit version please remember to recompile the binaries (you can find instruction in the folder cmp/src/).


Hope this could help!
Alessandra

Qingyang Li

unread,
Apr 20, 2012, 10:13:36 AM4/20/12
to cmtk-...@googlegroups.com
Great news Alessandra!

Just wanted to confirm that this new updated CMP works with both DTK 0.6.2 and earlier version of DTK, right?

Thanks

Yang
------
Qingyang Li

Balance and focus.

Qingyang Li

unread,
Apr 20, 2012, 10:20:46 AM4/20/12
to cmtk-...@googlegroups.com
Also,
 
Does this mean that the CMP before this release doesnot work well with 0.6.2 version of DTK?

Yang 
------
Qingyang Li

Balance and focus.


Alessandra Griffa

unread,
Apr 20, 2012, 10:26:28 AM4/20/12
to cmtk-...@googlegroups.com
Right, it works with both versions.
Alessandra

Alessandra Griffa

unread,
Apr 20, 2012, 10:29:08 AM4/20/12
to cmtk-...@googlegroups.com
Exactly, the 'old' version of the CMP outputs incorrect results from the reconstruction stage on if DTK 0.6.2 is used.

cmpetty

unread,
May 10, 2012, 4:59:11 PM5/10/12
to cmtk-...@googlegroups.com
I tried to install this update on my SL6 machine, but we're only up to boost 1.41, so none of the binaries will execute:
    libboost_program_options.so.1.42.0 => not found

Also, while searching for rpms, i never found a version 1.42 that i could re-compile.  I had to temporarily put off the update until i can sort this out

The previous version used boot 1.40:
    libboost_program_options.so.1.40.0 => /usr/lib64/libboost_program_options.so.1.40.0 (0x0000003ce3000000)

Any suggestions on how to proceed?  I tried symbolically linking  /usr/lib64/libboost_program_options.so.5 as the new version number, but there must've been enough of a difference between the versions for that not to work.

/usr/lib/python2.6/site-packages/cmp/binary/linux2/bit64/DTB_dtk2dir: symbol lookup error: /usr/lib/python2.6/site-packages/cmp/binary/linux2/bit64/DTB_dtk2dir: undefined symbol: _ZN5boost15program_options19options_descriptionC1ERKSsjj

Nicolas Rannou

unread,
May 10, 2012, 5:17:46 PM5/10/12
to cmtk-...@googlegroups.com
Did you try to recompile DTB against boost 1.42?

It's pretty straight forward and we currently run it against boost 1.46.
cd cmp/src/DTB
mkdir build
cd build
cmake ../
  ...
  # make sure the boost directories are correct                                                                                                                                                             
  Boost_INCLUDE_DIR                /usr/include                                                                                                                                                                      
  Boost_LIBRARY_DIRS               /usr/lib                                                                                                                                                                          
  Boost_PROGRAM_OPTIONS_LIBRARY    /usr/lib/libboost_program_options.so
  ...
  # modify the install path
  CMAKE_INSTALL_PREFIX             /chb/users/nicolas.rannou/gitroot/cmp/cmp/binary/linux2/bit64
  ...
make
make install
Hope this helps
Nicolas

cmpetty

unread,
May 11, 2012, 10:04:37 AM5/11/12
to cmtk-...@googlegroups.com
Thanks i did try recompiling, however i got about 9500 lines of errors.

I just captured all the errors and started to look through them and found that the blitz/config.h was looking in the wrong place for the 'blitz/gnu/bzconfig.h' header.

I symbolically linked it to where it was looking, then edited  'Boost_PROGRAM_OPTIONS_LIBRARY'  as you suggested and things compiled fine.

thanks again.

-chris
Reply all
Reply to author
Forward
0 new messages