Freesurfer

freesurfer@nmr.mgh.harvard.edu

1 participants
30089 discussions

analyzeto4dfp to get a talsrcimg.4dfp.ifh file
by Jeff Thompson 14 Aug '12

14 Aug '12

Hi,I have run talairach_avi with the template I have made, and an input file that is manually skull stripped. I ran: talairach_avi --i <input>.nii.gz --atlas <avgeragetemplate> --xfm talairach_avitest.xfmI had put the <averagetemplate>.nii.gz file in the average folder in freesurfer for this to work. I also have <averagetemplate>.4dfp.hdr , <averagetemplate>.4dfp.img , <averagetemplate>.4dfp.mat in the average folder.Running this creates talsrcimg.hdr, talsrcimg.img, talsrcimg.mat in the folder where I ran the script. However in the talairach_avi log it gives an error saying /Applications/freesurfer/average/<averagetemplate>.4dfp.ifh does not exist! How can I create this file?I found a brief note in a mailing list that mentioned analyzeto4dfp talsrcimg -O0 -y:$Id: ifh2hdr.c,v 1.3 2007/05/05 10:45:03 nicks Exp $ Sat Dec 31 03:27:10 2011 Writing: talsrcimg.4dfp.hdr $Id: analyzeto4dfp.c,v 1.2 2007/05/05 00:00:06 nicks Exp $ Reading: talsrcimg.hdr header size 348 bytes hdr.dime.datatype offset=70 value=2 hdr.dime.bitpix offset=72 value=8 hdr.hist.orient offset=252 value=-1 dimensionality 4 dimensions 256 256 256 1 Reading: talsrcimg.img Writing: talsrcimg.4dfp.img Writing: talsrcimg.4dfp.ifh ifh2hdr talsrcimg -r0to255 ori=2 However, I don't know what I need to run this. Will I need to install analyze and 4dfp to be able to run analyzeto4dfp? Or is there another way to get this <averagetemplate>.4dfp.ifh file?Thanks,-Jeff

1 0

Re: [Freesurfer] Creating and using an atlas from scratch‏
by Jeff Thompson 14 Aug '12

14 Aug '12

1 0

Re: [Freesurfer] mri_cnr
by prasser 14 Aug '12

14 Aug '12

Hi, I was wondering if there is any documentation on mri_cnr, particularly how the noise is calculated. Thank you, Paul > > thanks Dr. B.....that helped a lot > > ----- Original Message ----- > From: "Bruce Fischl" <fischl(a)nmr.mgh.harvard.edu> > To: "Kushal Kapse" <kkapse(a)mail.med.upenn.edu> > Cc: "freesurfer" <freesurfer(a)nmr.mgh.harvard.edu> > Sent: Monday, June 18, 2012 2:27:29 PM > Subject: Re: [Freesurfer] mri_cnr > > Hi KK > > this is something i wrote for myself, but you are welcome to try it out. > YOu don't need to give it the slope stuff, that is optional. The "vol" > command line parms are the volumes that you want to assess CNR in. For > example: > > mri_cnr ~/local_subjects/bruce/surf ~/local_subjects/bruce/mri/norm.mgz > processing MRI volume /homes/4/fischl/local_subjects/bruce/mri/norm.mgz... > white = 95.8+-9.7, gray = 65.3+-17.9, csf = 40.1+-17.2 > gray/white CNR = 2.241, gray/csf CNR = 1.026 > lh CNR = 1.633 > white = 95.7+-9.9, gray = 65.5+-17.8, csf = 41.5+-17.4 > gray/white CNR = 2.205, gray/csf CNR = 0.937 > rh CNR = 1.571 > total CNR = 1.602 > > > On Mon, > 18 Jun 2012, Kushal Kapse wrote: > > > hi fellas, > > > > i am trying to run mri_cnr command in freesurfer to compute and see CNR for gray/white/csf.... the command gives following info as help: > > > > -bash-3.2$ mri_cnr > > usage: mri_cnr [options] <surf directory> <vol 1> <vol 2> ... > > -s <slope fname> <dist in> <dist out> <step in> <step out> > > > > > > i understand that 'surf directory'= subjects 'surf' folder ; but i am not able to figure out what it means by vol1, vol2 and slope fname......it doesnt show any error but just doesnt do anything even if i mention the surf directory to this command..... > > > > i checked on freesurfer mail archive, but no info since 2009 about any update on this command..... > > > > may someone please give an info if anyone ever used this command > > > > > > thanks > > kk > > _______________________________________________ > > Freesurfer mailing list > > Freesurfer(a)nmr.mgh.harvard.edu > > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > > > > > > > _______________________________________________ > Freesurfer mailing list > Freesurfer(a)nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > > > The information in this e-mail is intended only for the person to whom it is > addressed. If you believe this e-mail was sent to you in error and the e-mail > contains patient information, please contact the Partners Compliance HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to you in error > but does not contain patient information, please contact the sender and properly > dispose of the e-mail. > > _______________________________________________ > Freesurfer mailing list > Freesurfer(a)nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >

2 1

Problems with ICV
by Wisse, L.E.M. 14 Aug '12

14 Aug '12

Dear freesurfers, I tried to calculate ICV with FreeSurfer, but I encountered some problems. I first ran autorecon 1, 2 and 3, but I noticed afterwards that a few ICV values were really off. The values were really high and when I looked at brain.finalsurfs.mgz, the segmentation also included skull, eyes and sometimes even the nose and ears. (I am not sure that I should look at the brainfinal.surfs.mgz for ICV segmentation, but the segmentations seemed to correlate with the ICV values.) So, I decided to try adjusting the watershed parameters and I also tried using gcut. I noticed that the segmentation brain.finalsurfs improved a lot, however in aseg.stats the ICV values did not change at all! Can anyone help me with this problem? Kind regards, Laura Wisse ------------------------------------------------------------------------------ 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.

3 4

longitudinal analysis: rate of change
by Shannon Kogachi 13 Aug '12

13 Aug '12

Hi, I had a question about the rate of change (thickening in mm/year) for the longitudinal processing. How is this value calculated when there are more than two timepoints per subject? Thank you! -Shannon K.

2 1

Radial Distance from Tessellated Hippocampus Surface
by Jared Saletin 13 Aug '12

13 Aug '12

Hi Freesurfer folks, I was wondering if anyone knew an automated or semi-automated method for calculating radial distance along the longitudinal axis of the hippocampus from a surface generated by tessellating the segmentation from aseg. I know radial distance is used to examine local changes in morphology in cases such as aging and dementia - I was curious if there anyone has done so using the freesurfer Hipp segmentation as the starting point. Thanks so much! Jared

1 0

Tracula: pathway #7
by Chris Watson 13 Aug '12

13 Aug '12

Hello, When I go through trac-prep, pathway #7 always takes much much longer than any of the others. And for that pathway it always displays this: INFO: Distances between consecutive points are 34 37 34 40 WARN: Could not find satisfactory control point fit - try 90 Has anyone else had this problem? Visually, they look right to me. Thanks, Chris

2 1

Re: [Freesurfer] Freesurfer Digest, Vol 102, Issue 10
by Linda Douw 13 Aug '12

13 Aug '12

