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

Boosted Regression Tree SDM pipeline #168

Open
jmlord opened this issue Sep 11, 2024 · 9 comments
Open

Boosted Regression Tree SDM pipeline #168

jmlord opened this issue Sep 11, 2024 · 9 comments
Labels
COP16 pipeline Linked to a pipeline or underlying scripts

Comments

@jmlord
Copy link
Contributor

jmlord commented Sep 11, 2024

Currently sandwiched with sampling priorisation in this PR:
#99

We should make a separate pipeline for BRT, test and merge it.

@jmlord jmlord added COP16 pipeline Linked to a pipeline or underlying scripts labels Sep 11, 2024
@tpoisot
Copy link

tpoisot commented Sep 11, 2024

Agreed - @gottacatchenall and I can take the lead on this

@gottacatchenall
Copy link
Contributor

Agreed, re #99 (comment), this can also include separating crossvalidation and performance metric computation into separate scripts from the BRT itself

@jmlord
Copy link
Contributor Author

jmlord commented Sep 11, 2024

@tpoisot @gottacatchenall
Do you think this could happen in September? So we have time to merge, re-run examples, feature them on the website by COP16?

(@JoryGriffith and I can assist if need be)

@tpoisot
Copy link

tpoisot commented Sep 11, 2024

I think a bare bones version, yes, but also as @gottacatchenall said the next logical step is to provide cross validation as steps for all sdm pipelines to use. This can happen post COP.

@jmlord
Copy link
Contributor Author

jmlord commented Sep 12, 2024

I agree! As you know, I always prefer to go incremental.

Could we just replace the maxent step with the BRT step in the other pipeline?

@gottacatchenall
Copy link
Contributor

Could we just replace the maxent step with the BRT step in the other pipeline?

Based on a brief look that should be pretty easy. PoisotLab/SpeciesDistributionToolkit.jl#227 (SimpleSDMLayers.jl v1.0) is very close to being merged, so once that's done and on the Julia Pkg registry, I'll work on this

@JoryGriffith
Copy link
Contributor

Ideally we would have a working pipeline for the sampling prioritization done for COP16 as well. Do you think that would be feasible once the BRT pipeline is working?

@tpoisot
Copy link

tpoisot commented Sep 12, 2024

@JoryGriffith very likely (and I agree about the importance of having it)

@gottacatchenall
Copy link
Contributor

gottacatchenall commented Sep 17, 2024

Ideally we would have a working pipeline for the sampling prioritization done for COP16 as well. Do you think that would be feasible once the BRT pipeline is working?

There's a few different options here

  1. Simplest -- One of the outputs of the BRT SDM is a map of model uncertainty. At the GEO-BON conference last year we presented this as a priority map for where to sample. We'll definitely have that by COP, hopefully by Thursday when @tpoisot and I will spend few hours on this

  2. Less Simple -- I've been procrastinating a major refactor of BONs.jl (v0.3  PoisotLab/BiodiversityObservationNetworks.jl#65) until SDMLayers v1.0 was ready. It'd be pretty easy to add an extra pipeline that takes the SDM uncertainty from (1) and the uses an updated version of BONs.jl to sample actual coordinates from it proportional to uncertainty, and getting v0.3  PoisotLab/BiodiversityObservationNetworks.jl#65 merged is something I've planned to do in the next month or so anyway.

  3. Even Less Simple -- With BONs.jl code as is, I've been able to come up with a toy-example of what selecting sites for a national Canadian BON (CAN-BON) would look like. This would be much truer to the spirit/name "BON-in-a-Box", but would require a bit more work than the first two options to port to a pipeline. This might work better in the paper itself though, I've included an example figure in the concept manuscript google-doc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
COP16 pipeline Linked to a pipeline or underlying scripts
Projects
Status: In progress
Development

No branches or pull requests

4 participants