Integrity
Fitness for service assessment is the analysis both the present integrity of the component given the current state of damage and the projected remaining life
Summary
#TODO
- Refactor input file as follows
- Divide app configuration data from input file to avoid confusion
- Extract pipe capacity evaluation as a separate library (i.e. github and pypi)
- Currently .xlsx is supported for wall thickness grid data. Change to simple .csv
- Results are dumped into single folder
- Divide them into high-level and detailed results into respective folders
- The detailed technical steps implemented pyintegrity are to be documented.
Usage
See examples files to set up the General Metal Loss (GML) and Local Metal Loss (LML) analysis:
- GML and LML, ASME B31.8 design code, see 12in_oil_cml28
- GML and LML, API 1111 design code, see 16in_gas
The high level methodologies for the general metal loss (GML) and local metal loss (LML) assessments are shown below:
The detailed steps implemented in pyintegrity are per API 579, 2016 code.
Assumptions
Scope
Per the API 579 damage classes, the following schematics shows the pyintegrity current scope:
Key References
Key references used for the package development are:
| Name | Description | Hyperlink |
|---|---|---|
| API 579 | Fitness for Service, 2021 | API 579 2021 |
| BS 7910 | Fitness for Service | BS 7910 |
| BS 7910 | Fitness for Service | BS 7910:2013 Overview |
Existing Software
| Name | Description | Hyperlink |
|---|---|---|
| Autodesk Codeware INSPECT | Fitness for service | FFS |
| Autodesk Codeware INSPECT GML & LML | General and Local Metal Loss | General and Local Metal Loss |
| QuestIntegrity SignalFFS | Signal Fitness-For-Service (FFS) performs fitness-for-purpose and fracture mechanics analysis on fixed and rotating equipment. | SignalFFS |
| BMT FlawCheck | Structural Integrity Assessment Tool | Flawcheck |
1 maintainer
Metadata
1 maintainer
Release files for pyintegrity 0.0.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 |
|---|---|---|---|---|
| pyintegrity-0.0.1.tar.gz | 45.6 kB | Without provenance | Details for pyintegrity-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyintegrity-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for pyintegrity-0.0.1-py3-none-any.whl |
Total release size: 100.7 kB
Release files / pyintegrity-0.0.1.tar.gz
| Download URL | pyintegrity-0.0.1.tar.gz |
|---|---|
| Size | 45.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30c5f938ec6a9af3df3f0ec9547435fc7000f4978281c7709266b5b6e38609b0
|
|
BLAKE2b-256 checksum How to use checksums |
b58fb2e48b06017c2beddd71897d55ee3885c492cc367be0d6092a66c8298424
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / pyintegrity-0.0.1-py3-none-any.whl
| Download URL | pyintegrity-0.0.1-py3-none-any.whl |
|---|---|
| Size | 55.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7be56dfe8be545b38c3369b69d534b0f138db31fd168d513e5d8ce170728cfbf
|
|
BLAKE2b-256 checksum How to use checksums |
118c5ca9c649bc4b915967ca0a32a6dcc45de26ce724ca150034cb98a6318924
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for pyintegrity 0.0.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.
