Stitcher package is a 3D mesh builder
It was developed by metaBIO lab member Heitor Gessner as part of his master thesis. The main usage is for recreating brain models from rare species, i.e., especies with low number of spiciements.
- It provides 3 classes:
Points()
Perimeters()
Surface()
Each Periemeter is a collection of Points. Each Surface is a collection of Perimeters. For the points in points, it is expected to have a 3D coordinate reference for each point that delimits a plane contour. The contours are made by manual or automatic segmentation, in the case of brains. This can be done in softwares such as ImageJ, Horos or Osirix - and than exported as a json file.
- Version 1.1:
-New super resolution method using Fourier Transform -Fixed fix_intersection() method from Perimeter() to properly handle rare parallel lines case
- Version 1.2:
-FIX: Point division by number added as operation (division) -NEW: Perimeter legth added -NEW: estimation of volume and lateral area by numerical approximation prior to the reconstruction (doi: 10.3389/fnana.2013.00028) -NEW: report of possible topological artifacts after build the 3D mesh
- Version 1.2.1:
-CHANGE: fixing the intersection is optinal when making a new Perimeter
- Version 1.2.2:
-Fix: loading from cache now works as expected -NEW: Perimeter.remove_by_angle(limit_in_radians) method to remove vertices that with angle<limit
- Version 1.2.2.1:
-Fix: Intersection check limit (reconstruction.Surface.intersection_limit) is now a property of Surface intead of being hard coded
- Version 1.2.3:
-NEW: Added Surface.self_intersection boolean property to report problematic surface build
- Version 1.3:
-Fix: remove_overlap was improved and now can handle multiple overlaps on the same spot
- Version 1.3.1:
-Fix: islands_ensemble now doesn’t create self intersection anymore
- Version 1.3.2:
-Fix: fix_intersection in Perimiter class didn’t update de area vector, now it does
Metadata
Release files for brain-stitcher 1.3.2
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 | |
|---|---|---|---|---|
| brain-stitcher-1.3.2.tar.gz | 1.2 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brain_stitcher-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / brain-stitcher-1.3.2.tar.gz
| Download URL | brain-stitcher-1.3.2.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b57fbb13dc51ddc6a28d1c76e7cf823b3ebb61d3c2160047538217fc8ecef15b
|
|
BLAKE2b-256 checksum How to use checksums |
4b35309d30775d6e19c61d50b1ee27095de794b0d42f7aea1cebaebee017deaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / brain_stitcher-1.3.2-py3-none-any.whl
| Download URL | brain_stitcher-1.3.2-py3-none-any.whl |
|---|---|
| Size | 39.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6bba338c36d5b62ba969e78d19f652d826aeb0a1a6abc7ed3b8d01f2fd85803
|
|
BLAKE2b-256 checksum How to use checksums |
5fa676b0fd301e23f5065adcb05548ac04a170860f2549fc879547e786882663
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for brain-stitcher 1.3.2
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.