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

Document requirements and Implement model run(s) for ADCIRC (ADvanced CIRCulation) #58

Open
4 tasks
ZacharyWills opened this issue Jun 30, 2023 · 9 comments

Comments

@ZacharyWills
Copy link
Contributor

Welcome to the IOOS Cloud-Sandbox!

Expected Behavior

A ADCIRC (ADvanced CIRCulation) model version should be selected, compiled and made available to users of the Cloud-Sandbox.

Current Behavior

ADCIRC (ADvanced CIRCulation) is not available.

Possible Solution

The Source should be compiled periodically, a set of static configuration examples made available, and documentation should be written to describe not only how this is done but also the lifecycle of this model.

Steps to Reproduce or Implement:

  • ADCIRC source code acquired
  • Compilation and test-runs automated for availability
  • Available Data acquired, and it's location documented for community use
  • Documentation of full ADCIRC usage, necessary inputs, output location, etc. made available

Context

The National Ocean Service has adopted four different community code packages for use in the operational Coastal
Ocean Modeling Framework (COMF):

Your Environment

  • Version used: To be updated upon Selection
  • Software Name and version: ADCIRC (ADvanced CIRCulation) model
  • Operating System and version (desktop or mobile): Amazon Linux 2
  • Link to your project/sponsor: [email protected]
@KatherinePowell-NOAA KatherinePowell-NOAA added this to the Run at least one baseline test case for each named model milestone Aug 31, 2023
@janahaddad
Copy link

Hello, I'm getting familiar with the sandbox and was trying to compile ADCIRC using cmake in the NOAA EC2 instance (for eventually testing ADCIRC+SWAN model runs for CO-OPS CORA)

Cmake is not finding a fortran compiler on the system, and I'm wondering if I'm going about this the wrong way. Should I be cloning cloud-sandbox repo first? or can you provide a path for a fortran compiler? or should I install gfortran in my user directory?

image

Here's the full output from the Cmake GUI configuration:
image

thanks for your help!

cc @Michael-Lalime, @greg-dusek

@Michael-Lalime
Copy link

Michael-Lalime commented Apr 3, 2024

@ZacharyWills @KatherinePowell-NOAA @patrick-tripp I thought we had a Fortran compiler in the sandbox? Can any of you help @janahaddad and @greg-dusek with this problem with cmake and Fortran?

@patrick-tripp
Copy link
Member

patrick-tripp commented Apr 3, 2024

Hi Jana,

You need to load the appropriate modules that contain the libraries and compilers you want to use.
'spack load' might also work also.
'module avail'
'spack find'

I am assuming you ran the setup-instance script when your sandbox was deployed?
That will install everything you need.

@ZacharyWills
Copy link
Contributor Author

Here's the fortran install/version:

sudo yum -y install intel-oneapi-compiler-fortran-2023.1.0.x86_64

@patrick-tripp
Copy link
Member

The above is for an older version and should be removed. When the sandbox is deployed it will automatically setup all of the software and libraries you need using the setup-instance.sh script. If it didn't run, you can manually run the scripts/setup-instance.sh script which will use Spack to install everything you need with the proper dependencies.

@Michael-Lalime
Copy link

Michael-Lalime commented Apr 3, 2024 via email

@janahaddad
Copy link

janahaddad commented Apr 3, 2024

I am assuming you ran the setup-instance script when your sandbox was deployed?
That will install everything you need.

@patrick-tripp No, where is setup-instance? I believe that I'm working in an environment that already has the latest cloud-sandbox deployed, right @Michael-Lalime?

Thought I tried module load but I guess I didn't! Will give that a try. If that doesn't work, I'll try the spack option with the setup-instance.sh script. Thanks y'all

@patrick-tripp
Copy link
Member

patrick-tripp commented Apr 3, 2024

OK, In that case don't need to run the setup-instance.sh script. You only need to specify the modules you need to use in your build and run scripts. You can see the LiveOcean or nosofs models as a reference. This will enable all of the Intel compilers, MPI, ESMF, HDF, netCDF, etc.

@Michael-Lalime
Copy link

Michael-Lalime commented Apr 3, 2024 via email

@KatherinePowell-NOAA KatherinePowell-NOAA changed the title ADCIRC (ADvanced CIRCulation) Document requirements and Implement model run(s) for ADCIRC (ADvanced CIRCulation) Aug 16, 2024
@KatherinePowell-NOAA KatherinePowell-NOAA removed this from the Run at least one baseline test case for each named model milestone Aug 29, 2024
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

No branches or pull requests

5 participants