-
Notifications
You must be signed in to change notification settings - Fork 27
/
README
73 lines (46 loc) · 2.44 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
LDM README FILE
INTRODUCTION:
This package contains the source-code for the Unidata Program Center's Local
Data Manager (LDM).
RELEASE IDENTIFICATION:
The release identifier for this package is in the file VERSION and has the
following form:
<major>.<minor>.<rev>
where:
<major> Is the major release-number (e.g., 6). Changes to this
component indicate a major departure from previous releases
(such as a change to the LDM protocol). Such changes are
often not compatible with previous releases.
<minor> Is the minor release-number (e.g., 1). Changes to this
component indicate the addition of new features. The
package remains compatible with previous releases having the
same major release-number.
<rev> Is the revision-level (e.g., 0). Changes to this component
indicate bug-fixes and/or performance improvments that are
functionally compatible with previous releases having the
same major and minor release-numbers.
LEGAL:
Licensing and copyright information are contained in the file COPYRIGHT,
which is in the top-level source directory.
INFORMATION:
HOMEPAGE -- INCLUDING INSTALLATION & CONFIGURATION INSTRUCTIONS:
The homepage of the LDM package is
http://www.unidata.ucar.edu/software/ldm/
Click on the appropriate release identifier to go the release-specific
homepage, where you will find detailed LDM installation and
configuration instructions as well as other useful information.
CHANGE LOG:
Changes to the package are documented in the file CHANGE_LOG, which is
in the top-level source-directory.
LDM DECODERS:
LDM-compatible decoders for local processing of received data products are
available for the McIDAS package. See
http://www.unidata.ucar.edu/software/mcidas/mcidd/
SUPPORT:
You may request support by sending an email inquiry to
Please include a description of the type of platform (hardware and operating
system) and any relevant information that can help us answer your question
(error messages, symptoms, etc.).
RULES FOR CONTRIBUTING:
See the file CONTRIBUTING.md in the top-level source-directory.