On Sun, Mar 9, 2014 at 7:23 AM, Yaroslav Halchenko <[email protected]>wrote:
> > On Sat, 08 Mar 2014, David Van Essen wrote: > > > As a quick update, we are aiming for the next workbench release > (v0.85; > > cifti-2 compatibility), including source code, to occur in about a > month. > > That is great -- thanks for the update! > > It would be especially nice if source release would be > accomplished with build(dependencies)/installation instructions, > thorough overview of copyright/licenses for any 3rd party code bundled > in (if any), and (unit)tests battery to verify its correct operation. > You don't ask for much, do you? We do plan to say what the build dependencies are (QT4, configured with the components we use, and OSMesa if you want wb_command -show-scene) and how to build (cmake), and installation shouldn't be picky as long as the libraries as configured for building are found - we don't currently have any preferred method of installation, and it doesn't need to be co-located with any reference data. We can note bundled 3rd party code in some file, maybe in the README? I'm having trouble finding info on how this is usually done. As for unit testing, we have a few tests on some of the simpler classes, but not full unit tests (and testing most of the processing code, such as volume to surface mapping, would require data files). Tim _______________________________________________ HCP-Users mailing list [email protected] http://lists.humanconnectome.org/mailman/listinfo/hcp-users
