# Longitudinal FBA: small absolute / large standard effect

**URL:** https://community.mrtrix.org/t/longitudinal-fba-small-absolute-large-standard-effect/4850
**Category:** Uncategorized
**Tags:** fba
**Created:** [May 6, 2021, 7:17am UTC](https://community.mrtrix.org/t/longitudinal-fba-small-absolute-large-standard-effect/4850 "2021-05-06T07:17:18Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![rsmith](https://community.mrtrix.org/user_avatar/community.mrtrix.org/rsmith/32/2672_2.png) [@rsmith](https://community.mrtrix.org/u/rsmith)
#### Post date: [May 7, 2021, 5:43am UTC](https://community.mrtrix.org/t/longitudinal-fba-small-absolute-large-standard-effect/4850/2 "2021-05-07T05:43:07Z")

</div>

Hi Michelle,

I’m rather sceptical of the numbers you’re reporting, so would encourage some very critical assessment of the data as a whole.

What those absolute effect statistics are claiming is that, in that region, the rate of change of log(FC) with respect to time in weeks is ~ 2e-08. So over the course of a year, log(FC) is predicted to change by ~ 1e-06. That’s a tiny number, well below the precision of image registration that the FC metric is derived from. Yet this is supposedly _the region with a statistically significant effect_. So something foul is afoot.

1. You need to confirm that your usage of the `fixelcfestats` command is faithful to your intended hypothesis test. There are a lot of ways in which a GLM other than the correct one can be invoked that won’t result in an error, but produce all sorts of weird outputs.

2. Check the raw fixel data input, make sure that they make sense and are within the expected numerical ranges.

3. Make sure that you are performing fixel data smoothing. In previous software versions, this was performed internally within the `fixelcfestats` command; as of `3.0.0`, this is instead done _prior_ to `fixelcfestats` using command `fixelfilter`. Failing to do so can result in very small statistically significant regions, as there are greater opportunities to obtain very large test statistics due to large effect / small variance by chance alone.

4. Look at the template streamlines tractogram in the region of the significant result, and compare it to the fixel analysis mask. Fixels that possess very little fixel-fixel connectivity can be problematic due to intrinsic non-stationarity correction ([essay on forum](https://community.mrtrix.org/t/how-to-improve-the-fba-results/4453/7)). Deriving a fixel mask for statistical inference that necessitates adequate fixel-fixel connectivity can be beneficial; indeed I’ll likely explicitly recommend this when I get around to revising the pipeline documentation.

> If we calculate the percentage effect as described we get the following result:  
> volume mean median std min max count  
> [0] 0 0 0 0 0 3

I can only hypothesize that this is a floating-point precision issue. That calculation for log(FC) _only_ depends on the absolute effect, nothing else. Those calculations _should_ all be being done using double-precision, in which case I’d have expected a non-zero result; but if the numbers bottle-neck to single-precision at any point, then e^(2.0 x 10^-8) will be so close to 1 that the result of the total computation is zero.

Rob

---

_[View the full topic](https://community.mrtrix.org/t/longitudinal-fba-small-absolute-large-standard-effect/4850)._