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
add sts_create(meta, data) where meta can be either a list or a single-row tibble. The only required items in meta would be latitude, longitude, timezone and deviceID. Others will be created or added as empty fields. Various checks will be performed and helpful error messages issued if the sts object cannot be created. (6/01/23)
use new suntools package instead of code copied into utils-timeInfo(). Note that suntools requires *sf. (7/12/23)
Items finished by 2024-03-08
.determineTimezone() fails when incoming POSIXct starttime has timezone == "" (4/18/23)
Items finished by 2024-01-16
add mts_pull(name) to pull a column of data from either 'meta' or 'data' depending on where that name is found. (01/16)
Items finished by 2023-09-21
mts_setTimeAxis() can change the time axis timezone when no timezone is specified. This should never happen. The underlying timezone should never change (e.g. from UTC). (9/09)
mts_trimDatetime() should be deprecated in favor of mts_setTimeAxis(). (9/09)
US/Hawaii timezone issue. (9/12)
Items finished by 2023-09-09
Add mts_slice() to select based on row indices in the meta table. (7/13)
Add mts_setTimeAxis() for cases where you want to extend a time series to mach other, longer time series. (9/05)
Items finished by 2023-07-10
mts_filterDatetime() uses datetime < timeRange[2]. This should perhaps be <=. When using ceilingEnd = TRUE, I would expect the last timestep to be included in the filtered results. (6/30)
Items finished by 2023-05-08
mts_select() fails when not all deviceDeploymentIDs are found. Solution is to mts_filterMeta() and then get found deviceDeploymentIDs from this new meta. Perhaps also issue a warning. (05/05)
Add mts_arrange() to work like dplyr::arrange() on mts$meta. (05/05)
Items as they come up:
TODO:
sts_create(meta, data)where meta can be either a list or a single-row tibble. The only required items inmetawould be latitude, longitude, timezone and deviceID. Others will be created or added as empty fields. Various checks will be performed and helpful error messages issued if the sts object cannot be created. (6/01/23)utils-timeInfo(). Note that suntools requires *sf. (7/12/23)Items finished by 2024-03-08
.determineTimezone()fails when incoming POSIXct starttime hastimezone == ""(4/18/23)Items finished by 2024-01-16
mts_pull(name)to pull a column of data from either 'meta' or 'data' depending on where that name is found. (01/16)Items finished by 2023-09-21
mts_setTimeAxis()can change the time axis timezone when no timezone is specified. This should never happen. The underlying timezone should never change (e.g. from UTC). (9/09)mts_trimDatetime()should be deprecated in favor ofmts_setTimeAxis(). (9/09)US/Hawaiitimezone issue. (9/12)Items finished by 2023-09-09
mts_slice()to select based on row indices in themetatable. (7/13)mts_setTimeAxis()for cases where you want to extend a time series to mach other, longer time series. (9/05)Items finished by 2023-07-10
mts_filterDatetime()usesdatetime < timeRange[2]. This should perhaps be<=. When usingceilingEnd = TRUE, I would expect the last timestep to be included in the filtered results. (6/30)Items finished by 2023-05-08
mts_select()fails when not alldeviceDeploymentIDs are found. Solution is tomts_filterMeta()and then get founddeviceDeploymentIDsfrom this new meta. Perhaps also issue a warning. (05/05)mts_arrange()to work likedplyr::arrange()onmts$meta. (05/05)Items finished on 2023-05-05