Useful links: Documentation |
Source code |
Bug reports | |
|
|
What is DoubleBlind?
DoubleBlind is a software tool that automatically and reversibly replaces file names with random strings to help experimenters quantify microscopy experiments blindly and maintain experimental integrity.
DoubleBlind aims to solve a common problem in scientific image quantification - keeping oneself blind to the experimental conditions. When experimenters are able to see the experimental conditions of their data during quantification, it can bias their observations and interpretations of the results. DoubleBlind solves this problem by automatically replacing file names with random strings, which can then be unblinded later when the experiment is complete. This allows experimenters to analyze their experiments without being influenced by knowledge of the experimental conditions, while still being able to access their original files later.
DoubleBlind file name replacement process is completely reversible, so users can easily unblind their image files when the experiment is complete. You don’t need to keep any special mapping of the original filenames - a blinded file can be unblinded just based on its encoded name.
Files can be blinded and unblinded at any time, individually or in groups. This allows experimenters to maintain the blinding of their data until the end of the experiment, while still being able to access the original filenames when needed.
DoubleBlind supports most accepted file formats, as well as specialized microscopy image formats, such as Olympus .vsi files.
Once the experiment is complete, DoubleBlind makes it easy to unblind the files and to replace the coded filenames with the original filenames in data files such as Excel sheets and text files. This ensures that the final data analysis is accurate and reliable.
DoubleBlind is also designed to be easy to use, with a simple and intuitive interface that works on all operating systems. This ease of use is particularly important for experimenters who may not have extensive experience with software tools.
Metadata
Release files for doubleblind 1.1.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 |
|---|---|---|---|---|
| doubleblind-1.1.1.tar.gz | 368.4 kB | Without provenance | Details for doubleblind-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| doubleblind-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for doubleblind-1.1.1-py3-none-any.whl |
Total release size: 487.3 kB
Release files / doubleblind-1.1.1.tar.gz
| Download URL | doubleblind-1.1.1.tar.gz |
|---|---|
| Size | 368.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c69c14172a5019052da0bc382e46287ec7a5cd361f4cf747734a62925026b0a5
|
|
BLAKE2b-256 checksum How to use checksums |
be0de0ee3b69c6da600cafb1267496b5d5926aaf22f16c582c10980f7deec977
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / doubleblind-1.1.1-py3-none-any.whl
| Download URL | doubleblind-1.1.1-py3-none-any.whl |
|---|---|
| Size | 118.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e05d845b6720df887df533f3ece65e680cdb5286420fa8a5a8b88d21b7ebf8d9
|
|
BLAKE2b-256 checksum How to use checksums |
9a6a8a2effaa8dea856cf780803ddaa77c9e589be42ed50a35ee330225697cee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for doubleblind 1.1.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.