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

Climate velocity code #202

Open
tpoisot opened this issue Oct 8, 2023 · 5 comments
Open

Climate velocity code #202

tpoisot opened this issue Oct 8, 2023 · 5 comments

Comments

@tpoisot
Copy link
Member

tpoisot commented Oct 8, 2023

This is something I've been meaning to add for a little while - this might be a case of porting the code @gottacatchenall wrote for BIAB2?

@gottacatchenall
Copy link
Member

gottacatchenall commented Oct 8, 2023

The BIAB2 code is a hasty port of some boilerplate from for PCAing a set of layers, with code tacked on to use tiffs specified with input jsons. Should be straightforward enough to implement climate velocity using SimpleSDMDatasets as the source of rasters

@gottacatchenall
Copy link
Member

gottacatchenall commented Oct 8, 2023

Curious if you have thoughts on chelsa-cmip6. Could be smart for SDT to provide an easy API for custom temporal ranges and specified GCMs. Maybe not for the first climate velocity release, but I think there could be something there

@tpoisot
Copy link
Member Author

tpoisot commented Oct 8, 2023

Definitely as part of SimpleSDMDatasets -- I haven't read deeply enough to get a good sense of the amount of work required, but I feel like this shouldn't interact with the functions for climate velocity (but it'll make this more useful when it's there)?

@tpoisot
Copy link
Member Author

tpoisot commented Oct 8, 2023

some boilerplate from for PCAing a set of layers

I think we discussed wrapping MultivariateStats at some point, this might be the time to do it?

@gottacatchenall
Copy link
Member

gottacatchenall commented Oct 9, 2023

See #204 (comment), we did but it required explicitly calling MultivariateStats.fit to not conflict with StatsBase, which isn't aesthetically wonderful

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

No branches or pull requests

2 participants