Skip to content

Commit

Permalink
semver(sdt): v0.1.3 (#286)
Browse files Browse the repository at this point in the history
* semver(sdt): v0.1.3

* doc: change gainloss
  • Loading branch information
tpoisot authored Sep 28, 2024
1 parent 1759419 commit b6bf5ee
Show file tree
Hide file tree
Showing 5 changed files with 11 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "SpeciesDistributionToolkit"
uuid = "72b53823-5c0b-4575-ad0e-8e97227ad13b"
authors = ["Timothée Poisot <timothee.poisot@umontreal.ca>"]
version = "0.1.2"
version = "0.1.3"

[deps]
Distances = "b4f34e82-e78d-54a5-968a-f98e89d6e8f7"
Expand Down
1 change: 1 addition & 0 deletions docs/make.jl
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,7 @@ makedocs(;
"manual/pseudoabsences.md",
"manual/polygons.md",
"manual/gadm.md",
"manual/utilities.md"
],
],
)
Expand Down
5 changes: 5 additions & 0 deletions docs/src/manual/utilities.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Other utility functions

```@docs
gainloss
```
2 changes: 1 addition & 1 deletion docs/src/tutorials/sdemo.jl
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ prd = predict(sdm, layers; threshold = false)
# Decision trees, in oredr to avoid overfitting, are pretty small -- indeed, the
# default version in `SDeMo` is capped at 12 nodes, with a maximal depth of 7.
# This is because there is no limit to how much decision trees can overfit. But
# as a result, the map representing these predictions can look a little coase:
# as a result, the map representing these predictions can look a little coarse:

# fig-initial-map
f = Figure(; size = (600, 300))
Expand Down
4 changes: 3 additions & 1 deletion src/utilities.jl
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@
gainloss(contemporary::SDMLayer{Bool}, future::SDMLayer{Bool})
Returns a layer with values -1, 0, and 1 corresponding to the difference in
ranges.
ranges. The two layers given as input must be layers with boolean values where
`true` indicates that the pixel is in the range. The presence of `false` pixels
is irrelevant as these are ignored internally.
"""
function gainloss(contemporary::SDMLayer{Bool}, future::SDMLayer{Bool})
rangemask = nodata((contemporary)|(future), false)
Expand Down

2 comments on commit b6bf5ee

@tpoisot
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/116230

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.3 -m "<description of version>" b6bf5ee2345dabb1cf8bc433c909a6d45dabbfcf
git push origin v0.1.3

Please sign in to comment.