Pyminc

Latest version: v0.57

Safety actively analyzes 706259 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.48

===================
* changes to the calls to miset_attribute and miset_attr_values in order to properly set the image:complete flag
* some fixes to the tests in order to avoid warning messages

0.47

===================
* the dtype for a volume created by volumeFromData is based on the data block provided, but can be overwritten using the dtype argument
* fixed the history entry: ends with a newline, which means that subsequent entries in the history are properly separated
* label files are not read in as double by default anymore, but as one of the unsigned integer types.

0.46

===================
* when using volumeFromDescription and volumeFromData, these numpy types are now properly supported:
numpy.int8, numpy.int16, numpy.int32, numpy.float32, numpy.float64, numpy.uint8, numpy.uint16, numpy.uint32
numpy.dtype("int8"), numpy.dtype("int16"), numpy.dtype("int32"), numpy.dtype("float32"), numpy.dtype("float64"),
numpy.dtype("uint8"), numpy.dtype("uint16"), numpy.dtype("uint32")
* changed the "from numpy import *" to "import numpy as numpy" to avoid possible name space clashes

0.45

===================
* when MINC volumes are read, their volume type on disk is determined (byte, unsigned short, float etc.) and preserved. The data type of the MINC representation in Python (numpy) is double by default to maintain presicion. You do have full control over what you want the volume type on disk to be for your MINC volumes in Python.
* code is now Python3 compatible
* you can now specify direction cosines when creating volumes using volumeFromDescription and volumeFromData
* default volume type for volumeLikeFile changed from ubyte to None; will be determined by the like file.
* default volume type for volumeFromDescription changed from ubyte to ushort.
* default volume type for volumeFromData changed from ubyte to ushort.
* the image:complete attribute is set upon successfully writing out the data (used by minccomplete)
* files that are not properly/fully written to disk are deleted when closeVolume() or the destructor is called (so no broken files are left behind)
* fixed getVolumeRange(), now returns the correct data limits
* added more tests (python setup.py test)

0.4

==================
* fixed bug, such that float and double MINC files can be written to disk

Page 3 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.