Re: Using plant pedigrees...

Dear Scott,

re:
In using ASREML for sugarcane (where lines are fixed clones), we find
that it would be more convenient to be able to use a GIV file, rather
than a PEDIGREE file when trying to formulate the model for estimation
of breeding values (another reason for this is that lines can be used
either as males or females).

*** ASReml generates a message but does not otherwise mind
if particular parents are used as male and female.

So, given a pedigree file, ASREML can apparently deal with clones by
using 'ide' in the model:

Y ~ !f something !r ide(Clone)

*** ide(Clone) ignores the relationships between Clones

 Clone !P
 ...
clone.ped !GIV
data.asd
 Y ~ mu !r Clone

is equivalent to

 Clone *
...
clone.giv
data.asd
 Y ~ mu !r giv(Clone,1)

provided care is taken to code Clone consistently between the factor
definition and the .giv file

I would like to know if, when I output the calculated GIV file for this
run (using !GIV), the matrix of distances will also assume that the
pedigree is of clones? Or will the GIV file be the same as if I had used
a model like this:

Y ~ !f something !r giv(Clone)

*** Does that make sense?

Best wishes in the Name of Jesus Christ, my Saviour.
Check out http://members.dodo.net.au/~cargovale

Arthur Gilmour PhD
Principal Research Scientist (Biometrics)
NSW Department of Primary Industries
Orange Agricultural Institute, Forest Rd, ORANGE, 2800, AUSTRALIA

mailto:Arthur.Gilmour_at_agric.nsw.gov.au
fax: 02 6391 3899; 02 6391 3922 Australia +61
telephone work: 02 6391 3815; home: 02 6364 3288;

http://www.agric.nsw.gov.au/reader/17263
http://www.asreml.co.uk/
The ASReml discussion group ASREML-L_at_agric.nsw.gov.au
   has reactivated. To join, mailto:arthur.gilmour_at_agric.nsw.gov.au
Cookbook: http://uncronopio.org/luis/asreml_cookbook.html

Ellen is doing well after her Hip replacement on 24 Feb but
she will need crutches for a while yet.
<><><><><><><><><><><><><><><><><><><><><><><><><>

This message is intended for the addressee named and may contain
confidential information. If you are not the intended recipient or
received it in error, please delete the message and notify sender. Views
expressed are those of the individual sender and are not necessarily the
views of their organisation.
Received on Sun Mar 14 2005 - 11:53:30 EST