Re: [Freesurfer] longer run time on 5.3 versus 5.2 ?
Hi Mehul no, that's definitely not expected for it to go from 20 min to almost 5 hours! We'll investigate as that shouldn't be the case. Bruce On Tue, 4 Jun 2013, Mehul Sampat wrote: In some cases, we are seeing that, for the same subject, the run time is slower for 5.3 versus 5.2; A quick check on recon-all-status.log shows that the CA Reg Inv step is taking longer with 5.3. recon-all-status.log from data processed with 5.2: #@# CA Reg Thu Jan 17 16:03:53 PST 2013 #@# CA Reg Inv Thu Jan 17 20:17:32 PST 2013 recon-all-status.log from data processed with 5.3 #@# CA Reg Mon Jun 3 19:46:37 PDT 2013 #@# CA Reg Inv Tue Jun 4 04:52:57 PDT 2013 Is this expected ? Or in your own testing are the recon-all processing times similar for 5.2 versus 5.3 ? The recon-all.log file for both cases are attached; Thanks Mehul ___ Freesurfer mailing list Freesurfer@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.
Re: [Freesurfer] longer run time on 5.3 versus 5.2 ?
Hi Bruce, Okay. It went from ~4 hours in 5.2 to ~9 hours in 5.3; we thought it was a big change to and are trying to isolate the root cause We are running 75 cases run with 5.3 that have been run with 5.2 before; once they are done, will let you all know if this issue is seen in other cases too. Mehul ps: the cases were run on different machines but the specs of the two machines are quite similar; we are also trying to see if it is hard-ware related.. On Tue, Jun 4, 2013 at 10:37 AM, Bruce Fischl fis...@nmr.mgh.harvard.eduwrote: Hi Mehul no, that's definitely not expected for it to go from 20 min to almost 5 hours! We'll investigate as that shouldn't be the case. Bruce On Tue, 4 Jun 2013, Mehul Sampat wrote: In some cases, we are seeing that, for the same subject, the run time is slower for 5.3 versus 5.2; A quick check on recon-all-status.log shows that the CA Reg Inv step is taking longer with 5.3. recon-all-status.log from data processed with 5.2: #@# CA Reg Thu Jan 17 16:03:53 PST 2013 #@# CA Reg Inv Thu Jan 17 20:17:32 PST 2013 recon-all-status.log from data processed with 5.3 #@# CA Reg Mon Jun 3 19:46:37 PDT 2013 #@# CA Reg Inv Tue Jun 4 04:52:57 PDT 2013 Is this expected ? Or in your own testing are the recon-all processing times similar for 5.2 versus 5.3 ? The recon-all.log file for both cases are attached; Thanks Mehul 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/**compliancelinehttp://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@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.
Re: [Freesurfer] longer run time on 5.3 versus 5.2 ?
ok, thanks On Tue, 4 Jun 2013, Mehul Sampat wrote: Hi Bruce, Okay. It went from ~4 hours in 5.2 to ~9 hours in 5.3; we thought it was a big change to and are trying to isolate the root cause We are running 75 cases run with 5.3 that have been run with 5.2 before; once they are done, will let you all know if this issue is seen in other cases too. Mehul ps: the cases were run on different machines but the specs of the two machines are quite similar; we are also trying to see if it is hard-ware related.. On Tue, Jun 4, 2013 at 10:37 AM, Bruce Fischl fis...@nmr.mgh.harvard.edu wrote: Hi Mehul no, that's definitely not expected for it to go from 20 min to almost 5 hours! We'll investigate as that shouldn't be the case. Bruce On Tue, 4 Jun 2013, Mehul Sampat wrote: In some cases, we are seeing that, for the same subject, the run time is slower for 5.3 versus 5.2; A quick check on recon-all-status.log shows that the CA Reg Inv step is taking longer with 5.3. recon-all-status.log from data processed with 5.2: #@# CA Reg Thu Jan 17 16:03:53 PST 2013 #@# CA Reg Inv Thu Jan 17 20:17:32 PST 2013 recon-all-status.log from data processed with 5.3 #@# CA Reg Mon Jun 3 19:46:37 PDT 2013 #@# CA Reg Inv Tue Jun 4 04:52:57 PDT 2013 Is this expected ? Or in your own testing are the recon-all processing times similar for 5.2 versus 5.3 ? The recon-all.log file for both cases are attached; Thanks Mehul 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@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.
Re: [Freesurfer] longer run time on 5.3 versus 5.2 ?
I saw this issue too. The total running time went from an average of 16.3h to 20.4h - Pedro Paulo de Magalhães Oliveira Junior Netfilter SpeedComm Telecom -- www.netfilter.com.br -- For mobile: http://itunes.apple.com/br/artist/netfilter/id365306441 On Tue, Jun 4, 2013 at 2:54 PM, Mehul Sampat mpsam...@gmail.com wrote: Hi Bruce, Okay. It went from ~4 hours in 5.2 to ~9 hours in 5.3; we thought it was a big change to and are trying to isolate the root cause We are running 75 cases run with 5.3 that have been run with 5.2 before; once they are done, will let you all know if this issue is seen in other cases too. Mehul ps: the cases were run on different machines but the specs of the two machines are quite similar; we are also trying to see if it is hard-ware related.. On Tue, Jun 4, 2013 at 10:37 AM, Bruce Fischl fis...@nmr.mgh.harvard.eduwrote: Hi Mehul no, that's definitely not expected for it to go from 20 min to almost 5 hours! We'll investigate as that shouldn't be the case. Bruce On Tue, 4 Jun 2013, Mehul Sampat wrote: In some cases, we are seeing that, for the same subject, the run time is slower for 5.3 versus 5.2; A quick check on recon-all-status.log shows that the CA Reg Inv step is taking longer with 5.3. recon-all-status.log from data processed with 5.2: #@# CA Reg Thu Jan 17 16:03:53 PST 2013 #@# CA Reg Inv Thu Jan 17 20:17:32 PST 2013 recon-all-status.log from data processed with 5.3 #@# CA Reg Mon Jun 3 19:46:37 PDT 2013 #@# CA Reg Inv Tue Jun 4 04:52:57 PDT 2013 Is this expected ? Or in your own testing are the recon-all processing times similar for 5.2 versus 5.3 ? The recon-all.log file for both cases are attached; Thanks Mehul 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/**compliancelinehttp://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@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@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.
