bwtrack
This repo hosts the code for tracking black and white particles in the mini interfacial rheometer developed by my friend Qiaoge.
乔哥牛逼!
I've got very timely and insightful feedbacks from Qiaoge, and I'm optimistic that the method here will become useful for other purposes eventually. So I create this repo to record the progress of the core functions.
I've always been fascinated about how a software package is made available to users from general public. I have downloaded many Python packages from PyPI. It is part of my habit to check out if there are existing projects that aim to solve my problem, and I'm more than happy to go through the documentations and see if there is a chance to participate in the project.
I've also been interested in publishing the code I write for other people to use. This is the key motivation for me to write code in a maintainable way, with clear comments and documentations. I tried to convince other people to try my code, but every time I have a feeling that I'm confusing other people with some functions in my local library, which do not exist on their computer. The problem is, I import my own functions as if they are from available packages, but they are not. For example, I often write in my code
from myImageLib import readdata
and this almost always cause problem to other people. Because they will get an error "myImageLib not found". Users with some Python experience will try
pip install myImageLib
only to find there is no package called this. Then they come ask me, and I explain them: you need to go to my GitHub and download this piece of code to your computer, and set this directory as your Python path. Not many steps, but can be confusing at each step, and ... not easy.
Imagine, if I can make myImageLib a PyPI package, and state it as a requirement of other code I give to users, things can be much more straightforward!
So this code, along with myImageLib, will be the first package I'm going to publish. The goal is to make it downloadable through pip, and work properly right after downloading.
Metadata
Release files for bwtrack 1.4
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 |
|---|---|---|---|---|
| bwtrack-1.4.tar.gz | 34.1 MB | Without provenance | Details for bwtrack-1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bwtrack-1.4-py3-none-any.whl | Python 3 | none | any | Details for bwtrack-1.4-py3-none-any.whl |
Total release size: 34.2 MB
Release files / bwtrack-1.4.tar.gz
| Download URL | bwtrack-1.4.tar.gz |
|---|---|
| Size | 34.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bdef431bb3165bd3b24d4e135e18001dbbd3c0348c30ba2f69fb3940eda4dd78
|
|
BLAKE2b-256 checksum How to use checksums |
145910790b980f931061a9739d457d7637e37c90c305c77e431ee255c8c7c916
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Release files / bwtrack-1.4-py3-none-any.whl
| Download URL | bwtrack-1.4-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1786ea32826076d7713bebfba61c7ded4920179563a5fccf33c517fd53e7a65
|
|
BLAKE2b-256 checksum How to use checksums |
bb506e400191ac221f87e826ba82e417ff67ef02bc85c7a8c77908c3ef9b03dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Security for bwtrack 1.4
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.