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
However, custom data (e.g., tracking, motus, banding) seldom contains equally sampled timepoints. So consider using "real" calculation on the date column to get stay_len with default unit of day.
add_stay_id or similar transformation will be a default behavior for BirdFlowRoutes.
Also now the synthetic routes generated by route function will not have circular dates (so cross the year boundary), but the timestep will circulate to 1 again. So we should calculate the stay based on date rather than timestep.
This change will be included in the next merge if nobody objects.
The text was updated successfully, but these errors were encountered:
Make sure you do some testing with plot_routes(). It will likely need some updating for the new format. I've wanted to drop the circular dates and drop a bunch of hackish stuff I did to deal with the circular dates, so this is an overdue change. Let me know if you want me to make the changes in the plotting.
The current
add_stay_id
function is using number of the rows as stop length, this is valid if the timesteps are sampled in the same frequency.BirdFlowR/R/route.R
Lines 176 to 184 in cef92ce
However, custom data (e.g., tracking, motus, banding) seldom contains equally sampled timepoints. So consider using "real" calculation on the
date
column to getstay_len
with default unit ofday
.add_stay_id or similar transformation will be a default behavior for
BirdFlowRoutes
.I removed the
add_stay_id
inroute
function.BirdFlowR/R/route.R
Line 187 in 83eaf15
And add the function
add_stay_id_with_varied_intervals
BirdFlowR/R/RouteDataFunction.R
Lines 395 to 415 in 83eaf15
which is applied when a new BirdFlowRoutes object is created:
BirdFlowR/R/RouteDataClass.R
Lines 198 to 209 in 83eaf15
Also now the synthetic routes generated by
route
function will not have circular dates (so cross the year boundary), but the timestep will circulate to 1 again. So we should calculate the stay based on date rather than timestep.This change will be included in the next merge if nobody objects.
The text was updated successfully, but these errors were encountered: