Skip to content

Conversation

ongqingyee
Copy link
Collaborator

Simplify https://github.com/COSIMA/cosima-recipes/blob/main/DocumentedExamples/Cross-slope_section.ipynb into two examples, one for a transect and one for an along/cross slope decomposition.

Originally posted by @ongqingyee in #332 (comment)

Original Examples/Cross-slope_section.ipynb now separated into two scripts. Any advice on making it model agnostic would be great - having to manually drop geolat and geolon for only one model does not seem optimal.

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@navidcy
Copy link
Collaborator

navidcy commented Jul 19, 2024

thanks @ongqingyee!!

I merged main and simplified a bit -- very minor things.

This is ready to be reviewed... Anybody?

@navidcy navidcy requested a review from a team July 19, 2024 12:54
@navidcy navidcy added 🛸 updating An existing notebook needs to be updated ready to review ❣️ labels Jul 19, 2024
@@ -0,0 +1,967 @@
{
Copy link
Collaborator

@adele-morrison adele-morrison Jul 24, 2024

Choose a reason for hiding this comment

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

Can delete "example" in title. I think we've been trying to make the titles the same as the notebook filenames.


Reply via ReviewNB

@@ -0,0 +1,967 @@
{
Copy link
Collaborator

@adele-morrison adele-morrison Jul 24, 2024

Choose a reason for hiding this comment

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

Anything we can do about these RuntimeWarnings? Maybe at the very least we could add a comment about why they are there and that they are ok to ignore?


Reply via ReviewNB

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

# warnings are for dividing by NaN/0, 

# i.e. when there is no topographic gradient and warning can be ignored

Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:42Z
----------------------------------------------------------------

"cross-slopE"


Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:43Z
----------------------------------------------------------------

Line #6.    pot_rho_2

Does the array need to be printed out here?


Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:44Z
----------------------------------------------------------------

Line #3.    pot_rho_2

Again, do we need to print the array here?


Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:44Z
----------------------------------------------------------------

Line #3.    pot_temp

Also here?


Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:45Z
----------------------------------------------------------------

Line #5.    #pot_rho_2 = grid_depth.interp(grid_depth.interp(pot_rho_2, axis = 'X').chunk({'yt_ocean': 500}) , axis = 'Y', boundary = 'extend')#.sel(yu_ocean=lat_slice).sel(st_ocean=slice(0,depth))

Is this commented code needed?


Copy link

review-notebook-app bot commented Jul 24, 2024

View / edit / reply to this conversation on ReviewNB

adele-morrison commented on 2024-07-24T10:34:46Z
----------------------------------------------------------------

Line #3.    pot_rho_2_section.load()

Could add a semicolon after this to suppress printing.


@adele-morrison
Copy link
Collaborator

adele-morrison commented Jul 24, 2024

Added some minor comments, but otherwise looks good to me @ongqingyee!

…mples/Cross-slope_section.ipynb. Ready to be merged.
@ongqingyee
Copy link
Collaborator Author

Changes have been made, thanks Adele!

Changes now saved to my forked repo. How should I merge it into main?

@navidcy
Copy link
Collaborator

navidcy commented Aug 19, 2024

@ongqingyee,

first @adele-morrison should approve

then we should resolve the conflicts; could you do that or shall I? I am happy to deal with this when all dust settles (meaning, when all the edits-reviewing is done)

@navidcy
Copy link
Collaborator

navidcy commented Aug 19, 2024

Changes now saved to my forked repo. How should I merge it into main?

by "saved" you mean the edits are pushed to your fork, right?

Copy link
Collaborator

@adele-morrison adele-morrison left a comment

Choose a reason for hiding this comment

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

Looks good Ellie. Only comment is that the fontsize on the Cross-slope_section plot seems unnecessarily large, though happy to ignore if you just want to merge.

@navidcy navidcy merged commit 3584105 into COSIMA:main Aug 19, 2024
2 checks passed
@navidcy navidcy mentioned this pull request Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants