12 .. :group: Organizations
18 * :ref:`testimonials_open_science`
19 * :ref:`testimonials_standardization`
20 * :ref:`testimonials_vm`
27 :group: Research institutions
29 .. not implemented for now
33 :author: Christian Haselgrove
34 :affiliation: Vice President for Neuroinformatics at
35 Neuromorphometrics, Inc; University of Massachusetts Medical School
37 :tags: email, derivatives, management
39 Developing informatics infrastructure often involves building
40 complex systems that require interaction between existing
41 components such as software and atlases. NeuroDebian makes it
42 trivial to manage the components of these systems, freeing me to
43 focus on the novel and important aspects of my work.
46 Research Software Projects
47 --------------------------
50 :group: Research software projects
54 :author: Stephan Gerhard, et al.
56 :tags: practices, quality
57 :source: The Connectome Viewer Toolkit, Front. Neuroinform. 5:3. doi: 10.3389/fninf.2011.00003
59 For proper software packaging and distribution, the NeuroDebian project provides professional expertise and infrastructure.
62 :author: Chuck Theobald
63 :affiliation: Lewis Center for Neuroimaging, University of Oregon, MRIConvert/mcverter build master and developer
64 :tags: email, impact, software distribution, upstream, dissemination
67 As a system administrator, I support the efforts of a number of
68 researchers who use fMRI analysis software. I was overjoyed to find
69 the NeuroDebian repository, a one-stop shop for nearly every
70 software package the researchers use. The work of the NeuroDebian
71 Team greatly simplifies the task of providing our researchers the
72 best software available, and I consider the repository a vital part
73 of my professional life. As a maintainer on the MRIConvert
74 project, I find that NeuroDebian provides a valuable venue for
75 dissemination of our software. It would not be possible to reach
76 the same wide audience without the NeuroDebian repository.
79 :author: Dr. Kiyotaka Nemoto
80 :affiliation: University of Tsukuba
81 :tags: email, derivatives, time
84 Neurodebian is the best solution for researchers in neuroscience.
85 Everybody should have experienced wasting so much time in just setting
86 up software. With Neurodebian repository, you can easily setup many
87 useful software packages and focus on your research. I recommend this
88 repository to everyone who is interested in using Linux in
92 :author: Dr. Andrew Janke
93 :affiliation: Center for Advanced Imaging, University of Queensland, Australia
95 :tags: email, upstream, stability, versioning, provenance, vm,
96 reproducibility, collaboration
98 We use NeuroDebian on a daily basis as it provides a stable and
99 versioned software base for analysis. This is critical as it allows us
100 to maintain data provenance, something that is often sorely lacking.
101 Our collaborators who don't quite have their heads around Linux yet
102 are pointed to the NeuroDebian Virtual Machine, it allows them to run
103 an identical analysis environment to us regardless of where they are
108 :affiliation: PMP, nitrc.org
110 :tags: disqus, money, quality, contributions, cloud, derivatives
112 NITRC-CE, or the NITRC Computational Environment, on the Amazon
113 Marketplace wouldn't have happened as quickly and thus cost effectively
114 without leveraging NeuroDebian's good works. We appreciate their
115 critical contribution to the neuroimaging compute community.
118 :author: Sebastiaan Mathôt
119 :affiliation: Aix-Marseille université, Laboratoire de Psychologie Cognitive
123 For any neuroscientist that relies on open-source software,
124 NeuroDebian is the single most important resource.
127 :author: Sebastian Eichelbaum
128 :affiliation: OpenWalnut project, Image and Signal Processing Group, Institute of Computer Science, University of Leipzig, Germany
130 :tags: email, breadth, dissemination
132 With NeuroDebian we can utilize thousands of tools, providing the foundation for our research. On the other hand, we can provide our tools to a large community easily.
136 Individual Laboratories and Researchers
137 ---------------------------------------
140 :group: Individual laboratories and researchers
144 :author: Prof. Petr Hlustik
145 :affiliation: Departments of Neurology and Radiology, Palacky University School of Medicine and University Hospital, Olomouc, Czech Republic
149 [...] those wonderful tools in Debian Neuro [...] make my life as a
150 researcher who also maintains a bunch of Debian boxes so much easier.
153 :author: Dr. Jo Etzel
154 :affiliation: Department of Psychology, Washington University
158 I am a dedicated R user ... and have a Windows box. But this
159 afternoon I (finally) downloaded and installed NeuroDebian and the
160 VirtualBox, ran AFNI, and generated the files I needed, all within
161 about an hour and a half. [...] not bad, considering that I know
162 essentially no Linux/Unix. So here's a big "thanks!" :)
165 :author: Vincent Kersten
166 :affiliation: University Medical Center Utrecht
167 :tags: email, standardization, money, Debian
170 Neurodebian provides us with a consitent way of sotware packaging
171 and upgrades, eliminating tedious compiles and home-brew setups,
172 while seamlessly integrating with the Debian distribution. Excellent
173 and very valuable work, saving costs and difficult to spot
174 errors. High five Michael, Yaroslav and team! Keep them packages
178 :author: Christian Stephan-Otto
179 :affiliation: Neuroimaging Research Group, Parc Sanitari Sant Joan de Deu, Barcelona, Spain
181 :tags: email, vm, breadth
183 Since I started using a NeuroDebian virtual machine on win64 months
184 ago I am relying more and more on its diverse tools, from
185 population-specific template creation to pipelining the analysis of
186 fMRI, DTI and morphology studies. There is a great chance I will
187 end up working exclusively with NeuroDebian!
190 :author: Mathias Goldau
191 :affiliation: Cortical Networks, Max-Planck-Institute for neurological research, Cologne, Germany
193 :tags: email, time, breadth
195 Without NeuroDebian we would have wasted precious time for
196 deploying software, and we wouldn't have tested so many software