Skip to main content

LAMMPS step

https://img.shields.io/pypi/v/lammps_step.svg https://img.shields.io/travis/molssi-seamm/lammps_step.svg Documentation Status Updates https://codecov.io/gh/molssi-seamm/lammps_step/branch/master/graph/badge.svg

The LAMMPS step for a SEAMM flowchart

Contributing

This project uses the git branching model outlined by Vincent Driessen. Development is handled by branching feature branches from the ‘develop’ branch:

Feature branches

May branch off from:

develop

Must merge back into:

develop

Branch naming convention:

anything except master, develop, release-, or hotfix-

Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into develop (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment).

Feature branches typically exist in developer repos only, not in origin.

Creating a feature branch

When starting work on a new feature, branch off from the develop branch:

$ git checkout -b myfeature develop
Switched to a new branch "myfeature"

Incorporating a finished feature on develop

Finished features may be merged into the develop branch to definitely add them to the upcoming release:

$ git checkout develop
Switched to branch 'develop'
$ git merge --no-ff myfeature
Updating ea1b82a..05e9557
(Summary of changes)
$ git branch -d myfeature
Deleted branch myfeature (was 05e9557).
$ git push origin develop

The –no-ff flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature.

Features

  • TODO

Credits

This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.

History

0.1.0 (2017-12-20)

  • First release on PyPI.

Metadata

Release files for lammps-step 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lammps-step 0.5.0
File Size Uploaded Provenance Actions
lammps_step-0.5.0.tar.gz 53.2 kB Without provenance Details for lammps_step-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lammps-step 0.5.0
File Interpreter ABI Platform Actions
lammps_step-0.5.0-py2.py3-none-any.whl Python 2, Python 3 none any Details for lammps_step-0.5.0-py2.py3-none-any.whl

Total release size: 113.6 kB

Release files / lammps_step-0.5.0.tar.gz

Download URL lammps_step-0.5.0.tar.gz
Size 53.2 kB
Tags Source
SHA-256 checksum
How to use checksums
710edf6c8c823d2fd08decbace4794bcbe5e3527ca28976a5f955afcc2aee936
BLAKE2b-256 checksum
How to use checksums
1abd9cae48d10bff582d313df2a64a78730a9ea2fc6e898674a6a4e5a088ef8c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.6.7

Release files / lammps_step-0.5.0-py2.py3-none-any.whl

Download URL lammps_step-0.5.0-py2.py3-none-any.whl
Size 60.4 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
02f7f14342563456a1e03a3a49956b9710ffe6ad77e468c96e0320d225cc53d6
BLAKE2b-256 checksum
How to use checksums
3b8b3d2c46a67870d05eea171e2d28f1565aefa28824492fb8ec55c51fb63040
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.6.7

Security for lammps-step 0.5.0

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.

Release history Release notifications | RSS feed

This release

0.5.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page