traitecoevo / rabbit

An R package to "rabbitly" process data recorded triaxial accelerometer outputs
Other
0 stars 0 forks source link

types of date-time inputs #6

Closed wcornwell closed 3 weeks ago

wcornwell commented 1 month ago

Do the timestamps always come in like in jack's example:

03/01/2024 01:08:16.000

or are there other cases to handle on input? @jack-bilby @courtneyadams1

wcornwell commented 1 month ago

question 2: time zones? do we want to keep track?

wcornwell commented 1 month ago

turns out this works for these particular rabbits/bilbies:

df$Timestamp <- dmy_hms(df$Timestamp, tz = "Australia/Adelaide")

but maybe we want the user to have the ability to change that? I guess it has to be consistent with the settings on the accelerometer

courtneyadams1 commented 1 month ago

Yeah the date/time for the numbat data looks the same. I will have different time zones though, some will be Adelaide and some will be Perth

jack-bilby commented 1 month ago

When you download the data to a csv in X Manager (the accelerometer application), you input the exact time and date that you turned on the device, meaning it should always be in local time to the device I believe.