<?xml version="1.0" encoding="utf-8"?><!DOCTYPE article  PUBLIC '-//OASIS//DTD DocBook XML V4.4//EN'  'http://www.docbook.org/xml/4.4/docbookx.dtd'><article><articleinfo><title>ScientificComputingUserSurvey</title><revhistory><revision><revnumber>6</revnumber><date>2013-03-07 21:23:01</date><authorinitials>localhost</authorinitials><revremark>converted to 1.6 markup</revremark></revision><revision><revnumber>5</revnumber><date>2009-11-30 11:29:35</date><authorinitials>RhodriCusack</authorinitials></revision><revision><revnumber>4</revnumber><date>2009-11-30 11:11:12</date><authorinitials>RhodriCusack</authorinitials></revision><revision><revnumber>3</revnumber><date>2009-11-30 11:06:05</date><authorinitials>RhodriCusack</authorinitials></revision><revision><revnumber>2</revnumber><date>2009-11-30 11:05:46</date><authorinitials>RhodriCusack</authorinitials></revision><revision><revnumber>1</revnumber><date>2009-11-30 10:56:15</date><authorinitials>RhodriCusack</authorinitials></revision></revhistory></articleinfo><section><title>User Survey Autumn 2009</title></section><section><title>Ratings</title><para><inlinemediaobject><imageobject><imagedata fileref="https://lsr-wiki-01.mrc-cbu.cam.ac.uk/imaging/ScientificComputingUserSurvey?action=AttachFile&amp;do=get&amp;target=usersurvey2009_frequency.jpg"/></imageobject><textobject><phrase>usersurvey2009_frequency.jpg</phrase></textobject></inlinemediaobject> <inlinemediaobject><imageobject><imagedata fileref="https://lsr-wiki-01.mrc-cbu.cam.ac.uk/imaging/ScientificComputingUserSurvey?action=AttachFile&amp;do=get&amp;target=usersurver2009_ratings.jpg"/></imageobject><textobject><phrase>usersurver2009_ratings.jpg</phrase></textobject></inlinemediaobject> </para></section><section><title>Open questions</title><para>The open questions in the form raised a number of issues. These have been categorised, and dealt with as described below. The number of times each item was raised is in parentheses. </para><section><title>Linux servers</title><informaltable><tgroup cols="3"><colspec colname="col_0"/><colspec colname="col_1"/><colspec colname="col_2"/><tbody><row rowsep="1"><entry colsep="1" rowsep="1"><para> <emphasis> issue </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> #comments </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> response/actions </emphasis> </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Speed of storage </para></entry><entry colsep="1" rowsep="1"><para> 4 </para></entry><entry colsep="1" rowsep="1"><para> There is a known issue with the /imaging filesystem. Because of the number of files (100 million+) the directory server has slowed down. We are proposing two responses to this. First, Computing plans to break the /imaging filesystem into parts, with different users in different sections, each of which will be smaller and more manageable. Second, we plan to make two changes to SPM: to make it write 4D files by default, and to stop so many intermediate files being stored </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> RAM </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> This should be dealt with by the new machine pool </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Slow processing </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> A new pool of machines l42-l58 has just been installed. We are furthermore working on a queuing system, likely to be Sun <ulink url="https://lsr-wiki-01.mrc-cbu.cam.ac.uk/imaging/ScientificComputingUserSurvey/imaging/GridEngine#">GridEngine</ulink>, to ensure they do not become overloaded when heavily used </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> 64 bit </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> The new machines are 64 bit </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Software should be updated more regularly </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> The new machines have completely refreshed software, and are configured to auto-update. Some software (e.g., python) may be pulled into separate installations and maintained by the imagers instead of computing, where somebody wishes to take responsibility </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Experimental network </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> This would require substantial investment and will be discussed with the person that requested it. It will become easier with NFS 4 to offer root access to single machines. </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Graphical SVN </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> We will talk to the person that requested this for suggestions </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Linux desktop </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> These can be provided if a good case can be made </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> Prefer Macintosh </para></entry><entry colsep="1" rowsep="1"><para> 2 </para></entry><entry colsep="1" rowsep="1"><para> This is under discussion at the IT strategy group. There are significant resource implications. </para></entry></row></tbody></tgroup></informaltable></section><section><title>PC</title><informaltable><tgroup cols="3"><colspec colname="col_0"/><colspec colname="col_1"/><colspec colname="col_2"/><tbody><row rowsep="1"><entry colsep="1" rowsep="1"><para> <emphasis> issue </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> #comments </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> response/actions </emphasis> </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> USB </para></entry><entry colsep="1" rowsep="1"><para> 6 </para></entry><entry colsep="1" rowsep="1"><para> This was discussed at the last IT strategy group and will be discussed again this time. It is not a scientific computing issue. Memory sticks should be available from Technical Services. </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> admin rights </para></entry><entry colsep="1" rowsep="1"><para> 2 </para></entry><entry colsep="1" rowsep="1"><para> These are now given by default </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> testing desktops &amp; stimulus delivery for fMRI </para></entry><entry colsep="1" rowsep="1"><para> 3 </para></entry><entry colsep="1" rowsep="1"><para> A new machine configuration is being created. One problem is that virus checking needs to be switched off for running experiments, but many people need to transfer data to and from them, meaning they easily catch viruses. Options are a dual log-in system, or a gateway machine for file transfer. It was suggested that as has recently been done for the imaging system, particular people are made responsible for particular pieces of software, notably E-prime, Presentation, Psychtoolbox, <ulink url="https://lsr-wiki-01.mrc-cbu.cam.ac.uk/imaging/ScientificComputingUserSurvey/imaging/PsyScope#">PsyScope</ulink>,DMDX, VB.net, VB6 </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> RAM </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> Where a case can be made a new machine will be provided </para></entry></row></tbody></tgroup></informaltable></section><section><title>Training &amp; support</title><informaltable><tgroup cols="3"><colspec colname="col_0"/><colspec colname="col_1"/><colspec colname="col_2"/><tbody><row rowsep="1"><entry colsep="1" rowsep="1"><para> <emphasis> issue </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> #comments </emphasis> </para></entry><entry colsep="1" rowsep="1"><para> <emphasis> response/actions </emphasis> </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> it would be helpful to have formal training </para></entry><entry colsep="1" rowsep="1"><para> 3 </para></entry><entry colsep="1" rowsep="1"><para> We will consider this for the next intake in 2010 </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> it-help does not answer queries </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> Computing are busy and have a broad range of enquiries of varying urgency. However, they will endeavour to remove the backlog </para></entry></row><row rowsep="1"><entry colsep="1" rowsep="1"><para> sexism </para></entry><entry colsep="1" rowsep="1"><para> 1 </para></entry><entry colsep="1" rowsep="1"><para> The importance of guarding against this was agreed with the computing group </para></entry></row></tbody></tgroup></informaltable></section></section></article>