-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description of use of split among pings #13
Comments
Polyvalent gears, or multiple target assemblages (e.g. DWS and DEF). How should catch or effort be split in these cases. |
Create a table from the script to count how many multi-gear or multi-metier trips exist, document what has been done with them. |
Here is a method for splitting metier/gear/mesh-size/ices retangle/gear width into the tacsatp file: trip_assign <- function(tacsatp, eflalo, col = "LE_GEAR", trust_logbook = T){ if(col == "LE_MET"){ e <- data.table(eflalo)[FT_REF %in% tst[V1>1]$FT_REF] tacsatpa_LE_GEAR <- trip_assign(tacsatp, eflalo, col = "LE_GEAR", trust_logbook = T) tacsatpa_LE_MSZ <- trip_assign(tacsatp, eflalo, col = "LE_MSZ", trust_logbook = T) tacsatpa_LE_RECT <- trip_assign(tacsatp, eflalo, col = "LE_RECT", trust_logbook = T) tacsatpa_LE_MET <- trip_assign(tacsatp, eflalo, col = "LE_MET", trust_logbook = T) if("LE_WIDTH" %in% names(eflalo)){ |
The use of "splitamongpings" is not well documented in the workflow. This could be improved by requiring some sort of flagging.
The text was updated successfully, but these errors were encountered: