Skip to content
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

tag-recapture: create user filter to set min number of recaptures for inclusion of a tag-group #280

Closed
Tracked by #636
Rick-Methot-NOAA opened this issue Mar 28, 2022 · 2 comments · Fixed by #281
Assignees
Labels
change log use for issues that should appear in change log tag-recapture wishlist request new feature; bigger than revision; OK to remove after adding to Milestone
Milestone

Comments

@Rick-Methot-NOAA
Copy link
Collaborator

some tag groups may have many releases, but few recaptures. It seems useful to allow a user to set a filter such that that number of recaptures in time >= mixperiod exist.
This could be implemented in ss_readdata330.tpl to create a "use" flag for each tag group.
The value could be read in ss_readdata330.tpl right after the input of the value for mixperiod.
The total number of recaps is currently not counted, but easily could be in ss_readdata330.tpl.
Note: remember to only count those that are >=mixperiod.
Probably should make this a conditional input:
if(mixperiod>=0){
min_tag_recap=0.0;}
else{
mixperiod=-mixperiod;
ad_comm: min_tag_recap;}

@Rick-Methot-NOAA Rick-Methot-NOAA added wishlist request new feature; bigger than revision; OK to remove after adding to Milestone tag-recapture labels Mar 28, 2022
@Rick-Methot-NOAA Rick-Methot-NOAA self-assigned this Mar 28, 2022
@Rick-Methot-NOAA Rick-Methot-NOAA moved this to In Progress in ss3-issue-tracker Mar 29, 2022
@Rick-Methot-NOAA
Copy link
Collaborator Author

Rick-Methot-NOAA commented Mar 29, 2022

1 # do tags (0/1)
121 # N tag groups
769 # N recap events
-4 # TG_mixperiod (latency) is the first period in which logL is calculated for this tag group (0 = release period)
#  (use negative value for TG_mixperiod to invoke reading TG_min_recap after TG_maxperiods
16 # max periods (seasons) to track recoveries, after which tags are still read into this accumulator period
2 # TG_min_recap:  N recaps >= mixperiod must be >= min_recap to include tag group in logL
# Release data for each tag group.  Tags are considered to be released at the beginning of a season (period)

ALSO*****
In compreport.sso, I now output the time in periods since release, which seems more useful for plotting and comparisons than real time, which is still there in another column

@k-doering-NOAA
Copy link
Contributor

The final output looks like this:

2 # do tags (0/1/2). 2 means include TG_min_recap input
121 # N tag groups
769 # N recap events
4 # TG_mixperiod (latency) is the first period in which logL is calculated for this tag group (0 = release period)
16 # max periods (seasons) to track recoveries, after which tags are still read into this accumulator period
2 # Cond on Do Tags 2: TG_min_recap:  N recaps >= mixperiod must be >= min_recap to include tag group in logL
# Release data for each tag group.  Tags are considered to be released at the beginning of a season (period)

@k-doering-NOAA k-doering-NOAA added the resolved issue resolved, look for "needs test" label label Mar 31, 2022
@Rick-Methot-NOAA Rick-Methot-NOAA linked a pull request Mar 31, 2022 that will close this issue
4 tasks
@k-doering-NOAA k-doering-NOAA removed the resolved issue resolved, look for "needs test" label label Apr 4, 2022
@e-perl-NOAA e-perl-NOAA added the change log use for issues that should appear in change log label Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change log use for issues that should appear in change log tag-recapture wishlist request new feature; bigger than revision; OK to remove after adding to Milestone
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants