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

Update Benchmark branch to use NDSL v2024.09.00 #96

Merged
merged 21 commits into from
Jan 6, 2025

Conversation

fmalatino
Copy link
Contributor

Description
Include a summary of the change and which issue is fixed. Please also include
relevant motivation and context. List any dependencies that are required for
this change.

Fixes # (issue)
If this is a hotfix to a released version, please specify it.

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note
any relevant details for your test configuration (e.g. compiler, OS). Include
enough information so someone can reproduce your tests.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules
  • New check tests, if applicable, are included

oelbert and others added 20 commits April 19, 2024 09:47
* updated generate_eta_files

* remove notebook, add script

* lint

---------

Co-authored-by: mlee03 <Mikyung.Lee@lscamd50-d.gfdl.noaa.gov>
* Updates to allow use of python3.11

* Removed main_unit_tests.yml as it is covered by tests in containers

* Updated images for unit tests with openmpi and mpich
* updated generate_eta_files

* remove notebook, add script

* lint

* correct path

* update constraints

* python3 execute

* Update main_unit_tests_mpich.yaml

* Update main_unit_tests_mpich.yaml

* update input directory

* get ..s correct

* lint

---------

Co-authored-by: mlee03 <Mikyung.Lee@lscamd50-d.gfdl.noaa.gov>
…A-GFDL#89)

* test

* tet

* fix test dir

* test

* checkout pace

* rename

* test

* rm

* remove dir

* fix name

* test

* pyshield

* test

* fix trigger mistake

* test

* change lint version

* remove push

* lint

---------

Co-authored-by: mlee03 <Mikyung.Lee@lscamd50-d.gfdl.noaa.gov>
…tdated pull request template (NOAA-GFDL#86)

* Changed workflows to use python 3.11.7, added pytest-subtests to requirments_dev.txt

* Matched package dependencies between main and develop branches

* Updating constraints file

* Updating Dockerfile to use 3.11-slim-bookworm base python image
* fix trigger mistake

* fix spacking

* update yaml files

* rename lint.yaml

* remove backup yaml file

* simply pull request trigger

* beloved lint

---------

Co-authored-by: mlee03 <Mikyung.Lee@lscamd50-d.gfdl.noaa.gov>
…FDL#88)

* add build script for intel oneapi and gcc compiler separately

* update the python version and remove the link time optimization option for gcc
…FDL#99)

* Updated README to include directions for generating eta files

* Linting

* Updated baroclinic_c2.yaml to generate zarr output
@@ -0,0 +1,36 @@
#!/usr/bin/env bash

# Example bash script to install Pace to run bare-metal on Gaea's c4 cluster
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this supposed to reference c5?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should. I am planning on making these changes before making this PR ready for review

Comment on lines 15 to 18
export CC=`which gcc`
export CXX=`which g++`
export MPICC=`which mpicc`
export MPICXX=`which mpicxx`
Copy link
Contributor

Choose a reason for hiding this comment

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

If these are on the cray, shouldn't they be referencing the HPE development environment wrappers of cc, ftn, and CC?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes they should. I will be altering this file before making this PR ready for review

@fmalatino fmalatino marked this pull request as ready for review January 6, 2025 18:41
@fmalatino fmalatino merged commit c64fa64 into NOAA-GFDL:benchmark Jan 6, 2025
2 checks passed
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.

4 participants