Pulsarpy DX
A Pulsarpy client extension for Pulsar LIMS that imports sequencing results from DNAnexus
AP documentation is on Read the Docs.
This is a companion tool to Pulsarpy, which in turn is the offical Python client for Pulsar LIMS. Pulsarpy DX is a gateway between Pulsar LIMS and related sequencing results stored on DNAnexus, and serves to import the sequencing results metadata from the DNAnexus platform into Pulsar LIMS.
The main feature of this package is the script called import_seq_results.py, which looks for projects under the specified DNAnexus billing org that were created within the past N days. Each project is checked if it's sequencing results need to be imoprted into Pulsar LIMS. The way it works is quite specific to the laboratoy workflow of the Snyder Production Center of ENCODE, here at Stanford.
Lab workflow
A SequencingRequest record is made in Pulsar LIMS. Then, an Excel form is filled out and sent to the nearby Stanford Genome Sequencing Service Center (GSSC). That form contains the library name, which the lab personel set to be equal to the SequencingRequest record's name in Pulsar. This name in the Excel form will eventually make its way to a DNAnexus project as a property called library_name when GSSC uploads the sequencing results there.
When import_seq_results.py is run, for each project it finds it will look at the value of the library_name property, then use this to look up a SequencingRequest by that name in Pulsar. The SequencingRequest record must pre-exist in order for sequencing results to be imported - a process that will entail creating a SequeningRun record and one or more SequencingResult records, as needed. See the script documentation for more details.
Metadata
Release files for pulsarpy-dx 0.5.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 |
|---|---|---|---|---|
| pulsarpy-dx-0.5.1.tar.gz | 9.2 kB | Without provenance | Details for pulsarpy-dx-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulsarpy_dx-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for pulsarpy_dx-0.5.1-py3-none-any.whl |
Total release size: 23.7 kB
Release files / pulsarpy-dx-0.5.1.tar.gz
| Download URL | pulsarpy-dx-0.5.1.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80cd10f81449f5d0f27e9956e48ccc7ca8c23c0eae2261f6314017f54ad6d1c3
|
|
BLAKE2b-256 checksum How to use checksums |
739f105a4be1654acf4018eec1be91466fea43fc868c26b81698fcd18620d820
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.1
|
Release files / pulsarpy_dx-0.5.1-py3-none-any.whl
| Download URL | pulsarpy_dx-0.5.1-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b59196ba15b0f7bc2c3aa50b4c432bb1a943450776939c7e57f224f71b82c9cd
|
|
BLAKE2b-256 checksum How to use checksums |
ad4ff315c10ec90b23dc0b70415559fb92ad46d154bcc8bee28956824fa5856b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.1
|
Security for pulsarpy-dx 0.5.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.