Andrew O'Reilly-Nugent

I should have been more descriptive: ``` parse_date_time(c("2101, Apr 10", "10/04/2101"), orders = c("ymd", "dmy"), train = F) [1] "2010-01-21 UTC" "2101-04-10 UTC" ``` Both dates should parse as `2101-04-10...

This is my butt-ugly workaround: ``` r library(tidyverse) library(lubridate) data.frame(date = c("2101, Apr 10", "10/04/2101")) %>% mutate(a = parse_date_time(date, orders = c("ymd", "dmy")), b = ifelse(!is.na(ymd(date)) & ymd(date) != a,...

Nice one @Namyalg - sorry it's taken so long to review

I'm not sure if this is the same thing, but another example would be declaring covariate matrices in Stan. Currently something like this works: ```{r} df %>% compose_data(X = model.matrix(~...

Censoring looks great, thanks! Converting to logical is a nice touch. #### Matrices: These examples come up together because I have data declarations for Stan that often look like this:...

> I might have missed it in the docs, but I'm not sure how multivariate (matrix) data work either: I was close! Must mean you've got an intuitive interface. ```...

> no longer complain when you pass in data lists that have extra variables not present in the model. I've not had a problem with Stan or JAGS, so this...

I support the the change but don't totally understand the motivation. Your point about expending compute time in proportion to leaf area makes sense, but that doesn't seem relevant if...

@itowers1 found it! I just rediscovered it when looking at turnover in #380.

Wholeheartedly endorsed! TF24 aligns with the naming convention in https://traitecoevo.github.io/plant/articles/developer_notes.html#strategies