leeselab_project_creator
Python script to generate plate layout lists as well as worklist for laboratory projects in the Aquatic Ecosystem Research Group. Automatically suggests a pooling strategy as well as optimal primer order for library generation.
How to install and run
Installation via pip:
pip install leeselab-project-creator
How to update:
pip install --upgrade leeselab-project-creator
How to run:
leeselab-project-creator or python -m leeselab-project-creator
How to use
After starting the GUI will look like this:
The project creator needs an Excel list with sample names as input. You can set the Path to the sample list, the sheet in which it can be found as well as the cell of the first sample. Select between 1 and 500 extraction replicates. Select between 1 and 500 PCR replicates. Select what primers to use, seperated by comma (e.g. fwh2, rbcl, 16S). Select which 1st step primer tags are available for the primer sets, seperated by comma (e.g. 1,2,3,4,5,6,7,8). Enter a project name and select a folder where to save the plate layout. Hit "Generate sample list".
Example
As an example sample list a list with 12 samples was selected:
The example setup looks like this when it is completly filled:
The project creator will generate a plate layout according to the settings. This will include the technical replicates to control for cross-contamination as well as the selected amount of extraction replicates (indicated by _1, _2 ...)
Two more sheet will be generated, the extraction worklist and the PCR worklist:
In the PCR worklist a pooling strategy for the librarys will be calculated as well as an optimal use of primers to maximize library diversity.
The selected PCR replicates will be generated as seperate plates in the PCR worklist.
All sheets can be printed and taken into the lab to document all required data to sufficiently describe the analysis in the end.
Metadata
Release files for leeselab-project-creator 2.0.0
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 |
|---|---|---|---|---|
| leeselab_project_creator-2.0.0.tar.gz | 9.6 kB | Without provenance | Details for leeselab_project_creator-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| leeselab_project_creator-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for leeselab_project_creator-2.0.0-py3-none-any.whl |
Total release size: 20.0 kB
Release files / leeselab_project_creator-2.0.0.tar.gz
| Download URL | leeselab_project_creator-2.0.0.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1aca4da6966618a7a45d80f147395990eb95505912a39f8594be41c39d82f8a
|
|
BLAKE2b-256 checksum How to use checksums |
3bff0f5caf7d2eb481bb8eb6a38fc1417717aebe54d62ff2c31cd27e94838d99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / leeselab_project_creator-2.0.0-py3-none-any.whl
| Download URL | leeselab_project_creator-2.0.0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc86613a7f9d90fe12561b4cde43984b2f1ef6b58dc71002ceaf5a01ce984c63
|
|
BLAKE2b-256 checksum How to use checksums |
9339b19716e8bb724ba6b09f89959c90f7c20fb27f63565ada21f978d0d4b575
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for leeselab-project-creator 2.0.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.