You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using preprocessed-only birdflow objects as the bf argument for BirdFlowR functions is currently possible, but isn't explicitly supported and does not always produce expected results. However, it is sometimes very useful to be able to do so. For example, when wanting to extract timestep or CRS info created during the preprocessing.
The overall user experience related to using preprocessed-only objects could be improved with some combination of documentation, tests, warnings, or errors.
The following example from lookup_timestep() will soon be fixed by broader changes being made by @ethanplunkett, but similar situations might arise with other functions.
# goal: use existing birdflow object to lookup timesteps
bf <- BirdFlowR::preprocess_species('paibun', res = 1000, hdf5 = FALSE, skip_quality_checks = TRUE)
timesteps <-
structure(
c(1325376000, 1293408000, 1283040000),
class = c("POSIXct",
"POSIXt"),
tzone = "UTC"
)
tail(bf$dates, 1) #53
# timestep #53 in preprocessed model creates non-ascending `breaks` vector,
# which causes error in findIntervals
lookup_timestep(timesteps, bf) # error, see above note
Using preprocessed-only birdflow objects as the bf argument for BirdFlowR functions is currently possible, but isn't explicitly supported and does not always produce expected results. However, it is sometimes very useful to be able to do so. For example, when wanting to extract timestep or CRS info created during the preprocessing.
The overall user experience related to using preprocessed-only objects could be improved with some combination of documentation, tests, warnings, or errors.
The following example from
lookup_timestep()
will soon be fixed by broader changes being made by @ethanplunkett, but similar situations might arise with other functions.BirdFlowR/R/lookup_timestep.R
Line 64 in 43beefa
The text was updated successfully, but these errors were encountered: