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

New public release #5

Merged
merged 13 commits into from
Jul 29, 2024
Merged

New public release #5

merged 13 commits into from
Jul 29, 2024

Conversation

oliverwm1
Copy link
Collaborator

Update public code to latest.

@mcgibbon
Copy link
Contributor

When we do this in the future, I would suggest having the first commit be a replacement rather than deletion of the code, so it's possible to see what files have changed. I don't think this is super important to review but I was curious to check it for any potential issues.

Copy link
Contributor

@mcgibbon mcgibbon left a comment

Choose a reason for hiding this comment

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

LGTM. Some minor comments.

@@ -1,4 +1,4 @@
__version__ = "0.1.0"
__version__ = "0.2.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

We should update this in full-model also.

README.md Outdated
@@ -1,8 +1,8 @@
# ACE: AI2 Climate Emulator
This repo contains the inference code accompanying "ACE: A fast, skillful learned global atmospheric model for climate prediction" ([arxiv:2310.02074](https://arxiv.org/abs/2310.02074)).

## DISCLAIMER
This is rapidly changing research software. We make no guarantees of maintaining backwards compatibility.
## Documentation
Copy link
Contributor

Choose a reason for hiding this comment

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

Did you mean to remove the DISCLAIMER?

I would suggest not adding a header for a documentation link until we actually have said link. But we should probably include instructions for building the docs locally.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It was intentional—we have a note in the docs about this being research software which I think is sufficient.

Sounds good, I'll remove the documentation section. I don't think we need to bother with local build instructions since we'll have the RTD page up soon.

mcgibbon
mcgibbon previously approved these changes Jul 26, 2024
Copy link
Contributor

@mcgibbon mcgibbon left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines -4 to -5
## DISCLAIMER
This is rapidly changing research software. We make no guarantees of maintaining backwards compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we mean to remove this disclaimer?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, this was intentional. There is a similar warning in the docs.

Copy link
Contributor

@frodre frodre left a comment

Choose a reason for hiding this comment

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

Thanks, @oliverwm1!

I was thinking about most of the configuration/data processing files in the scripts folder. Generally, I feel like it adds a lot of noise since there are a few important files for generating stats / ENSO metrics among them, but they are separated by folder so people could also probably just look for what they need.

Personally, since I think this will be one of our more widely seen and used repositories, I think it feels better just to have only relevant files distributed in a package rather than our internal processing. I would vote for cleaning up scripts. BUT, I realize this also adds an inconvenient divergence when merging into this repository as those scripts might be updated in full-model and create conflicts if they are deleted here.

Also, what's the plan for the documentation? Add that in after this merge? We could also consider linking the ACE colab notebook with a note at the beginning of the quickstart.

Makefile Outdated
@@ -1,11 +1,16 @@
VERSION ?= $(shell git rev-parse --short HEAD)
IMAGE ?= fme
REGISTRY ?= registry.nersc.gov/m4492/ai2cm
Copy link
Contributor

Choose a reason for hiding this comment

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

Could probably remove the NERSC specific items for REGISTRY and push_shifter_image

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yup thanks for reminder—thought I had done this.

@oliverwm1
Copy link
Collaborator Author

Personally, since I think this will be one of our more widely seen and used repositories, I think it feels better just to have only relevant files distributed in a package rather than our internal processing. I would vote for cleaning up scripts. BUT, I realize this also adds an inconvenient divergence when merging into this repository as those scripts might be updated in full-model and create conflicts if they are deleted here.

I'm not too worried about conflicts. I did already delete some of the things in the scripts directory but agreed there is a lot of stuff in data_process that is not widely applicable. I'll make a commit deleting everything other than get_stats.py and see what others think.

Also, what's the plan for the documentation? Add that in after this merge? We could also consider linking the ACE colab notebook with a note at the beginning of the quickstart.

Yes, building the docs / hosting on RTD will be a follow on PR. Agreed, once this is merged to main and the colab notebook can reflect that, we can add a link.

Copy link
Contributor

@frodre frodre left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the cleanup in the scripts folder

@oliverwm1 oliverwm1 merged commit 7178ce2 into main Jul 29, 2024
4 checks passed
@oliverwm1 oliverwm1 deleted the v2-rc2 branch July 29, 2024 15:53
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.

3 participants