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

Recipe template for using ESM Datastores - ACCESS-NRI Catalog & user defined #6

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

charles-turner-1
Copy link
Contributor

Demo notebook.

@charles-turner-1 charles-turner-1 changed the title Recipe template for using ESM Recipe template for using ESM Datastores - ACCESS Dec 3, 2024
@charles-turner-1 charles-turner-1 changed the title Recipe template for using ESM Datastores - ACCESS Recipe template for using ESM Datastores - ACCESS-NRI Catalog & user defined Dec 3, 2024
@charles-turner-1
Copy link
Contributor Author

@anton-seaice Are you able to take a look & tell me if this is roughly what you had in mind?

Closes #5 .

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

@anton-seaice anton-seaice Dec 4, 2024

Choose a reason for hiding this comment

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

Line #5.          "catalog_directory" : "./catalog_demo",

In om3-scripts we just put it into the output folder for a model run. Which maybe is not super useful because we don't want to in this example


Reply via ReviewNB

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

@anton-seaice anton-seaice Dec 4, 2024

Choose a reason for hiding this comment

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

Line #6.          "catalog_name" : "demo_datastore",

In om3-scripts we call this intake_datastore


Reply via ReviewNB

Copy link
Collaborator

Choose a reason for hiding this comment

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

Does this replace building_Intake_Datastore_1Experiment.ipynb ?

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@charles-turner-1
Copy link
Contributor Author

Sorry, not quite sure how but both notebooks got caught in this PR - I was more interested in your thoughts on the other notebook

@anton-seaice
Copy link
Collaborator

I was thinking more a template than this - e.g. something people would copy and modify. This can be copied and modified too, just needs deleting lots of comments.

This version has useful information for people getting started, so its good in that way and we don't want duplication.

Thoughts ? Maybe leave as is? Or maybe try cull a little to term into into a template for new notebooks ?

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

Successfully merging this pull request may close these issues.

2 participants