What is loom?
Loom is a platform-independent tool to create, execute, track, and share workflows.
Why use Loom?
Ease of use
Loom runs out-of-the-box locally or in the cloud.
Repeatable analysis
Loom makes sure you can repeat your analysis months and years down the road after you’ve lost your notebook, your data analyst has found a new job, and your server has had a major OS version upgrade.
Loom uses Docker to reproduce your runtime environment, records file hashes to verify analysis inputs, and keeps fully reproducible records of your work.
Traceable results
Loom remembers anything you ever run and can tell you exactly how each result was produced.
Portability between platforms
Exactly the same workflow can be run on your laptop or on a public cloud service.
Open architecture
Not only is Loom open source and free to use, it uses an inside-out architecture that minimizes lock-in and lets you easily share your work with other people.
Write your results to a traditional filesystem or object store and browse them outside of Loom
Publish your tools as Docker images
Publish your workflows as simple, human-readable documents
Collaborate by sharing your workflows and results between Loom servers
Connect Loom to multiple file stores without creating redundant copies
Efficient re-use of results for redundant analysis steps
How many times do you really need to run the same analysis on the same inputs? Loom knows which steps in your workflow have already been run and seamlessly integrates previous results with the current run, while still maintaining data provenance and traceability.
Graphical user interface
While you may want to automate your analysis from the command line, a graphical user interface is useful for interactively browsing workflows and results.
Security and compliance
Loom is designed with clinical compliance in mind.
Who needs Loom?
Loom is built for the kind of workflows that bioinformaticians run – multi-step analyses with large data files passed between steps. But nothing about Loom is specific to bioinformatics.
Loom is scalable and supports individual analysts or large institutions.
Get started
Check out our Getting Started Guide and give Loom a try.
What is the current status?
Loom is under active development. To get involved, contact info@loomengine.org
Contributors
Nathan Hammond
Isaac Liao
Metadata
Release files for loomengine-utils 0.7.3
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 |
|---|---|---|---|---|
| loomengine_utils-0.7.3.tar.gz | 41.5 kB | Without provenance | Details for loomengine_utils-0.7.3.tar.gz |
Release files / loomengine_utils-0.7.3.tar.gz
| Download URL | loomengine_utils-0.7.3.tar.gz |
|---|---|
| Size | 41.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d00b2428e5364c77e65b200a24020d481f845c9cebf94b041b90f590b63a59f9
|
|
BLAKE2b-256 checksum How to use checksums |
68869f5d67bc2ad366a054e8e1c7f593c221a5fd67d9f3b8ee962acb82cfabf3
|
| 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.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.15rc1
|
Security for loomengine-utils 0.7.3
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.