Skip to main content

Kronos

kronos is a software tool for automating reproducible, auditable and distributable bioinformatics workflow development. It obviates explicit coding for workflow development to a great extent by compiling a text configuration file into an executable Python scripts.

Dependencies

Optional Python Libraries

For running on a cluster using drmaa, i.e. using -b drmaa, you will need to install:

Documentation

Please refer to kronos online documentation.

Contact

email: Jafar Taghiyar <jafar.taghiyar@gmail.com>

Please report issues in our kronos google group.

Change log

2.3.0:

  • added a mechanism to update the requirements of the implicit merge via GENERAL section. Note: you can switch off the implicit merge and use an explicit merge if you want to specify a particular requirement for only that merge task.

  • previously, multiple identical implicit merge tasks could exist in a workflow. In the new version, they are combined into a single merge task that happens only once.

  • added a switch called merge that defaults to True in the run subsection of each task. If it is set to False, the implicit merging mechanism is switched off for that task and the following warning message is shown when initializing the workflow:

    UserWarning: Implicit merge is off for task <the_task_name>.
    You may have to use an explicit merge task.
  • added support for tags in the interval file, i.e. an optional tag can be added for each chunk in each line of the interval file that will be used as the suffix for the name of the task corresponding to that chunk. The tags should be added to each line using tab as the separation character, e.g.:

    chunk1     tag1
    chunk2     tag2
    chunk3
    chunk4     tag4
  • bug fixes.

2.2.0:

  • each task in the configuration file now has its own requirements entry in the run subsection which takes precedence over the requirements listed in the GENERAL section. This enables users to have different versions of the same requirements for different tasks.

  • interval file now takes precedence over the synchronization, i.e. if a task has an interval file, then it will not be synchronized with its predecessors.

  • added support for floating point memory requests.

  • made all the merged files to store in a directory called merge.

  • username and version are automatically added to the config files when using make_config command.

  • added a check to make sure that the input of the implicit merge node is always a list.

  • bug fixes.

2.1.0:

  • Kronos now uses multithreading instead of multiprocessing.

2.0.4:

  • removed the limitation on the number of simultaneous jobs/pipelines.

  • added --no_prefix back to the input options of run command.

  • minor bug fixes.

2.0.3:

First version released!

Metadata

Release files for kronos-pipeliner 2.3.0

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

Source distribution (sdist)

Source distribution for kronos-pipeliner 2.3.0
File Size Uploaded Provenance Actions
kronos_pipeliner-2.3.0.tar.gz 33.6 kB Without provenance Details for kronos_pipeliner-2.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for kronos-pipeliner 2.3.0
File Interpreter ABI Platform Actions
kronos_pipeliner-2.3.0-py2-none-any.whl Python 2 none any Details for kronos_pipeliner-2.3.0-py2-none-any.whl

Total release size: 75.5 kB

Release files / kronos_pipeliner-2.3.0.tar.gz

Download URL kronos_pipeliner-2.3.0.tar.gz
Size 33.6 kB
Tags Source
SHA-256 checksum
How to use checksums
97219acb9550b3323672cc16d518562a2b1a7a56046d8bacd601175c828bd9f8
BLAKE2b-256 checksum
How to use checksums
831cfd08fdeca2b3467e892b5f7cd7ec1b2386e3f63e709dd13f3597b06f87b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / kronos_pipeliner-2.3.0-py2-none-any.whl

Download URL kronos_pipeliner-2.3.0-py2-none-any.whl
Size 41.9 kB
Tags Python 2
SHA-256 checksum
How to use checksums
572303517d2f67d51032b71f4430b4cba805ab02df9a3d2ee82131858429ad28
BLAKE2b-256 checksum
How to use checksums
c889413cebcc9648cca53b079eb1b33527056f0fc8364b05990eb4dd10c64812
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for kronos-pipeliner 2.3.0

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.

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