A curated list of open technology projects to sustain a stable climate, energy supply, biodiversity and natural resources.

MHKiT-Python

Provides the marine renewable energy community tools for data processing, visualization, quality control, resource assessment, and device performance.
https://github.com/MHKiT-Software/MHKiT-Python

Category: Renewable Energy
Sub Category: Hydro Energy

Keywords

marine-renewable-energy mhkit mhkit-python python quality-control visualization

Keywords from Contributors

mhkit-matlab mhk mhkit-documentation snl-applications hydrodynamics wave-energy boundary-element-method potential-flow water-wave

Last synced: about 12 hours ago
JSON representation

Repository metadata

MHKiT-Python provides the marine renewable energy (MRE) community tools for data processing, visualization, quality control, resource assessment, and device performance.

README.md

MHKiT-Python

MHKiT-Python is a Python package designed for marine renewable energy applications to assist in
data processing and visualization. The software package include functionality for:

  • Data processing
  • Data visualization
  • Data quality control
  • Resource assessment
  • Device performance
  • Device loads

Documentation

MHKiT-Python documentation includes overview information, installation instructions, API documentation, and examples.
See the MHKiT documentation for more information.

Installation

MHKiT-Python requires Python (3.8, 3.9, 3.10, 3.11) along with several Python
package dependencies. MHKiT-Python can be installed from PyPI using the command:

pip install mhkit

See installation instructions for more information.

Copyright and license

MHKiT-Python is copyright through the National Renewable Energy Laboratory,
Pacific Northwest National Laboratory, and Sandia National Laboratories.
The software is distributed under the Revised BSD License.
See copyright and license for more information.

Issues

The GitHub platform has the Issues feature that is used to track ideas, feedback, tasks, and/or bugs. To submit an Issue, follow the steps below. More information about GitHub Issues can be found here

  1. Navigate to the MHKiT-Python main page
  2. 2.Under the repository name (upper left), click Issues.
  3. Click New Issue.
  4. If the Issue is a bug, use the Bug report template and click Get started, otherwise click on the Open a blank issue link.
  5. Provide a Title and description for the issue. Be sure the title is relevant to the issue and that the description is clear and provided with sufficient detail.
  6. When you're finished, click Submit new issue. The developers will follow-up once the issue is addressed.

Creating a fork

The GitHub platform has the Fork feature that facilitates code modification and contributions. A fork is a new repository that shares code and visibility settings with the original upstream repository. To fork MHKiT-Python, follow the steps below. More information about GitHub Forks can be found here

  1. Navigate to the MHKiT-Python main page
  2. Under the repository name (upper left), click Fork.
  3. Select an owner for the forked repository.
  4. Specify a name for the fork. By default, forks are named the same as their upstream repositories.
  5. Add a description of your fork (optional).
  6. Choose whether to copy only the default branch or all branches to the new fork. You will only need copy the default branch to contribute to MHKiT-Python.
  7. When you're finished, click Create fork. You will now have a fork of the MHKiT-Python repository.

Creating a branch

The GitHub platform has the branch feature that facilitates code contributions and collaboration amongst developers. A branch isolates development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. To create a branch of your forked MHKiT-Python repository, follow the steps below. More information about GitHub branches can be found here

  1. Navigate to your fork of MHKiT-Python (see instructions above)
  2. Above the list of files, click Branches.
  3. Click New Branch.
  4. Enter a name for the branch. Be sure to select MHKiT-Software/MHKiT-Python:master as the source.
  5. Click Create branch. You will now have a branch on your fork of MHKiT-Python that you can use to work with the code base.

Creating a pull request

The GitHub platform has the pull request feature that allows you to propose changes to a repository such as MHKiT-Python. The pull request will allow the repository administrators to evaluate the pull request. To create a pull request for MHKiT-Python repository, follow the steps below. More information about GitHub pull requests can be found here

  1. Navigate to the MHKiT-Python main page
  2. Above the list of files, click Pull request.
  3. On the compare page, click Compare accross forks.
  4. In the "base branch" drop-down menu, select the branch of the upstream repository you'd like to merge changes into.
  5. In the "head fork" drop-down menu, select your fork, then use the "compare branch" drop-down menu to select the branch you made your changes in.
  6. Type a title and description for your pull request.
  7. If you want to allow anyone with push access to the upstream repository to make changes to your pull request, select Allow edits from maintainers.
  8. To create a pull request that is ready for review, click Create Pull Request. To create a draft pull request, use the drop-down and select Create Draft Pull Request, then click Draft Pull Request. More information about draft pull requests can be found here
  9. MHKiT-Python adminstrators will review your pull request and contact you if needed.

Code Formatting in MHKiT

MHKiT adheres to the "black" code formatting standard to maintain a consistent and readable code style. Developers contributing to MHKiT have several options to ensure their code meets this standard:

  1. Manual Formatting with Black: Install the 'black' formatter and run it manually from the terminal to format your code. This can be done by executing a command like black [file or directory].

  2. IDE Extension: If you are using an Integrated Development Environment (IDE) like Visual Studio Code (VS Code), you can install the 'black' formatter as an extension. This allows for automatic formatting of code within the IDE.

  3. Pre-Commit Hook: Enable the pre-commit hook in your development environment. This automatically formats your code with 'black' each time you make a commit, ensuring that all committed code conforms to the formatting standard.