Hi Doug, I first parcellate fsaverage5 using ico4 (all my functional data are morphed to fsaverage5 surface): mris_make_face_parcellation /fsaverage5/rh.inflated $FREESURFER_HOME/lib/bem/ic4.tri rh.ico4.annot Then I extract the waveforms using mri_segstats mri_segstats --i rh.functional.nii.gz --avgwf rh_ico4.txt --annot fsaverage5c rh ico4 --sum ico4_rh.sum Hope this clarifies the problem! Linda > ------------------------------ > > Message: 25 > Date: Fri, 10 Aug 2012 11:18:38 -0400 > From: Douglas N Greve <greve(a)nmr.mgh.harvard.edu> > Subject: Re: [Freesurfer] ico4 parcellation and mri_segstats > To: freesurfer(a)nmr.mgh.harvard.edu > Message-ID: <5025264E.3030801(a)nmr.mgh.harvard.edu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > what are your command lines? > doug > > On 08/09/2012 01:21 PM, Linda Douw wrote: >> Dear Freesurfers, >> >> I'm trying to extract the average waveforms from all 2562 ROIs in an >> annotation constructed using mris_make_face_parcellation with ico4. >> However, I get only 2460 waveforms after doing mri_segstats, and the >> summary files show that several ROIs are 'skipped' for some reason. Am I >> missing something? >> >> Thanks, >> > > -- > Douglas N. Greve, Ph.D. > MGH-NMR Center > greve(a)nmr.mgh.harvard.edu > Phone Number: 617-724-2358 > Fax: 617-726-7422 > > Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting > FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html > > > > ------------------------------ > > _______________________________________________ > Freesurfer mailing list > Freesurfer(a)nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer > > End of Freesurfer Digest, Vol 102, Issue 10 > ******************************************* > > >

2 1

polar angle analysis with clockwise- and counterclockwise-rotating wedges
by Thomas Janssens 13 Aug '12

13 Aug '12

