-
Notifications
You must be signed in to change notification settings - Fork 2
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
custom start and end for route_migration #88
Comments
I had thought of |
Currently
While
After the change it would be:
or
|
We could also add a function to customize the species metadata in a BirdFlow object, and/or you could edit the bf$species list directly. I have mixed feelings about this as it would be nice to make it clear that the resulting dates weren't from eBird S&T. We could for instance allow optional "custom_" versions in the species list that would be preferentially used (if present) when looking up the migration dates, along with a function |
An alternative approach keeping things more modular could be to wrap this messy part into a helper function:
And return Then user could do something like this:
|
I think I'd rather think of the ebirdST data (prebreeding start, etc) within the bf object as coming directly from S&T and not modify it. |
https://birdflow-science.github.io/BirdFlowR/reference/sample_distr.html |
I think I'm going to merge
After #110 we then can replace @slager does that work for you? After the discussion above the only remaining difference between the two functions was whether the starting locations are sampled from the distributions. |
That works. It could be nice to have a flag to sample from ebirdst distribution or sample from model marginal distribution. |
You can now do everything with
You can use any of the time arguments supported by
|
I think it could maybe be useful to also be able to pass custom start and end inputs to route_migration, that would be processed by lookup_timestep to replace the season argument. Running into this with a species where I disagree with the eBird S&T assigned dates for the end of migration. I could also see this being useful for plenty of other applications, like shorter-term predictions of where birds go.
The text was updated successfully, but these errors were encountered: