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 Finite Volume Community Ocean Model (FVCOM) #57

Open
1 of 4 tasks
ZacharyWills opened this issue Jun 30, 2023 · 2 comments

Comments

@ZacharyWills
Copy link
Contributor

ZacharyWills commented Jun 30, 2023

Welcome to the IOOS Cloud-Sandbox!

Expected Behavior

A Finite Volume Community Ocean Model (FVCOM) version should be selected, compiled and made available to users of the Cloud-Sandbox.

Current Behavior

Finite Volume Community Ocean Model (FVCOM) 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:

  • FVCOM source code acquired
  • Compilation and test-runs automated for availability
  • Available Data acquired, and it's location documented for community use
  • Documentation of full FVCOM 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: Finite Volume Community Ocean Model (FVCOM)
  • 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
@ZacharyWills
Copy link
Contributor Author

@KatherinePowell-NOAA
Copy link

I reviewed the FVCOM GitHub repo Readme file, cloned the source code, and started evaluating the installation steps.

The above was discussed with Zach, Michael, and Breanna and we noted several things:

1 - The GitHub instructions do not specify the versions to use for compilers or libraries (i.e., "Both NetCDF-C and NetCDF-Fortran are required. https://www.unidata.ucar.edu/software/netcdf/")
2 - Several optional Libraries are listed, but exact use cases will need to be identified.
3 - Installation instructions are incomplete and/or too broad (i.e., "Generate the module dependencies of FVCOM codes. This step is required only when there are new codes added.")
4 - The provided "Testsuite" (https://drive.google.com/file/d/1xwcFjzkSNT26FBu83pq2I8oIGzPqnjUn/view):
- includes a DOC folder with a User Manual dated July 2013
- includes an Examples folder, however there is little information about or guidance on how to use this data

@KatherinePowell-NOAA KatherinePowell-NOAA changed the title Finite Volume Community Ocean Model (FVCOM) Document requirements and Implement model run(s) for Finite Volume Community Ocean Model (FVCOM) 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

2 participants