Hi, I am currently analyzing some retinotopy data. For the polar angle stimulus we had both clockwise and counterclockwise stimuli. Both of them started at the top of the screen (12 o'clock), each run includes 4 full cycles and ends with the last wedge slightly before/after 12o'clock. We have created seperate paradigm files (direction pos / direction neg) for the clockwise and counterclockwise runs and followed the steps as indicated by the "FsFastIndividualRetinotopyAnalysis". However, when we run the Freesurfer retinotopy analysis on the whole data set, the polar angle is very noisy. When we run the same analysis separately for the clockwise and counterclockwise runs separately, the results look much better. Could anyone tell me what I am doing wrong? Thanks! Thomas

2 6

Re: [Freesurfer] memory corruption when performing mri_segstats
by Douglas N Greve 13 Aug '12

13 Aug '12

Hi Wenjing, I don't know what is happening either . Can you tar up the aparc+aseg.nii.gz and filtered_func_data.nii.gz file can send them to me on our file drop? www.nmr.mgh.harvard.edu/facility/filedrop/index.html <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> thanks doug On 08/13/2012 04:59 AM, Wenjing Li wrote: > Dear Doug, > > Sorry for the late response. Thanks for your quick reply. > Same errors happened for all of my data. There is an empty output > file. I don't know what's going on. > > All the best, > Wenjing > > On 9 August 2012 23:07, Douglas N Greve <greve(a)nmr.mgh.harvard.edu > <mailto:greve@nmr.mgh.harvard.edu>> wrote: > > Does this happen on all of your data sets or just this one? Did it > create the output file? If so, does it have anything in it? > doug > > > On 08/09/2012 07:14 AM, Wenjing Li wrote: > > Hi Freesurfer experts, > > I want to extract time courses according to: > > https://mail.nmr.mgh.harvard.edu/pipermail//freesurfer/2010-July/015091.html > > Previous steps work fine, but memory corruption happened when > I perform the command line (I have a 12 GB memory): > > mri_segstats --seg SUBID.feat/reg/freesurfer/aparc+aseg.nii.gz > --in SUBID.feat/filtered_func_data.nii.gz --avgwf file.dat > > > I pasted the errors below: > > $Id: mri_segstats.c,v 1.75.2.2 2011/04/27 22:18:58 nicks Exp $ > cwd > cmdline mri_segstats --seg > /mnt/workspace/subid.feat/reg/freesurfer/aparc+aseg.nii.gz > --in /mnt/workspace/subid.feat/filtered_func_data.nii.gz > --avgwf /mnt/workspace/subid.feat/file.dat > > sysname Linux > hostname fmri-Canlab > machine x86_64 > user wenjing > Loading /mnt/workspace/subid.feat/reg/freesurfer/aparc+aseg.nii.gz > Loading /mnt/workspace/subid.feat/filtered_func_data.nii.gz > Voxel Volume is 70.3125 mm^3 > > Generating list of segmentation ids > Found 109 segmentations > Computing statistics for each segmentation > 0 0 96808 6.80682e+06 > 1 2 3101 218039 <tel:3101%20%20218039> > 2 4 59 4148.44 > 3 5 3 210.938 > > 4 7 152 10687.5 <tel:7%20%20%20%20152%20%2010687.5> > 5 8 816 57375 > 6 10 116 8156.25 > 7 11 62 4359.38 > 8 12 114 8015.63 > 9 13 26 1828.13 > 10 14 13 914.063 > 11 15 30 2109.38 > > 12 16 257 18070.3 > 13 17 75 5273.44 > 14 18 31 2179.69 > 15 24 19 1335.94 > 16 26 11 773.438 > 17 28 60 4218.75 > 18 31 12 843.75 > 19 41 3163 222399 > > 20 43 37 2601.56 > 21 44 3 210.938 > 22 46 155 10898.4 > 23 47 789 55476.6 > 24 49 110 7734.38 > 25 50 65 4570.31 > 26 51 105 7382.82 <tel:51%20%20%20%20105%20%207382.82> > 27 52 24 1687.5 > > 28 53 75 5273.44 > 29 54 26 1828.13 > 30 58 9 632.813 > 31 60 59 4148.44 > 32 63 17 1195.31 > 33 77 19 1335.94 > 34 251 12 843.75 > 35 252 5 351.563 > > 36 253 5 351.563 > 37 254 6 421.875 > 38 255 15 1054.69 > 39 1000 38 2671.88 > 40 1001 57 4007.81 > 41 1002 34 2390.63 > 42 1003 121 8507.82 > 43 1005 43 3023.44 > > 44 1006 24 1687.5 > 45 1007 157 11039.1 > 46 1008 263 18492.2 > 47 1009 170 11953.1 > 48 1010 35 2460.94 > 49 1011 170 11953.1 > 50 1012 123 8648.44 > 51 1013 121 8507.82 > > 52 1014 74 5203.13 > 53 1015 265 18632.8 > 54 1016 38 2671.88 > 55 1017 55 3867.19 > 56 1018 64 4500 > 57 1019 33 2320.31 > 58 1020 61 4289.06 > 59 1021 33 2320.31 > > 60 1022 201 14132.8 > 61 1023 49 3445.31 > 62 1024 236 16593.8 > 63 1025 189 13289.1 > 64 1026 32 2250 > 65 1027 256 18000 > 66 1028 379 26648.4 > 67 1029 214 15046.9 > > 68 1030 205 14414.1 > 69 1031 205 14414.1 > 70 1032 13 914.063 > 71 1033 29 2039.06 > 72 1034 21 1476.56 > 73 1035 104 7312.5 > 74 2000 37 2601.56 > 75 2001 58 4078.13 > > 76 2002 24 1687.5 > 77 2003 120 8437.5 > 78 2005 46 3234.38 > 79 2006 33 2320.31 > 80 2007 147 10335.9 > 81 2008 314 22078.1 > 82 2009 190 13359.4 > 83 2010 40 2812.5 > > 84 2011 195 13710.9 > 85 2012 112 7875 > 86 2013 111 7804.69 > 87 2014 54 3796.88 > 88 2015 215 15117.2 > 89 2016 39 2742.19 > 90 2017 59 4148.44 > 91 2018 63 4429.69 > > 92 2019 39 2742.19 > 93 2020 79 5554.69 > 94 2021 38 2671.88 > 95 2022 189 13289.1 > 96 2023 55 3867.19 > 97 2024 211 14835.9 > 98 2025 153 10757.8 > 99 2026 35 2460.94 > > 100 2027 264 <tel:100%20%20%202027%20%20%20%20264> 18562.5 > 101 2028 369 <tel:101%20%20%202028%20%20%20%20369> 25945.3 > 102 2029 225 <tel:102%20%20%202029%20%20%20%20225> 15820.3 > 103 2030 221 <tel:103%20%20%202030%20%20%20%20221> 15539.1 > 104 2031 202 <tel:104%20%20%202031%20%20%20%20202> 14203.1 > 105 2032 13 914.063 > 106 2033 35 2460.94 > 107 2034 17 1195.31 > > 108 2035 110 <tel:108%20%20%202035%20%20%20%20110> 7734.38 > > Reporting on 109 segmentations > Computing spatial average of each frame > 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 > 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 > > 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 > 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 > 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 > 100101102103104105106107108 > > Writing to /mnt/workspace/subid.feat/file.dat > *** glibc detected *** mri_segstats: malloc(): memory > corruption: 0x34775428 *** > ======= Backtrace: ========= > /lib32/libc.so.6(+0x6c231)[0xf750d231] > /lib32/libc.so.6(+0x6f065)[0xf7510065] > > /lib32/libc.so.6(__libc_malloc+0x5c)[0xf7511c6c] > /lib32/libc.so.6(+0x5d01f)[0xf74fe01f] > /lib32/libc.so.6(fopen64+0x2c)[0xf750068c] > mri_segstats(vfprintf+0x3e9e)[0x80526d6] > /lib32/libc.so.6(__libc_start_main+0xe6)[0xf74b7bd6] > > mri_segstats(__gxx_personality_v0+0x1c9)[0x804f791] > ======= Memory map: ======== > 08048000-087f2000 r-xp 00000000 00:00 0 > 087f2000-2e568000 rwxp 00000000 00:00 0 > 2f1d4000-347b2000 rwxp 00000000 00:00 0 > [heap] > > f7300000-f7321000 rwxp 00000000 00:00 0 > f7321000-f7400000 ---p 00000000 00:00 0 > f7435000-f7469000 rwxp 00000000 00:00 0 > f7469000-f7473000 r-xp 00000000 08:01 522410 > /lib32/libnss_files-2.11.1.so > <http://libnss_files-2.11.1.so> <http://libnss_files-2.11.1.so> > > f7473000-f7474000 r-xp 00009000 08:01 522410 > /lib32/libnss_files-2.11.1.so > <http://libnss_files-2.11.1.so> <http://libnss_files-2.11.1.so> > f7474000-f7475000 rwxp 0000a000 08:01 522410 > /lib32/libnss_files-2.11.1.so > <http://libnss_files-2.11.1.so> <http://libnss_files-2.11.1.so> > > f7475000-f747d000 r-xp 00000000 08:01 522412 > /lib32/libnss_nis-2.11.1.so > <http://libnss_nis-2.11.1.so> <http://libnss_nis-2.11.1.so> > f747d000-f747e000 r-xp 00007000 08:01 522412 > /lib32/libnss_nis-2.11.1.so > <http://libnss_nis-2.11.1.so> <http://libnss_nis-2.11.1.so> > > f747e000-f747f000 rwxp 00008000 08:01 522412 > /lib32/libnss_nis-2.11.1.so > <http://libnss_nis-2.11.1.so> <http://libnss_nis-2.11.1.so> > > f749f000-f74a1000 rwxp 00000000 00:00 0 > f74a1000-f75f4000 r-xp 00000000 08:01 522401 > /lib32/libc-2.11.1.so <http://libc-2.11.1.so> > <http://libc-2.11.1.so> > > f75f4000-f75f5000 ---p 00153000 08:01 522401 > /lib32/libc-2.11.1.so <http://libc-2.11.1.so> > <http://libc-2.11.1.so> > f75f5000-f75f7000 r-xp 00153000 08:01 522401 > /lib32/libc-2.11.1.so <http://libc-2.11.1.so> > <http://libc-2.11.1.so> > > f75f7000-f75f8000 rwxp 00155000 08:01 522401 > /lib32/libc-2.11.1.so <http://libc-2.11.1.so> > <http://libc-2.11.1.so> > > f75f8000-f75fb000 rwxp 00000000 00:00 0 > f75fb000-f7618000 r-xp 00000000 08:07 262399 > /usr/lib32/libgcc_s.so.1 > > f7618000-f7619000 r-xp 0001c000 08:07 262399 > /usr/lib32/libgcc_s.so.1 > f7619000-f761a000 rwxp 0001d000 08:07 262399 > /usr/lib32/libgcc_s.so.1 > f761a000-f763e000 r-xp 00000000 08:01 522405 > /lib32/libm-2.11.1.so <http://libm-2.11.1.so> > <http://libm-2.11.1.so> > > f763e000-f763f000 r-xp 00023000 08:01 522405 > /lib32/libm-2.11.1.so <http://libm-2.11.1.so> > <http://libm-2.11.1.so> > f763f000-f7640000 rwxp 00024000 08:01 522405 > /lib32/libm-2.11.1.so <http://libm-2.11.1.so> > <http://libm-2.11.1.so> > > > f7640000-f7729000 r-xp 00000000 08:07 271130 > /usr/lib32/libstdc++.so.6.0.13 > f7729000-f772d000 r-xp 000e9000 08:07 271130 > /usr/lib32/libstdc++.so.6.0.13 > f772d000-f772e000 rwxp 000ed000 08:07 271130 > /usr/lib32/libstdc++.so.6.0.13 > > f772e000-f7735000 rwxp 00000000 00:00 0 > f7735000-f774a000 r-xp 00000000 08:01 522415 > /lib32/libpthread-2.11.1.so > <http://libpthread-2.11.1.so> <http://libpthread-2.11.1.so> > f774a000-f774b000 r-xp 00014000 08:01 522415 > /lib32/libpthread-2.11.1.so > <http://libpthread-2.11.1.so> <http://libpthread-2.11.1.so> > > f774b000-f774c000 rwxp 00015000 08:01 522415 > /lib32/libpthread-2.11.1.so > <http://libpthread-2.11.1.so> <http://libpthread-2.11.1.so> > > f774c000-f774e000 rwxp 00000000 00:00 0 > f774e000-f7750000 r-xp 00000000 08:01 522404 > /lib32/libdl-2.11.1.so <http://libdl-2.11.1.so> > <http://libdl-2.11.1.so> > > f7750000-f7751000 r-xp 00001000 08:01 522404 > /lib32/libdl-2.11.1.so <http://libdl-2.11.1.so> > <http://libdl-2.11.1.so> > f7751000-f7752000 rwxp 00002000 08:01 522404 > /lib32/libdl-2.11.1.so <http://libdl-2.11.1.so> > <http://libdl-2.11.1.so> > > > f7752000-f7753000 rwxp 00000000 00:00 0 > f7753000-f775c000 r-xp 00000000 08:01 522403 > /lib32/libcrypt-2.11.1.so > <http://libcrypt-2.11.1.so> <http://libcrypt-2.11.1.so> > f775c000-f775d000 r-xp 00008000 08:01 522403 > /lib32/libcrypt-2.11.1.so > <http://libcrypt-2.11.1.so> <http://libcrypt-2.11.1.so> > > f775d000-f775e000 rwxp 00009000 08:01 522403 > /lib32/libcrypt-2.11.1.so > <http://libcrypt-2.11.1.so> <http://libcrypt-2.11.1.so> > > f775e000-f7785000 rwxp 00000000 00:00 0 > f7785000-f7798000 r-xp 00000000 08:07 262397 > /usr/lib32/libz.so.1.2.3.3 > > f7798000-f7799000 r-xp 00012000 08:07 262397 > /usr/lib32/libz.so.1.2.3.3 > f7799000-f779a000 rwxp 00013000 08:07 262397 > /usr/lib32/libz.so.1.2.3.3 > f779a000-f77ad000 r-xp 00000000 08:01 522407 > /lib32/libnsl-2.11.1.so <http://libnsl-2.11.1.so> > <http://libnsl-2.11.1.so> > > f77ad000-f77ae000 r-xp 00012000 08:01 522407 > /lib32/libnsl-2.11.1.so <http://libnsl-2.11.1.so> > <http://libnsl-2.11.1.so> > f77ae000-f77af000 rwxp 00013000 08:01 522407 > /lib32/libnsl-2.11.1.so <http://libnsl-2.11.1.so> > <http://libnsl-2.11.1.so> > > > f77af000-f77b1000 rwxp 00000000 00:00 0 > f77b1000-f77b7000 r-xp 00000000 08:01 522408 > /lib32/libnss_compat-2.11.1.so > <http://libnss_compat-2.11.1.so> <http://libnss_compat-2.11.1.so> > f77b7000-f77b8000 r-xp 00006000 08:01 522408 > /lib32/libnss_compat-2.11.1.so > <http://libnss_compat-2.11.1.so> <http://libnss_compat-2.11.1.so> > > f77b8000-f77b9000 rwxp 00007000 08:01 522408 > /lib32/libnss_compat-2.11.1.so > <http://libnss_compat-2.11.1.so> <http://libnss_compat-2.11.1.so> > > f77b9000-f77bc000 rwxp 00000000 00:00 0 > f77bc000-f77d8000 r-xp 00000000 08:01 522398 > /lib32/ld-2.11.1.so <http://ld-2.11.1.so> > <http://ld-2.11.1.so> > > f77d8000-f77d9000 r-xp 0001b000 08:01 522398 > /lib32/ld-2.11.1.so <http://ld-2.11.1.so> > <http://ld-2.11.1.so> > f77d9000-f77da000 rwxp 0001c000 08:01 522398 > /lib32/ld-2.11.1.so <http://ld-2.11.1.so> > <http://ld-2.11.1.so> > > > f77da000-f77db000 r-xp 00000000 00:00 0 > [vdso] > ffdf0000-ffe06000 rwxp 00000000 00:00 0 > [stack] > Aborted > > Is this a memory or library problem? > > > Looking forward to your reply. > > All the best, > Wenjing > > > -- > Douglas N. Greve, Ph.D. > MGH-NMR Center > greve(a)nmr.mgh.harvard.edu <mailto:greve@nmr.mgh.harvard.edu> > Phone Number: 617-724-2358 > Fax: 617-726-7422 > > Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting > <http://surfer.nmr.mgh.harvard.edu/fswiki/BugReporting> > FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html > <http://www.nmr.mgh.harvard.edu/facility/filedrop/index.html> > > > > The information in this e-mail is intended only for the person to > whom it is > addressed. If you believe this e-mail was sent to you in error and > the e-mail > contains patient information, please contact the Partners > Compliance HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to > you in error > but does not contain patient information, please contact the > sender and properly > dispose of the e-mail. > > > > > -- > Wenjing Li > Key Lab of Complex Systems and Intelligent Science, > Institute of Automation, Chinese Academy of Sciences(CASIA) > Beijing, 100190,P.R.CHINA -- Douglas N. Greve, Ph.D. MGH-NMR Center greve(a)nmr.mgh.harvard.edu Phone Number: 617-724-2358 Fax: 617-726-7422 Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting FileDrop: www.nmr.mgh.harvard.edu/facility/filedrop/index.html

1 0

Jump to page: