All Forums  Support Forums  Analysis Software Support  bxh_eventstats bug fixed

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format Mode: Basic  Help  Prompt  Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Red Yellow Pink Green Orange Purple Blue Beige Brown Teal Navy Maroon LimeGreen Message: * HTML is OFF * Forum Code is ON Smilies [quote][i]Originally posted by syam.gadde[/i] [br]There was a bug in bxh_eventstats that is only triggered when using multiple runs that have different numbers of timepoints. The nature of this bug is that it may have calculated the "data range" time interval incorrectly for any run having different numbers of timepoints than the first run, where the "data range" time interval refers to the time interval between the first and last volumes in the data. The impact is that events may have been incorrectly excluded from the analysis if their epochs were determined to be outside this incorrectly-calculated time interval. Only those who ran bxh_eventstats on multiple 4-D time series with different numbers of time points (e.g. run1 has 100 volumes, run2 has 150 volumes, etc.) between Feb. 23 and March 16 should be affected. I don't expect many people to have this problem. If you fall into this category, check your <prefix>_LOG_EPOCHAVG.txt file and look for entries that look like this: [font=Andale Mono] Ignoring event at time 436.501 because the following ranges fall outside data range: (0 - 453 secs) [/font=Andale Mono] Double-check that the "data range" specified looks correct. This should normally be 0 to (N+1)*TR seconds where N is the number of time points. [/quote]   Check here to include your profile signature. Check here to subscribe to this topic.