kaitlyngaynor
commented
3 years ago I already raised this issue with Meredith & am waiting for her reply! I'm going to make a consolidated version with one row per camera and will send it to you once it's ready
On Mon, Feb 15, 2021 at 6:26 PM klg-2016 notifications@github.com wrote:
I'm starting to switch to the new spreadsheets that Meredith just shared and ran into an issue creating the camera operation matrix with the new data. That spreadsheet ("Camera_operation_year1-4") has more than one set of start/end dates for some of the cameras, as makes sense given it covers multiple seasons. However, the cameraOperation function doesn't like that and throws this error: "Error: 48 stations have more than 1 item in CTtable. Please specify 'cameraCol' or 'sessionCol'"
My first thought for how to address this was to call the times between active monitoring for cameras "problems" and rearrange the spreadsheet so that each station only has a single row. Do you think that might work? I'm not sure if I'm missing something basic for how the function is operating that would suggest no.
I also started looking into the issue in the camtrapR package description online (https://cran.r-project.org/web/packages/camtrapR/camtrapR.pdf) and found that you sessionCol is a variable accepted by cameraOperation, which is specifically for multi-season work so it seems like a better bet. It looks like you just create a "session" column in your data frame and fill it with the year (i.e. 2016). That should be mostly straightforward, except for not having a 1:1 relationship for the camera info and seasons (there are some active camera periods that include more than a single late dry period). For that, I'm thinking I might just try repeating the row so that every camera has a row for every season, with some duplicates. I'm close to winding down for the evening; this is the route I'm planning to pursue when I get back to work. Whenever you get a chance, I'd appreciate your thoughts! Thank you
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kaitlyngaynor/gorongosa-mesocarnivores/issues/111, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHA7WT3J3YSFSJRBYQN7LEDS7HJTRANCNFSM4XVUNVIA .
klg-2016
https://github.com/kaitlyngaynor/gorongosa-mesocarnivores/blob/f458aba3a7a198db1cd53bd63bca3b612ee5d5a1/scripts/multi-season%20model/01-multi-season-data-prep.R#L26
I'm starting to switch to the new spreadsheets that Meredith just shared and ran into an issue creating the camera operation matrix with the new data. That spreadsheet ("Camera_operation_year1-4") has more than one set of start/end dates for some of the cameras, as makes sense given it covers multiple seasons. However, the cameraOperation function doesn't like that and throws this error: "Error: 48 stations have more than 1 item in CTtable. Please specify 'cameraCol' or 'sessionCol'"
My first thought for how to address this was to call the times between active monitoring for cameras "problems" and rearrange the spreadsheet so that each station only has a single row. Do you think that might work? I'm not sure if I'm missing something basic for how the function is operating that would suggest no.
I also started looking into the issue in the camtrapR package description online (https://cran.r-project.org/web/packages/camtrapR/camtrapR.pdf) and found that you sessionCol is a variable accepted by cameraOperation, which is specifically for multi-season work so it seems like a better bet. It looks like you just create a "session" column in your data frame and fill it with the year (i.e. 2016). That should be mostly straightforward, except for not having a 1:1 relationship for the camera info and seasons (there are some active camera periods that include more than a single late dry period). For that, I'm thinking I might just try repeating the row so that every camera has a row for every season, with some duplicates. I'm close to winding down for the evening; this is the route I'm planning to pursue when I get back to work. Whenever you get a chance, I'd appreciate your thoughts! Thank you