MHKiT-Python

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

https://github.com/MHKiT-Software/MHKiT-Python

Science Score: 49.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 3 DOI reference(s) in README
  • Academic publication links
    Links to: zenodo.org
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (18.5%) to scientific vocabulary

Keywords

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

Keywords from Contributors

boundary-element-method hydrodynamics potential-flow water-wave wave-energy
Last synced: 5 months ago · JSON representation

Repository

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

Basic Info
Statistics
  • Stars: 54
  • Watchers: 8
  • Forks: 46
  • Open Issues: 5
  • Releases: 13
Topics
marine-renewable-energy mhkit mhkit-python python quality-control visualization
Created about 6 years ago · Last pushed 6 months ago
Metadata Files
Readme License

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.10, 3.11, 3.12) along with several Python package dependencies. MHKiT-Python can be installed using the Conda package manager:

bash conda install -c conda-forge mhkit

MHKiT can alternatively be installed from PyPi using pip:

bash 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:main 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

  • Name: MHKiT
  • Login: MHKiT-Software
  • Kind: organization

MHKiT is open-source software, developed in Python and MATLAB, for data processing, visualization, quality control, resource assessment, and device performance.

GitHub Events

Total
  • Create event: 3
  • Release event: 1
  • Issues event: 56
  • Watch event: 3
  • Delete event: 3
  • Issue comment event: 146
  • Push event: 32
  • Pull request event: 54
  • Pull request review comment event: 89
  • Pull request review event: 98
  • Fork event: 2
Last Year
  • Create event: 3
  • Release event: 1
  • Issues event: 56
  • Watch event: 3
  • Delete event: 3
  • Issue comment event: 146
  • Push event: 32
  • Pull request event: 54
  • Pull request review comment event: 89
  • Pull request review event: 98
  • Fork event: 2

Committers

Last synced: 10 months ago

All Time
  • Total Commits: 550
  • Total Committers: 21
  • Avg Commits per committer: 26.19
  • Development Distribution Score (DDS): 0.622
Past Year
  • Commits: 27
  • Committers: 4
  • Avg Commits per committer: 6.75
  • Development Distribution Score (DDS): 0.519
Top Committers
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 (Top 20 + Academic)

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 144
  • Total pull requests: 328
  • Average time to close issues: 8 months
  • Average time to close pull requests: about 1 month
  • Total issue authors: 44
  • Total pull request authors: 24
  • Average comments per issue: 3.05
  • Average comments per pull request: 3.09
  • Merged pull requests: 264
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 25
  • Pull requests: 64
  • Average time to close issues: 29 days
  • Average time to close pull requests: 15 days
  • Issue authors: 16
  • Pull request authors: 6
  • Average comments per issue: 1.6
  • Average comments per pull request: 1.27
  • Merged pull requests: 50
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • ssolson (32)
  • browniea (16)
  • rpauly18 (13)
  • cmichelenstrofer (8)
  • akeeste (6)
  • hivanov-nrel (4)
  • Rjan821163 (4)
  • ryancoe (4)
  • Matthew-Boyd (4)
  • mbruggs (3)
  • stinawahlgren (3)
  • simmsa (3)
  • jtgrasb (3)
  • willcoxe (3)
  • jmcvey3 (2)
Pull Request Authors
  • ssolson (135)
  • jmcvey3 (52)
  • akeeste (33)
  • rpauly18 (29)
  • browniea (15)
  • kaklise (11)
  • simmsa (9)
  • cmichelenstrofer (6)
  • kmruehl (6)
  • ryancoe (6)
  • mbruggs (5)
  • hivanov-nrel (5)
  • SeanPluemer (3)
  • rgcoe (2)
  • kchong75 (2)
Top Labels
Issue Labels
enhancement (22) bug (18) Clean Up (12) wave module (8) dolfyn module (7) question (4) documentation (2) conda (2) proposal (1) river module (1) good first issue (1) deprecation (1) release (1)
Pull Request Labels
Clean Up (50) enhancement (47) wave module (15) bug (11) dolfyn module (10) deprecation (7) river module (7) loads module (7) documentation (7) tidal module (6) acoustics (4) utils module (3) release (2) actions (2) power module (1)

Packages

  • Total packages: 3
  • Total downloads:
    • pypi 809 last-month
  • Total dependent packages: 0
    (may contain duplicates)
  • Total dependent repositories: 1
    (may contain duplicates)
  • Total versions: 39
  • Total maintainers: 4
proxy.golang.org: github.com/mhkit-software/mhkit-python
  • Versions: 13
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Dependent packages count: 7.0%
Average: 8.2%
Dependent repos count: 9.3%
Last synced: 6 months ago
proxy.golang.org: github.com/MHKiT-Software/MHKiT-Python
  • Versions: 13
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Dependent packages count: 7.0%
Average: 8.2%
Dependent repos count: 9.3%
Last synced: 6 months ago
pypi.org: mhkit

Marine and Hydrokinetic Toolkit

  • Versions: 13
  • Dependent Packages: 0
  • Dependent Repositories: 1
  • Downloads: 809 Last month
Rankings
Forks count: 6.3%
Dependent packages count: 7.3%
Stargazers count: 10.5%
Average: 12.9%
Downloads: 18.4%
Dependent repos count: 22.1%
Maintainers (4)
Last synced: 6 months ago