Warning messages: query?

38 views
Skip to first unread message

Kerry Kilshaw

unread,
Apr 5, 2024, 3:39:45 PMApr 5
to ctmm R user group
Hi everyone

I'm rerunning a script that has worked fine before but its throwing up this error after running ctmm.select

Warning messages:
1: In M[[i]]$error[TEST] <- ERROR[TEST] :
  number of items to replace is not a multiple of replacement length
2: In M[[i]]$error[TEST] <- ERROR[TEST] :
  number of items to replace is not a multiple of replacement length

When I look at the summary of the FITS object, two of the individuals are showing inf in the error 3 row

$name
[1] "OUF anisotropic error"

$DOF
     mean      area diffusion     speed
 124.1140  200.4577  520.7824  124.0780

$CI
                                        low       est      high
area (square kilometers)           1.686141  1.946254  2.224753
τ[position] (hours)                2.982787  3.531689  4.181603
τ[velocity] (minutes)              3.075096  3.922613  5.003712
speed (kilometers/day)            22.203272 24.344892 26.484059
diffusion (square kilometers/day)  1.368822  1.494433  1.625479
error 3 (meters)                   0.000000  0.000000       Inf

I have applied a UERE to the data from an independent calibration dataset using the following which has never resulted in any issues before

# assign the calibration prior from calibration data to this data

uere(Fairburn_segmented.telemetry) <- UERE

There is HDOP values for all rows in the dataset, so wondering if anyone has seen this error before, I can't see anything wrong or even if I need to worry about it?

Thanks

Kerry

Christen Fleming

unread,
Apr 10, 2024, 12:01:22 AMApr 10
to ctmm R user group
Hi Kerry,

I suspect that your datasets were in different formats when they were imported, causing different assumed error-model structures or names. You can look at the UERE slot of each object via uere() and the rows are probably different or have different names, which can be traced back to the columns and column names present in the CSV files being different. Structuring and naming those files the same way and re-importing should then fix the issue.

If that isn't the case, then feel free to send me a minimal working example and I will take a look at it.

Best,
Chris

Kerry Kilshaw

unread,
Apr 18, 2024, 7:39:00 AMApr 18
to ctmm R user group
Hi Chris

Yes, that sorted it, thanks, on of the column headings was slightly different!

Thanks

Kerry
Reply all
Reply to author
Forward
0 new messages