For detailed instructions on installing and using 'black', please refer to the Black Documentation. This resource provides comprehensive guidance on installation, usage, and configuration of the formatter.


Owner metadata


GitHub Events

Total
Last Year

Committers metadata

Last synced: 4 days ago

Total Commits: 550
Total Committers: 21
Avg Commits per committer: 26.19
Development Distribution Score (DDS): 0.622

Commits in past year: 27
Committers in past year: 4
Avg Commits per committer in past year: 6.75
Development Distribution Score (DDS) in past year: 0.519

Name Email Commits
ssolson s****n@s****v 208
rpauly18 r****y@n****v 182
kaklise k****e@s****v 35
Kelley Ruehl k****l@s****v 33
Ivanov h****v@n****v 31
Adam Keester 7****e 10
Chris h****v@n****v 9
Ryan Coe r****e@s****v 8
James McVey 5****3 8
Michelen c****l@s****v 5
Matthew Boyd m****d@g****m 3
Emily Browning 6****a 3
b0ndman i****d@g****m 3
Andrew Simms s****w@g****m 2
Mark Bruggemann m****k@e****o 2
calumkenny c****y@g****m 2
aidanbharath 4****h 2
Cesar 5****r 1
Maxwell Levin 2****n 1
Sean Pluemer 5****r 1
Dylan Mayes 6****7 1

Committer domains:


Issue and Pull Request metadata

Last synced: 1 day ago

Total issues: 139
Total pull requests: 252
Average time to close issues: 7 months
Average time to close pull requests: about 1 month
Total issue authors: 41
Total pull request authors: 23
Average comments per issue: 3.33
Average comments per pull request: 3.45
Merged pull request: 210
Bot issues: 0
Bot pull requests: 0

Past year issues: 27
Past year pull requests: 57
Past year average time to close issues: about 2 months
Past year average time to close pull requests: 21 days
Past year issue authors: 13
Past year pull request authors: 5
Past year average comments per issue: 2.93
Past year average comments per pull request: 2.82
Past year merged pull request: 47
Past year bot issues: 0
Past year bot pull requests: 0

More stats: https://issues.ecosyste.ms/repositories/lookup?url=https://github.com/MHKiT-Software/MHKiT-Python

Top Issue Authors

  • ssolson (34)
  • browniea (16)
  • rpauly18 (13)
  • cmichelenstrofer (8)
  • akeeste (4)
  • Rjan821163 (4)
  • ryancoe (4)
  • Matthew-Boyd (4)
  • hivanov-nrel (4)
  • willcoxe (3)
  • mbruggs (3)
  • jtgrasb (3)
  • nikg321 (3)
  • simmsa (3)
  • b0ndman (2)

Top Pull Request Authors

  • ssolson (104)
  • rpauly18 (29)
  • jmcvey3 (28)
  • akeeste (22)
  • browniea (13)
  • kaklise (11)
  • kmruehl (6)
  • ryancoe (6)
  • cmichelenstrofer (6)
  • mbruggs (5)
  • hivanov-nrel (5)
  • simmsa (4)
  • SeanPluemer (3)
  • castillocesar (1)
  • Alex-McVey (1)

Top Issue Labels

  • enhancement (25)
  • bug (18)
  • Clean Up (12)
  • wave module (8)
  • dolfyn module (8)
  • question (4)
  • documentation (2)
  • conda (2)
  • proposal (1)
  • river module (1)
  • good first issue (1)
  • deprecation (1)
  • release (1)

Top Pull Request Labels

  • enhancement (45)
  • Clean Up (31)
  • wave module (15)
  • bug (9)
  • dolfyn module (7)
  • tidal module (6)
  • river module (6)
  • loads module (6)
  • documentation (6)
  • deprecation (5)
  • utils module (2)
  • acoustics (2)
  • power module (1)
  • release (1)
  • actions (1)

Package metadata

proxy.golang.org: github.com/mhkit-software/mhkit-python

proxy.golang.org: github.com/MHKiT-Software/MHKiT-Python

pypi.org: mhkit

Marine and Hydrokinetic Toolkit

  • Homepage: https://github.com/MHKiT-Software/mhkit-python
  • Documentation: https://mhkit.readthedocs.io/
  • Licenses: Revised BSD
  • Latest release: 0.9.0 (published 5 months ago)
  • Last Synced: 2025-04-25T13:36:05.680Z (1 day ago)
  • Versions: 13
  • Dependent Packages: 0
  • Dependent Repositories: 1
  • Downloads: 689 Last month
  • Rankings:
    • Forks count: 6.289%
    • Dependent packages count: 7.31%
    • Stargazers count: 10.451%
    • Average: 12.915%
    • Downloads: 18.439%
    • Dependent repos count: 22.088%
  • Maintainers (4)

Score: 13.714128783275319