Skip to main content

driven-pile

Long-term capacity of driven piles from the pile-driving log.

driven-pile implements a method in which each logged foot of driving characterizes the friction angle of the soil at the pile toe. The pore pressure generated by hammer blows reduces the soil's resistance during driving. The end-of-drive capacity represents the resistance of the soil with elevated pore-water pressure. The long-term capacity represents the resistance of the soil after all excess pore-water pressure has dissipated. Uncertainty in the driving-formula capacity, the data smoothing, the friction angle estimate, the cyclic resistance ratio, and the soil above the logged elevations is propagated with an optional Monte Carlo simulation.

Documentation: https://lornearnold.github.io/driven-pile/

Install

pip install driven-pile          # numpy and scipy only
pip install "driven-pile[plot]"  # adds matplotlib for the plot helpers

Use

import driven_pile as dp

pile = dp.Pile.octagonal(width_in=24, length_ft=150)
hammer = dp.Hammer(ram_weight=20.0)  # kips
log = dp.DriveLog.from_csv(
    "pile_B-25.5.csv",
    pile,
    hammer,
    depth="depth_ft",
    bpm="bpm",
    bpf="bpf",
    tip_elevation=-141.0,
    pile_id="B-25.5",
)
soil = dp.SoilProfile(
    mudline=-30.0,  # ft
    elevation=[-30, -80, -150],
    fines=[10, 35, 15],
)  # ft, percent

result = dp.analyze(log, soil)
print(result.drive.ltc, result.drive.ltc_shaft, result.drive.toe_eod)

result = dp.analyze(log, soil, run_mc=True)
print(result.mc.quantiles([0.05, 0.5, 0.95]))

The deterministic result uses the lowest admissible friction angle for the unlogged top segment; result.top_band holds the whole admissible band. Fines content is given as a table of elevation versus percent fines, or a single value for a uniform profile.

Units are US customary throughout (feet, kips, kips per square foot), matching the construction records the method was developed on.

License

GPL-3.0-or-later.

Metadata

Release files for driven-pile 0.1.2

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

Source distribution (sdist)

Source distribution for driven-pile 0.1.2
File Size Uploaded Provenance
driven_pile-0.1.2.tar.gz 295.2 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for driven-pile 0.1.2
File Interpreter ABI Platform
driven_pile-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 337.3 kB

Release files / driven_pile-0.1.2.tar.gz

Download URL driven_pile-0.1.2.tar.gz
Size 295.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e90dcc954fd7bcfed12fdca7d165ee0c2bb7697104b70eb078cee636cf57c0ec
BLAKE2b-256 checksum
How to use checksums
749dad5025cad66803841f79dcb71c3c6421562033dd544c8098461544e76004
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Release files / driven_pile-0.1.2-py3-none-any.whl

Download URL driven_pile-0.1.2-py3-none-any.whl
Size 42.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
85db9a24edde96e5c657cda23e095d9fde8285c6e1705928c6219c7def1587c2
BLAKE2b-256 checksum
How to use checksums
d1cdf4bee09483d829535b3542a597e36a4d9bdaae9ce51c419f3e1873d88936
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Security for driven-pile 0.1.2

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for driven_pile-0.1.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

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.

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