Introduction
well_profile is a tool to generate or load well profiles in 3D. Features are added as they are needed; suggestions and contributions of all kinds are very welcome.
Documentation
See here for the complete well_profile package documentation.
Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
Get well_profile
- Users: Wheels for Python from PyPI
pip install well_profile
- Developers: Source code from Github
git clone https://github.com/pro-well-plan/well_profile
Quick examples
Color by specified parameter: e.g. 'dls'|'dl'|'tvd'|'md'|'inc'|'azi'
import well_profile as wp
well = wp.load('trajectory1.xlsx') # LOAD WELL
well.plot(style={'color': 'dls', 'size': 5}).show()
Also with dark mode:
well.plot(style={'darkMode': True, 'color': 'dls', 'size': 5}).show()
Plotting 3 wellbores:
Well 1 -> excel file: trajectory1.xlsxWell 2 -> generated wellWell 3 -> excel file: trajectory2.xlsx
import well_profile as wp
well_1 = wp.load('trajectory1.xlsx') # LOAD WELL 1
well_2 = wp.get(6000, profile='J', kop=2000, eob=3000, build_angle=85, set_start={'east':2000}) # GET WELL 2 --> North: 0 m, East: 2000 m
well_3 = wp.load('trajectory2.xlsx', set_start={'north':-3000}) # LOAD WELL 3 --> North: -3000 m, East: 0 m
well_1.plot(add_well=[well_2, well_3],
names=['first well name',
'second well name',
'third well name']).show() # Generate 3D plot for well 1 including wells 2 and 3
Contributing
Please read CONTRIBUTING for details on our code of conduct, and the process for submitting pull requests to us.
History
This tool was initially written and is maintained by Pro Well Plan AS as a free, simple, easy-to-use way to perform torque and drag calculations along the well that can be tailored to our needs, and as contribution to the free software community.
License
This project is licensed under the GNU Lesser General Public License v3.0 - see the LICENSE file for details
for further information contact juan@prowellplan.com
Metadata
Release files for well-profile 0.8.1
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 | Actions |
|---|---|---|---|---|
| well_profile-0.8.1.tar.gz | 17.8 kB | Without provenance | Details for well_profile-0.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| well_profile-0.8.1-py3-none-any.whl | Python 3 | none | any | Details for well_profile-0.8.1-py3-none-any.whl |
Total release size: 36.1 kB
Release files / well_profile-0.8.1.tar.gz
| Download URL | well_profile-0.8.1.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15cdce660dcce20afcd4c220a472d80ef44a4d1ec7b387e4d569848f8b61666d
|
|
BLAKE2b-256 checksum How to use checksums |
db1284d3d3769842e064603031d6382035363ae1efe6c11913d7cd2d25abb90c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / well_profile-0.8.1-py3-none-any.whl
| Download URL | well_profile-0.8.1-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5523d127c2a3ba34f31b6c9dfe0743b9cc6554cc35faead86a62c21109169529
|
|
BLAKE2b-256 checksum How to use checksums |
75dd6098de5ff9ede6b95bbd931a0c6b37c83a7a9bba69501ae1b486e64bcfd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for well-profile 0.8.1
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.