Open famuvie opened 8 years ago
For getting rid of pedigreemm
we should:
For 1, we could get away with a simple data.frame (as other packages like pedigree
or nadiv
do) or create a custom class. Then we should adapt the usage of the pedigree throughout the code.
For 2, there are several options:
pedigree
provides fast compiled functions makeA()
and makeAinv()
. The inconvenient part is that it works by writing the results to text files which need to be read into memory. nadiv
also provides fast compiled functions with the same names as pedigree
and it does not bring in too many sub-dependencies. Moreover, it contains additional functions for computing dominance matrices, inbreeding and other potentially useful stuff.AnimalINLA
) if licenses allow that.
We currently have the dependency structure shown below.
Most dependencies are actually via
ggplot2
. Should we produce the default plots using base graphics only? Maybe we could simply suggestggplot2
.Another source of heavy dependencies is
pedigreemm
, which in particular requiresnloptr
which in turn requires an external library that needs to be compiled and is often problematic. This looks too problematic, given that we only leverage thepedigree
class inpedigreemm
and the functionsgetA()
andgetAinv()
.