forked from equinor/segyio
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsetup.py
84 lines (71 loc) · 3.09 KB
/
setup.py
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
#!/usr/bin/env python
from distutils.core import setup, Extension
_segyio = Extension('segyio._segyio',
sources=['python/segyio/_segyio.c', 'lib/src/segy.c'],
include_dirs=['lib/src', 'lib/include'],
define_macros=[('HAVE_MMAP', 1), ('HAVE_NETINET_IN_H', 1)],
extra_compile_args=['-std=c99'])
long_description = """
=======
SEGY IO
=======
Introduction
------------
Segyio is a small LGPL licensed C library for easy interaction with SEG Y
formatted seismic data, with language bindings for Python and Matlab. Segyio is
an attempt to create an easy-to-use, embeddable, community-oriented library for
seismic applications. Features are added as they are needed; suggestions and
contributions of all kinds are very welcome.
Feature summary
---------------
* A low-level C interface with few assumptions; easy to bind to other
languages.
* Read and write binary and textual headers.
* Read and write traces, trace headers.
* Easy to use and native-feeling python interface with numpy integration.
Project goals
-------------
Segyio does necessarily attempt to be the end-all of SEG-Y interactions;
rather, we aim to lower the barrier to interacting with SEG-Y files for
embedding, new applications or free-standing programs.
Additionally, the aim is not to support the full standard or all exotic (but
correctly) formatted files out there. Some assumptions are made, such as:
* All traces in a file are assumed to be of the same sample size.
* It is assumed all lines have the same number of traces.
The writing functionality in Segyio is largely meant to *modify* or adapt
files. A file created from scratch is not necessarily a to-spec SEG-Y file, as
we only necessarily write the header fields segyio needs to make sense of the
geometry. It is still highly recommended that SEG-Y files are maintained and
written according to specification, but segyio does not mandate this.
"""
setup(name='SegyIO',
version='1.0.4',
description='IO library for SEG-Y files',
long_description=long_description,
author='Statoil ASA',
author_email='[email protected]',
url='https://github.com/Statoil/SegyIO',
packages=['segyio'],
package_dir={'': 'python'},
package_data={'': ['License.md']},
license='LGPL-3.0',
ext_modules=[_segyio],
platforms='any',
requires=['numpy'],
install_requires=['numpy'],
classifiers=[
'Development Status :: 5 - Production/Stable',
'Environment :: Other Environment',
'Intended Audience :: Developers',
'Intended Audience :: Science/Research',
'License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)',
'Natural Language :: English',
'Operating System :: OS Independent',
'Programming Language :: C',
'Programming Language :: Python :: 2.7',
'Topic :: Scientific/Engineering',
'Topic :: Scientific/Engineering :: Physics',
'Topic :: Software Development :: Libraries',
'Topic :: Utilities'
]
)