Skip to content

Commit

Permalink
use a fill-value different from data values
Browse files Browse the repository at this point in the history
  • Loading branch information
@Alexander-Barth
Alexander-Barth committed Jan 29, 2024
1 parent ee6918c commit f87bcb0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion test/test_scaling.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ for Tbase in (UInt8, Int8, Float32, Float64, Int64, Char, String)

if Tbase == String
data[:,:] = rand(string.('a':'z'),size(data))
fv = "z"
fv = "X"
else
data[:,:] = rand(Tbase(0):Tbase(10),size(data))
fv = Tbase(99)
Expand Down

2 comments on commit f87bcb0

@Alexander-Barth
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

Release notes

  • allow to use a different value than missing to mask _FillValue (experimental)

@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/99827

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.3.3 -m "<description of version>" f87bcb0cce3e1e5b45e580470fb97d6e5711eda6
git push origin v0.3.3

Please sign in to comment.