forked from BIC-MNI/libminc
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
86 lines (64 loc) · 3.08 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
MINC - Medical Image NetCDF or MINC isn't netCDF
INTRODUCTION
------------
The MINC file format is a highly flexible medical image file format
built on the HDF5 generalized data format. The format is
simple, self-describing, extensible, portable and N-dimensional, with
programming interfaces for both low-level data access and high-level
volume manipulation. On top of the libraries is a suite of generic
image-file manipulation tools. The format, libraries and tools are
designed for use in a medical-imaging research environment : they are
simple and powerful and make no attempt to provide a pretty interface
to users.
Minc tools are hosted in https://github.com/BIC-MNI/minc-tools
Additional tools are available from the Montreal Neurological
Institute (MNI).
http://packages.bic.mni.mcgill.ca/tgz
SUPPORT FOR HDF5 "MINC 2.0" FORMAT FILES
----------------------------------------
This change requires that HDF5 must be installed before MINC can be
built. You can obtain HDF5 from, current version is 1.8.11:
http://www.hdfgroup.org/
You should NOT need to become an HDF5 expert to use MINC 2.0.
However, two tools included with HDF5 may prove useful, "h5dump" and
"h5ls". h5dump is roughly equivalent to netCDF's ncdump utility.
There is no exact netCDF tool analogous to h5ls. h5ls is useful for
exploring and extracting bits of the HDF5 hierarchy.
3. TENTATIVE ".mincrc" AND ENVIRONMENT VARIABLE SUPPORT
This is implemented as a way to control certain behaviors of the library
which are not readily available through other means. These variables may
be defined either in your environment, or in the .mincrc file in your
home directory. The value in the environment should override the one in
.mincrc.
Here's what exists so far:
# Force output files to MINC 2.0 format, regardless of the "-2" option.
#
MINC_FORCE_V2 = {1, 0}
# Desired ZLIB compression level. Zero implies no compression, a value
# of 4 gives a good tradeoff of compression and performance.
#
MINC_COMPRESS = {0..9}
# Desired HDF5 chunking dimension. This controls the size of the
# "hypercube" used by HDF5 to store the file. If set to zero, the
# file will not be stored in a chunked format, unless compression is
# enabled. The chunk size will automatically be reduced if it exceeds
# any actual dimension of the volume. If chunking is enabled
# automatically because of compression, the default chunk dimension is
# 32.
#
MINC_CHUNKING = {0..N}
# Log file - path to the desirned output file for messages. The default
# is the standard error (stderr) stream. To redirect to standard output,
# set this variable to "stdout" or "-". Otherwise the variable is taken
# to be the path to the desired log file. If the path name begins with
# a '+' character, the log file should be appended rather than recreated.
#
MINC_LOGFILE = [+]<pathname>|stdout|-
# Logging level. Not really useful yet, but intended to allow setting
# of 'verbosity' of messages. A value of zero would inhibit all but
# fatal messages, a value of 4 would allow debugging messages.
#
MINC_LOGLEVEL = 0-4
DOCUMENTATION
-------------
http://en.wikibooks.org/wiki/MINC