Loop Project File Documentation {#mainpage}
What is Loop?
The Loop platform is an open source 3D probabilistic geological and geophysical modelling platform, initiated by Geoscience Australia and the OneGeology consortium. The project is funded by Australian territory, State and Federal Geological Surveys, the Australian Research Council and the MinEx Collaborative Research Centre.
What is a Loop Project File?
A Loop Project File encapsulates all the data and models used or created in a Loop workflow. This includes the ability to create meta-data which provides provenance of the data and the methodology and history of how models are used and produced. The Loop Project File is based on netCDF and has APIs for C/C++ and Python (with the intention of creating a Fortran API in the future).
Why use a project file?
There are several benefits to using a single project file. These include encapsulating the information in a single place, server storage and retrieval enabling batching of model creation over multiple servers, easily shared workflows, and storage efficiency among many more.
Why use netCDF?
netCDF enables multi-dimensional data structure storage in a highly compressed format as well as data attribution for meta-data all within a single data file.
Licencing
The Loop Project File python repository is under the MIT license
2 maintainers
Metadata
2 maintainers
Release files for LoopProjectFile 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| loopprojectfile-0.2.2.tar.gz | 29.5 kB | Details |
Release files / loopprojectfile-0.2.2.tar.gz
| Download URL | loopprojectfile-0.2.2.tar.gz |
|---|---|
| Size | 29.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5589228c7cecb0a39a9c8ec87dab803ba24aa8e001e85b04fd09cb916980ae5
|
|
BLAKE2b-256 checksum How to use checksums |
386cd2ffa1ddf84a09d5314a0e0249eb7b8f5752df909428117a6dc56ddfb920
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Dec 16, 2024.
Transparency log
