pyww3
Python wrapper for NOAA’s WaveWatchIII (WW3) Model.
This package wraps around the WW3’s executables by properly defining the namelists (.nml) required to drive the model’s executables.
Requirements
pyww3 requires WaveWatchIII to be properly compiled with netCDF4 available in your $PATH. Please follow the installation instructions from NOAA.
Programs supported: ww3_grid, ww3_prnc, ww3_shel, ww3_ounf, ww3_ounp and ww3_bounc.
Note that I don’t have plans to support programs that require ASCII input (such as ww3_outf) even tough they may have an associated namelist.
You will need python 3.7+ because of the extensive usage of dataclasses.
Getting Started
All the implemented classes have the same structure and methods. For example, to run simulation with ww3_shel you do:
import datetime
from pyww3.shel import WW3Shel
W = WW3Shel(nproc=8,
runpath="tests/test_run/",
mod_def="tests/test_data/GLOB_60_MIN.ww3grid",
domain_start=datetime.datetime(2010, 1, 1, 0),
domain_stop=datetime.datetime(2010, 1, 1, 2),
input_forcing_winds=True,
input_forcing_ice_conc=True,
date_field_stride=3600,
date_point_stride=3600,
date_restart_stride=3600,
type_point_file="tests/test_data/boundary_point_list.txt")
W.to_file() # writes ww3_shel.nml in the run path
W.run() # run the simulation
print(W.stdout) # print the output given by WW3
Credits
This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
WW3 is maintained and distributed by NOAA’s Environmental Modeling Center (EMC).
Disclaimer
There is no warranty for the program, to the extent permitted by applicable law except when otherwise stated in writing the copyright holders and/or other parties provide the program “as is” without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. the entire risk as to the quality and performance of the program is with you. should the program prove defective, you assume the cost of all necessary servicing, repair or correction.
History
0.1.0 (2021-08-25)
First release on PyPI.
Metadata
Release files for pyww3 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyww3-0.1.4.tar.gz | 50.1 kB | Without provenance | Details |
Release files / pyww3-0.1.4.tar.gz
| Download URL | pyww3-0.1.4.tar.gz |
|---|---|
| Size | 50.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5afc54b82cb7b76dde02fd63b610b5c18c5802a79c8780cf630618c687e25635
|
|
BLAKE2b-256 checksum How to use checksums |
0f8ee9a74cdf39f711578a2b4b8afd6f13e3572633a333ffbc3a5d413c2412fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/3.10.0 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.8.11
|
Security for pyww3 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.