JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for SPM Archives


SPM Archives

SPM Archives


SPM@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

SPM Home

SPM Home

SPM  1998

SPM 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: normalization

From:

[log in to unmask] (Jesper Andersson)

Reply-To:

[log in to unmask] (Jesper Andersson)

Date:

Mon, 9 Nov 1998 16:47:04 GMT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (115 lines)

Dear Peter,

> 
> hello SPM-ers,
> 
> I have problems normalizing my data. The volumes are realigned but the normalization
> goes wrong. Some of the scans in the normalization are cut, specially the scans in
> the begin and the scans in the end of the volumes. I have read that this can be 
> normal, but when I display the normalized images with disp_analyze I get 
> divide by zeros (which doesn't look right to me).

I honestly don't know what "disp_analyze is, but I would guess that as
long as you can see the images (not all voxels are zero) you should be
OK.

> 
> If I run statistics on the normalized data, then I get the following errors:
> 
> Warning: Log of zero
> 
> Warning: Log of zero
> 
> Warning: Log of zero
> ??? Index exceeds matrix dimensions.
> 
> Error in ==> /rug103/home2/users/csg/csg739/spm96/spm_lambda.m
> On line 43 ==> if df <= length(LC2T); Lc2t = LC2T(df); end
> 
> Error in ==> /rug103/home2/users/csg/csg739/spm96/spm_spm.m
> On line 315 ==> Lc2z = spm_lambda(df);
> 
> Error in ==> /rug103/home2/users/csg/csg739/spm96/spm_fmri_spm_ui.m
> On line 509 ==> spm_spm(V,H,C,B,G,CONTRAST,ORIGIN,GX,HCBGnames,P,SIGMA,RT);
> 
> ??? Error while evaluating callback string.
> 

judging from the the error messages above your problem may not be
assosciated with the spatial normalisation as you have assumed. The
error messages indicate that you have negative degrees of freedom for
the design which you attempt to fit your data to, which in turn means
that you have defined more effects than you have independent
measurements.

> 
> some info
> ---------
> 
> The data is fmri
> 
> The volumes consist of 6 scans, covering only part of the brain going from high
> in the forehead, over the ears to low in the back of the head.
> 

Six times six = 36mm isn't really a great coverage in the axial
direction, and the spatial normalisation may have problems working out
the transforms in that direction.

> The structural scans were taken on the same place as the functionals.
> 

I take it that you have done your structuals in the same was as the
functionals (6 slices of 6mm width). One point of doing structurals may
actually (in the case where you have incomplete coverage with your
functional data) be to have a scan on which to base the spatial
normalisation. This may be something you wish to consider in the
future.

> the resolution of the scans (both structural and functional are (256 x 256).
> the voxel-size is [0.89 0.89 6]
> 
> the ac isn't on the scans
>

The spatial normalisation does not explicitly use the ac in any way, so
that should not be an issue.
 
> I did get results in spm for windows
>

Good for you. Possibly there are some differences in how you set up the
analysis.
 
> some more questions ?
> ---------------------
> 
> Do i have to set the origin?

You don't have to set it, although it may be a good idea to do so. You say that you don't have the ac in the imaged volume, but possibly you could venture a guess as to where it is in relation to your volume.
 
> Is is neccessary to coregister? If so, what do I fill in as target, object (t1,T2 ?) ?

It may be necessary to coregister depending on exactly what you are
doing. If you are basing the spatial normalisation on the structurals
and applying the parameters to the functionals, then it may be a good
idea to coregister the functional data to your structural. Assuming you
want to use the structurals for spatial normalisation you should set
for your target image the appropriate modality for the structural
(probably best with T1) and for your object image you should set the
appropriate modality for that (T2).

> which of the default normalization options do you advice me to change ?
>
Given your poor coverage in the z-direction you may want too settle for
an affine registration (including zooms and shears, but excluding any
nonlinear componenets). You may even want to assume a value for the
z-axis zoom and not fit that value. You may work out a reasonable
assumption based on the x- and y-axes zooms and the data given in the
paper Ashburner et al. NeuroImage 1997; 6:344-352.
> 
> 


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager