Consider some way where a user could indicate the final detection location (i.e. spawning location) to use for each pit tag. Once that is set, could PITcleanr determine which observations to "keep"? Thinking about making workflow more reproducible, especially if the configuration file or list of sites changes, so prepWrapper output changes slightly (new rows, fewer rows, etc.). This could also make it less likely that a user erroneously fills out user_keep_obs column to something they didn't intend.
Would this be a separate column for final_location, and users could indicate T for each tag. Tags with "standard" paths would have that filled in.
Consider some way where a user could indicate the final detection location (i.e. spawning location) to use for each pit tag. Once that is set, could PITcleanr determine which observations to "keep"? Thinking about making workflow more reproducible, especially if the configuration file or list of sites changes, so
prepWrapperoutput changes slightly (new rows, fewer rows, etc.). This could also make it less likely that a user erroneously fills outuser_keep_obscolumn to something they didn't intend.Would this be a separate column for final_location, and users could indicate T for each tag. Tags with "standard" paths would have that filled in.