There have been some off-list messages on this thread, and I wanted to share this:
Tim Coalson wrote: > ... it seems that the previous generation on-CPU graphics didn't have this > problem. The newer generation having this problem with the same code seems > like the driver might be the culprit - ensure you have the latest graphics > drivers. If it still occurs, perhaps we could contact intel and let them > know of the problem. They might just brush it off (caret5 is using an old > version of openGL), but you never know. Jon Schindler wrote: > As Tim says, one factor is that they are underpowered compared to discrete > graphics cards. However, another factor is that since Intel's attempt to > make a GPU is relatively recent, and they aren't trying to support high-end > legacy applications (professional OpenGL applications), they may not have > optimized the version of OpenGL that we use, which is fairly outdated, and > used primarily in expensive legacy OpenGL applications. Most consumer OpenGL > apps, which are Intel's target market, tend not to require extremely fast > OpenGL 2.x support (as they've moved on to OpenGL 3.x+), so we may be > witnessing some slowdowns due to the version of OpenGL we are using. Make sure your graphics card driver is up-to-date. It would be nice to know whether that helps any of the three we know experiencing this problem. (Also, whether anyone is seeing it on a platform other than windows.) On Aug 7, 2013, at 11:45 AM, Donna Dierker <[email protected]> wrote: > I have emailed nicky, the first one who reported this issue, to see what > graphics card she was using when she ran into this. > > Hopefully Steven is still tuned into this thread. > > This information is most helpful, Wouter. Thank you much for posting these > details. > > > On Aug 6, 2013, at 12:51 PM, "Schellekens, W." <[email protected]> > wrote: > >> Hi, >> >> I'd like to contribute to this topic, although I'm not sure of what use >> it'll be... >> >> I'm experiencing the slowdown as well on a new windows 7 64bit machine. But >> I may have found a reason why. >> >> I used to be able to use Caret v5.65 on my older windows 7 64bit laptop just >> fine. The main difference between that older laptop and my current one is >> the processor. The older one was a 2nd gen intel i3, and the current one is >> a 3th gen intel i7. Except for having higher clock rate now, something else >> has changed as well: the onboard graphics processor from HD3000 to HD4000. >> In addition to the onboard intel graphics chip, I also have a low-end Nvidia >> Geforce 610M graphics chip, which performance is quite similar to the HD4000. >> >> Now, I still have the exact copy of Caret v5.65 I installed on the 2nd gen >> i3, and installed that one on my current system. When I'm using the HD4000 >> graphics chip, Caret runs horrendously slow (editing voxels, node IDs, right >> mouse button, etc.). However, when I change to the Nvidia chip, Caret runs >> fine. My best guess is, that Caret and the HD4000 chip don't play nice >> together. >> >> It would be interesting to see, if the other guys that experience slowdowns >> are using the HD4000 chip as well. >> Hopefully, this has helped someone. >> Cheers, >> >> Wouter Schellekens >> -------------------------------------------------------------------------------------- >> Brain Center Rudolf Magnus >> Neurology & Neurosurgery, Brain Division, UMC Utrecht >> Postal address: Str. 4.205, Postbus 85060, 3508 AB, Utrecht >> Visit: Str. 4.115, Universiteitsweg 100, 3584 CG, Utrecht >> E-mail: [email protected] >> >> >> ________________________________________ >> Van: [email protected] >> [[email protected]] namens Donna Dierker >> [[email protected]] >> Verzonden: maandag 5 augustus 2013 21:00 >> Aan: Caret, SureFit, and SuMS software users >> Onderwerp: Re: [caret-users] Voxel editing slowdown? >> >> We can rule out volume size as an issue, then. >> >> Both complaints along these lines came from Windows users. >> >> The only other idea that comes to mind (okay, delivered by another user) is >> trying the neurodebian virtual machine. See if voxel editing is more >> responsive that way. >> >> Apart from editing in another software package like MRIcron, and then >> prepare for flattening using the steps near the bottom of this page: >> >> http://brainvis.wustl.edu/help/peak_tweaking/ >> >> I wish I knew of a quick fix. >> >> >> On Aug 5, 2013, at 12:42 PM, Steven Lu <[email protected]> wrote: >> >>> Thank you for the reply! >>> >>> I am indeed running Windows (7 Professional 64-bit). I get similar delays >>> when opening the Identify Window after clicking anywhere on my image. The >>> dimensions of my volume are 78x182x128 (right hemisphere), but I get the >>> same slowdown with the Identify Window regardless of the volume used >>> (likely the same effect with voxel editing. >>> >>> Best, >>> Steven >>> >>> On Mon, Aug 5, 2013 at 8:02 AM, Donna Dierker <[email protected]> >>> wrote: >>> See this thread: >>> >>> http://www.mail-archive.com/[email protected]/msg02842.html >>> >>> Are you running Caret on Windows, too? >>> >>> Out of curiosity, what are the dimensions of the segmentation volume you >>> are editing? >>> >>> >>> On Aug 4, 2013, at 8:45 PM, Steven Lu <[email protected]> wrote: >>> >>>> Hi, I've been working on segmentation and the voxel editing tools (mainly >>>> Turn Voxels On and Turn Voxels Off) show very delayed responses (about 2 >>>> seconds after clicking). I'm wondering if anybody else has experienced >>>> this and, if so, what can be done about it? >>>> _______________________________________________ >>>> caret-users mailing list >>>> [email protected] >>>> http://brainvis.wustl.edu/mailman/listinfo/caret-users >>> >>> >>> _______________________________________________ >>> caret-users mailing list >>> [email protected] >>> http://brainvis.wustl.edu/mailman/listinfo/caret-users >>> >>> _______________________________________________ >>> caret-users mailing list >>> [email protected] >>> http://brainvis.wustl.edu/mailman/listinfo/caret-users >> >> >> _______________________________________________ >> caret-users mailing list >> [email protected] >> http://brainvis.wustl.edu/mailman/listinfo/caret-users >> >> ------------------------------------------------------------------------------ >> >> De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is >> uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht >> ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct >> te informeren door het bericht te retourneren. Het Universitair Medisch >> Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de >> W.H.W. >> (Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd >> bij >> de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197. >> >> Denk s.v.p aan het milieu voor u deze e-mail afdrukt. >> >> ------------------------------------------------------------------------------ >> >> This message may contain confidential information and is intended exclusively >> for the addressee. If you receive this message unintentionally, please do not >> use the contents but notify the sender immediately by return e-mail. >> University >> Medical Center Utrecht is a legal person by public law and is registered at >> the Chamber of Commerce for Midden-Nederland under no. 30244197. >> >> Please consider the environment before printing this e-mail. >> >> _______________________________________________ >> caret-users mailing list >> [email protected] >> http://brainvis.wustl.edu/mailman/listinfo/caret-users > > > _______________________________________________ > caret-users mailing list > [email protected] > http://brainvis.wustl.edu/mailman/listinfo/caret-users _______________________________________________ caret-users mailing list [email protected] http://brainvis.wustl.edu/mailman/listinfo/caret-users
