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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
|
%global _empty_manifest_terminate_build 0
Name: python-webviz-subsurface
Version: 0.2.19
Release: 1
Summary: Webviz config plugins for subsurface data
License: GNU General Public License v3 (GPLv3)
URL: https://github.com/equinor/webviz-subsurface
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3b/57/80975071a275f4bee153fe034a35627ed01cd2b92a0c8555944b8d5316f2/webviz-subsurface-0.2.19.tar.gz
BuildArch: noarch
Requires: python3-dash
Requires: python3-dash-bootstrap-components
Requires: python3-dash-daq
Requires: python3-defusedxml
Requires: python3-flask-caching
Requires: python3-fmu-ensemble
Requires: python3-fmu-tools
Requires: python3-geojson
Requires: python3-jsonschema
Requires: python3-pandas
Requires: python3-pillow
Requires: python3-pyarrow
Requires: python3-pyjwt
Requires: python3-pyscal
Requires: python3-scipy
Requires: python3-statsmodels
Requires: python3-xtgeo
Requires: python3-vtk
Requires: python3-webviz-config
Requires: python3-webviz-core-components
Requires: python3-webviz-subsurface-components
Requires: python3-ecl2df
Requires: python3-opm
Requires: python3-bandit
Requires: python3-black
Requires: python3-dash[testing]
Requires: python3-flaky
Requires: python3-isort
Requires: python3-mypy
Requires: python3-pylint
Requires: python3-pytest-mock
Requires: python3-pytest-xdist
Requires: python3-selenium
Requires: python3-types-pkg-resources
Requires: python3-types-pyyaml
%description
[](https://badge.fury.io/py/webviz-subsurface)
[](https://github.com/equinor/webviz-subsurface/actions?query=branch%3Amaster)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/alerts/)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/context:python)
[](https://www.python.org/)
## Webviz subsurface
> :sparkles::eyeglasses: **[Live demo application](https://webviz-subsurface-example.azurewebsites.net)**
### Introduction
This repository contains subsurface specific standard `webviz` containers, which are used as
plugins in [webviz-config](https://github.com/equinor/webviz-config).
### Installation
The easiest way of installing this package is to run
```bash
pip install webviz-subsurface
```
Add `--upgrade` if you have installed earlier, but want to upgrade to a newer version.
If you want to install the latest, unreleased, code you can instead run
```bash
pip install git+https://github.com/equinor/webviz-subsurface
```
### Usage and documentation
For general usage, see the documentation on
[webviz-config](https://github.com/equinor/webviz-config). End-user documentation for
the subsurface containers are automatically built and hosted on the
[github pages](https://equinor.github.io/webviz-subsurface/) for this repository.
There is also a [live demo application](https://webviz-subsurface-example.azurewebsites.net)
showing how a created application can look like, using the `master` branch of this repository.
### Example webviz configuration files
Example `webviz` configuration files, and corresponding test data, is available at
https://github.com/equinor/webviz-subsurface-testdata.
See that repository for instructions on how to download and run the examples.
### Creating new elements
If you are interested in creating new elements which can be configured through
the configuration file, take a look at the
[webviz-config contribution guide](https://github.com/equinor/webviz-config/blob/master/CONTRIBUTING.md).
You can do automatic linting of your code changes by running
```bash
black --check webviz_subsurface tests # Check code style
pylint webviz_subsurface tests # Check code quality
bandit -r -c ./bandit.yml webviz_subsurface tests # Check Python security best practice
```
### Review of contributions
When doing review of contributions, it is usually useful to also see the resulting application live, and
not only the code changes. In order to facilitate this, this repository is using GitHub actions.
When on a feature branch, and a commit message including the substring `[deploy test]` arrives, the GitHub
action workflow will try to build and deploy a test Docker image for you (which you then can link to a web app with
e.g. automatic reload on new images). All you need to do in your own fork is to add
GitHub secrets with the following names:
- `review_docker_registry_url`: The registry to push to (e.g. `myregistry.azurecr.io`)
- `review_docker_registry_username`: Registry login username.
- `review_docker_registry_token`: Registry login token (or password).
- `review_container_name`: What you want to call the container pushed to the registry.
You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`.
### Disclaimer
This is a tool under heavy development. The current configuration file layout,
also for subsurface containers, will therefore see large changes.
%package -n python3-webviz-subsurface
Summary: Webviz config plugins for subsurface data
Provides: python-webviz-subsurface
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-webviz-subsurface
[](https://badge.fury.io/py/webviz-subsurface)
[](https://github.com/equinor/webviz-subsurface/actions?query=branch%3Amaster)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/alerts/)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/context:python)
[](https://www.python.org/)
## Webviz subsurface
> :sparkles::eyeglasses: **[Live demo application](https://webviz-subsurface-example.azurewebsites.net)**
### Introduction
This repository contains subsurface specific standard `webviz` containers, which are used as
plugins in [webviz-config](https://github.com/equinor/webviz-config).
### Installation
The easiest way of installing this package is to run
```bash
pip install webviz-subsurface
```
Add `--upgrade` if you have installed earlier, but want to upgrade to a newer version.
If you want to install the latest, unreleased, code you can instead run
```bash
pip install git+https://github.com/equinor/webviz-subsurface
```
### Usage and documentation
For general usage, see the documentation on
[webviz-config](https://github.com/equinor/webviz-config). End-user documentation for
the subsurface containers are automatically built and hosted on the
[github pages](https://equinor.github.io/webviz-subsurface/) for this repository.
There is also a [live demo application](https://webviz-subsurface-example.azurewebsites.net)
showing how a created application can look like, using the `master` branch of this repository.
### Example webviz configuration files
Example `webviz` configuration files, and corresponding test data, is available at
https://github.com/equinor/webviz-subsurface-testdata.
See that repository for instructions on how to download and run the examples.
### Creating new elements
If you are interested in creating new elements which can be configured through
the configuration file, take a look at the
[webviz-config contribution guide](https://github.com/equinor/webviz-config/blob/master/CONTRIBUTING.md).
You can do automatic linting of your code changes by running
```bash
black --check webviz_subsurface tests # Check code style
pylint webviz_subsurface tests # Check code quality
bandit -r -c ./bandit.yml webviz_subsurface tests # Check Python security best practice
```
### Review of contributions
When doing review of contributions, it is usually useful to also see the resulting application live, and
not only the code changes. In order to facilitate this, this repository is using GitHub actions.
When on a feature branch, and a commit message including the substring `[deploy test]` arrives, the GitHub
action workflow will try to build and deploy a test Docker image for you (which you then can link to a web app with
e.g. automatic reload on new images). All you need to do in your own fork is to add
GitHub secrets with the following names:
- `review_docker_registry_url`: The registry to push to (e.g. `myregistry.azurecr.io`)
- `review_docker_registry_username`: Registry login username.
- `review_docker_registry_token`: Registry login token (or password).
- `review_container_name`: What you want to call the container pushed to the registry.
You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`.
### Disclaimer
This is a tool under heavy development. The current configuration file layout,
also for subsurface containers, will therefore see large changes.
%package help
Summary: Development documents and examples for webviz-subsurface
Provides: python3-webviz-subsurface-doc
%description help
[](https://badge.fury.io/py/webviz-subsurface)
[](https://github.com/equinor/webviz-subsurface/actions?query=branch%3Amaster)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/alerts/)
[](https://lgtm.com/projects/g/equinor/webviz-subsurface/context:python)
[](https://www.python.org/)
## Webviz subsurface
> :sparkles::eyeglasses: **[Live demo application](https://webviz-subsurface-example.azurewebsites.net)**
### Introduction
This repository contains subsurface specific standard `webviz` containers, which are used as
plugins in [webviz-config](https://github.com/equinor/webviz-config).
### Installation
The easiest way of installing this package is to run
```bash
pip install webviz-subsurface
```
Add `--upgrade` if you have installed earlier, but want to upgrade to a newer version.
If you want to install the latest, unreleased, code you can instead run
```bash
pip install git+https://github.com/equinor/webviz-subsurface
```
### Usage and documentation
For general usage, see the documentation on
[webviz-config](https://github.com/equinor/webviz-config). End-user documentation for
the subsurface containers are automatically built and hosted on the
[github pages](https://equinor.github.io/webviz-subsurface/) for this repository.
There is also a [live demo application](https://webviz-subsurface-example.azurewebsites.net)
showing how a created application can look like, using the `master` branch of this repository.
### Example webviz configuration files
Example `webviz` configuration files, and corresponding test data, is available at
https://github.com/equinor/webviz-subsurface-testdata.
See that repository for instructions on how to download and run the examples.
### Creating new elements
If you are interested in creating new elements which can be configured through
the configuration file, take a look at the
[webviz-config contribution guide](https://github.com/equinor/webviz-config/blob/master/CONTRIBUTING.md).
You can do automatic linting of your code changes by running
```bash
black --check webviz_subsurface tests # Check code style
pylint webviz_subsurface tests # Check code quality
bandit -r -c ./bandit.yml webviz_subsurface tests # Check Python security best practice
```
### Review of contributions
When doing review of contributions, it is usually useful to also see the resulting application live, and
not only the code changes. In order to facilitate this, this repository is using GitHub actions.
When on a feature branch, and a commit message including the substring `[deploy test]` arrives, the GitHub
action workflow will try to build and deploy a test Docker image for you (which you then can link to a web app with
e.g. automatic reload on new images). All you need to do in your own fork is to add
GitHub secrets with the following names:
- `review_docker_registry_url`: The registry to push to (e.g. `myregistry.azurecr.io`)
- `review_docker_registry_username`: Registry login username.
- `review_docker_registry_token`: Registry login token (or password).
- `review_container_name`: What you want to call the container pushed to the registry.
You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`.
### Disclaimer
This is a tool under heavy development. The current configuration file layout,
also for subsurface containers, will therefore see large changes.
%prep
%autosetup -n webviz-subsurface-0.2.19
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-webviz-subsurface -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.19-1
- Package Spec generated
|
