Prior to starting make sure that:
.csv
file that
contains a single column with a header row with the names of thee fatty
acids listed below (see example file “FAset.csv”)..csv
file
with the full set of FAs and then add code to subset the FAs you wish to
use from that set -> this alternative is useful if you are
planning to test multiple sets..csv
file should
be proportions summing to 1.p.SMUFASA
BUT make sure
that the same FAs appear in the predator and prey files..csv
file can contain as much
tombstone data columns as you like, you must extract the predator FA
signatures as separate input in order to run in p.SMUFASA
.
For example: in the code below, the predator .csv
file
(“predatorFAs.csv
”) has 4 tombstone columns (SampleCode,
AnimalCode, SampleGroup, Biopsy). Prior to running
p.SMUFASA
, the tombstone (columns 1-4) and FA data (columns
5 onward) are each extracted from the original data frame. The FA data
becomes the predator.matrix
(which is passed to
p.SMUFASA
) and the tombstone data is retained so that it
can be recombined with the model output later on..csv
file should be
proportions summing to 1.FC - rep(1,nrow(prey.matrix))
.The MUFASA output is a list with 4 components:
A vector of length equal to the number of FAs used and whose sum is the total number of FAs used. Thos is a set of calibration coefficients common to all predators used.
The diet estimate vector returned by p.SMUFASA
represents an overall common diet for all predators in
predator.matrix
. Note: If you wish to
obtain diet estimates for each individual predator see the steps
below.
This is a vector of the negative log likelihood values at each iteration of the optimizer.
Once a vector of calibration coefficients is obtained via
p.SMUFASA
you can pass this vector to p.QFASA
or p.MUFASA
to obtain individual diet estimates.