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

How to subset - filter data for different species #1

Open
ericward-noaa opened this issue Aug 13, 2019 · 5 comments
Open

How to subset - filter data for different species #1

ericward-noaa opened this issue Aug 13, 2019 · 5 comments

Comments

@ericward-noaa
Copy link
Collaborator

Should we filter surveys to the range that species are observed?

@jordanwatson
Copy link

If you don't, then wouldn't zeroes in the data bias results on the boundaries?

@ericward-noaa
Copy link
Collaborator Author

Right now the way that we're doing it is restricting the estimation to the spatial domain that contains positive tows for each species. There's probably other ways to do this, but wanted to flag it as a topic for discussion / input

@jordanwatson
Copy link

I guess that by leaving the extended range in there, you provide the opportunity for the species distribution to shift, which of course is the whole question....

@Lewis-Barnett-NOAA
Copy link
Contributor

Yes, Eric and I discussed trying a more conservative threshold for defining the spatial domain in some follow-up work. Something like the convex hull that encompasses 95% of the positive observations?

@ericward-noaa
Copy link
Collaborator Author

Our subgroup was worried about the potential to have estimates of environmental effects be biased with all the zeros. For example, if a species was only observed in the northern half of the Cal Current, and the temp gradient means it's warmer in the south, fitting a model to the full dataset would overestimate the temp effect on ranges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants