Skip to content

Commit

Permalink
More straightforward text label for ECCO visualization (#250)
Browse files Browse the repository at this point in the history 
* More straightforward label for ECCO data

It's confusing to think about things in terms of depth when our entire interface is in terms of height.

* Update inspect_ecco_data.jl

---------

Co-authored-by: Navid C. Constantinou <[email protected]>
  • Loading branch information
@glwagner @navidcy
glwagner and navidcy authored Nov 17, 2024
1 parent cf26e73 commit 801ba06
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion examples/inspect_ecco_data.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Colorbar(fig[1, 2], hmT, label="Temperature (ᵒC)")
Colorbar(fig[2, 2], hmS, label="Salinity (psu)")

z = znodes(grid, Center())
depth_str = @lift @sprintf("%.1f meters depth", -z[$k])
depth_str = @lift @sprintf("z = %d meters", z[$k])
text!(axT, 50, 50, text=depth_str, color=:lemonchiffon, justification=:center, fontsize=20)
text!(axS, 50, 50, text=depth_str, color=:lemonchiffon, justification=:center, fontsize=20)

Expand Down

2 comments on commit 801ba06

@navidcy
Copy link
Collaborator

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 updated: JuliaRegistries/General/119603

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.2.3 -m "<description of version>" 801ba0643d1ed99d1f707432c942bcef69321672
git push origin v0.2.3

Please sign in to comment.