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
345
346
347
348
349
|
%global _empty_manifest_terminate_build 0
Name: python-yt-idefix
Version: 2.2.0
Release: 1
Summary: An extension module for yt, adding a frontend for Idefix and Pluto
License: GPL-3.0
URL: https://yt-project.org/
Source0: https://mirrors.aliyun.com/pypi/web/packages/a4/4f/b35e0b74bf50240df0ab6e1af4d022485d8ed52512323f2a7a402549798f/yt_idefix-2.2.0.tar.gz
BuildArch: noarch
Requires: python3-inifix
Requires: python3-numpy
Requires: python3-yt
Requires: python3-h5py
%description
# yt_idefix
[](https://pypi.org/project/yt_idefix/)
[](https://pypi.org/project/yt_idefix/)
[![yt-project](https://img.shields.io/static/v1?label="works%20with"&message="yt"&color="blueviolet")](https://yt-project.org)
<!--- Tests and style --->
[](https://github.com/neutrinoceros/yt_idefix/actions/workflows/ci.yml)
[](https://results.pre-commit.ci/latest/github/neutrinoceros/yt_idefix/main)
[](https://github.com/psf/black)
[](https://github.com/charliermarsh/ruff)
A maturing yt frontend for Idefix and Pluto, packaged as an extension for yt.
## Installation
```shell
python -m pip install yt_idefix
```
## Supported formats
| Code | format | supported since | additional dependencies |
|--------|:------:|:---------------:|-------------------------|
| Idefix | `.dmp` | v0.1.0 | |
| Idefix | `.vtk` | v0.3.0 | |
| Pluto | `.vtk` | v0.9.0 | |
| Pluto | XDMF | v1.1.0 | `h5py` |
## Usage
Integration with yt is seamless. *Installing* this plugin is all that's required to make yt
compatible with data formats supported by `yt_idefix` !
### Additional arguments to `yt.load`
The metadata are parsed from data file, definitions header file and inifile when loading dataset.
Definitions header file (`definitions.h` for Pluto, or `definitions.hpp` for Idefix) and inifile (`pluto.ini` and `idefix.ini` respectively) are discovered automatically if they match default names, are located along with data files, and unique. Otherwise, they can be specified explicitly as paths (either relative to data files or absolute paths) with parameters `definitions_header` and `inifile` respectively.
Geometry is parsed automatically whenever possible, but as a last resort, it can also be specified as a keyword argument (possible values are "cartesian", "spherical", "cylindrical" and "polar").
```python
# Examples
ds = yt.load("data.0010.vtk", definitions_header="../definitions.h", inifile="example.ini")
ds = yt.load("data.0010.vtk", geometry='spherical")
```
The data are loaded as physical quantities with units. The default unit system is `cgs` in yt. This frontend can convert data from code units into `cgs` properly, based on the unit definitions from metadata.
Users are able to choose the unit displayed in two ways, through `unit_system` ("code", "mks" and "cgs") and `units_override`(only valid for Pluto).
```python
# Examples on units
ds = yt.load("data.0010.vtk", unit_system='mks")
units_override = dict(length_unit=(100.0, "au"), mass_unit=yt.units.mass_sun)
ds = yt.load("data.0010.vtk", unit_override=unit_override) # Caution that other units will also be changed for consistency!!
```
With Pluto data, the rest of the system will be derived consistently with given units, within the following rules:
1. Temperature unit cannot be overridden (always set to Kelvin)
2. No more than three units can be overridden at once (overconstrained systems are never validated for simplicity)
3. When given less than three overrides, base units in Pluto (ordered: velocity_unit, density_unit, length_unit) are assumed
4. The following combinations are not allowed
```python
{"magnetic_unit", "velocity_unit", "density_unit"},
{"velocity_unit", "time_unit", "length_unit"},
{"density_unit", "length_unit", "mass_unit"},
```
yt is able to provide some derived fields from existed fields, e.g., `"cell_volume"`. Fields related to element species can be created according to primordial abundances of H and He, through `default_species_fields` (`"neutral"` and `"ionized"`) parameters.
```python
# Example
ds = yt.load("data.0010.vtk", default_species_fields="ionized")
```
### Convention of field names
The outputs are loaded from disk with field names in uppercase. This normalization is only applied to the standard outputs but user-defined outputs and Pluto's ion fraction outputs.
```python
# Example
ds.field_list
# Output:
# [('pluto-vtk', 'PRS'), # standard output
# ('pluto-vtk', 'RHO'), # standard output
# ('pluto-vtk', 'VX1'), # standard output
# ('pluto-vtk', 'VX2'), # standard output
# ('pluto-vtk', 'VX3'), # standard output
# ('pluto-vtk', 'temp')] # This is a user-defined output
```
%package -n python3-yt-idefix
Summary: An extension module for yt, adding a frontend for Idefix and Pluto
Provides: python-yt-idefix
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-yt-idefix
# yt_idefix
[](https://pypi.org/project/yt_idefix/)
[](https://pypi.org/project/yt_idefix/)
[![yt-project](https://img.shields.io/static/v1?label="works%20with"&message="yt"&color="blueviolet")](https://yt-project.org)
<!--- Tests and style --->
[](https://github.com/neutrinoceros/yt_idefix/actions/workflows/ci.yml)
[](https://results.pre-commit.ci/latest/github/neutrinoceros/yt_idefix/main)
[](https://github.com/psf/black)
[](https://github.com/charliermarsh/ruff)
A maturing yt frontend for Idefix and Pluto, packaged as an extension for yt.
## Installation
```shell
python -m pip install yt_idefix
```
## Supported formats
| Code | format | supported since | additional dependencies |
|--------|:------:|:---------------:|-------------------------|
| Idefix | `.dmp` | v0.1.0 | |
| Idefix | `.vtk` | v0.3.0 | |
| Pluto | `.vtk` | v0.9.0 | |
| Pluto | XDMF | v1.1.0 | `h5py` |
## Usage
Integration with yt is seamless. *Installing* this plugin is all that's required to make yt
compatible with data formats supported by `yt_idefix` !
### Additional arguments to `yt.load`
The metadata are parsed from data file, definitions header file and inifile when loading dataset.
Definitions header file (`definitions.h` for Pluto, or `definitions.hpp` for Idefix) and inifile (`pluto.ini` and `idefix.ini` respectively) are discovered automatically if they match default names, are located along with data files, and unique. Otherwise, they can be specified explicitly as paths (either relative to data files or absolute paths) with parameters `definitions_header` and `inifile` respectively.
Geometry is parsed automatically whenever possible, but as a last resort, it can also be specified as a keyword argument (possible values are "cartesian", "spherical", "cylindrical" and "polar").
```python
# Examples
ds = yt.load("data.0010.vtk", definitions_header="../definitions.h", inifile="example.ini")
ds = yt.load("data.0010.vtk", geometry='spherical")
```
The data are loaded as physical quantities with units. The default unit system is `cgs` in yt. This frontend can convert data from code units into `cgs` properly, based on the unit definitions from metadata.
Users are able to choose the unit displayed in two ways, through `unit_system` ("code", "mks" and "cgs") and `units_override`(only valid for Pluto).
```python
# Examples on units
ds = yt.load("data.0010.vtk", unit_system='mks")
units_override = dict(length_unit=(100.0, "au"), mass_unit=yt.units.mass_sun)
ds = yt.load("data.0010.vtk", unit_override=unit_override) # Caution that other units will also be changed for consistency!!
```
With Pluto data, the rest of the system will be derived consistently with given units, within the following rules:
1. Temperature unit cannot be overridden (always set to Kelvin)
2. No more than three units can be overridden at once (overconstrained systems are never validated for simplicity)
3. When given less than three overrides, base units in Pluto (ordered: velocity_unit, density_unit, length_unit) are assumed
4. The following combinations are not allowed
```python
{"magnetic_unit", "velocity_unit", "density_unit"},
{"velocity_unit", "time_unit", "length_unit"},
{"density_unit", "length_unit", "mass_unit"},
```
yt is able to provide some derived fields from existed fields, e.g., `"cell_volume"`. Fields related to element species can be created according to primordial abundances of H and He, through `default_species_fields` (`"neutral"` and `"ionized"`) parameters.
```python
# Example
ds = yt.load("data.0010.vtk", default_species_fields="ionized")
```
### Convention of field names
The outputs are loaded from disk with field names in uppercase. This normalization is only applied to the standard outputs but user-defined outputs and Pluto's ion fraction outputs.
```python
# Example
ds.field_list
# Output:
# [('pluto-vtk', 'PRS'), # standard output
# ('pluto-vtk', 'RHO'), # standard output
# ('pluto-vtk', 'VX1'), # standard output
# ('pluto-vtk', 'VX2'), # standard output
# ('pluto-vtk', 'VX3'), # standard output
# ('pluto-vtk', 'temp')] # This is a user-defined output
```
%package help
Summary: Development documents and examples for yt-idefix
Provides: python3-yt-idefix-doc
%description help
# yt_idefix
[](https://pypi.org/project/yt_idefix/)
[](https://pypi.org/project/yt_idefix/)
[![yt-project](https://img.shields.io/static/v1?label="works%20with"&message="yt"&color="blueviolet")](https://yt-project.org)
<!--- Tests and style --->
[](https://github.com/neutrinoceros/yt_idefix/actions/workflows/ci.yml)
[](https://results.pre-commit.ci/latest/github/neutrinoceros/yt_idefix/main)
[](https://github.com/psf/black)
[](https://github.com/charliermarsh/ruff)
A maturing yt frontend for Idefix and Pluto, packaged as an extension for yt.
## Installation
```shell
python -m pip install yt_idefix
```
## Supported formats
| Code | format | supported since | additional dependencies |
|--------|:------:|:---------------:|-------------------------|
| Idefix | `.dmp` | v0.1.0 | |
| Idefix | `.vtk` | v0.3.0 | |
| Pluto | `.vtk` | v0.9.0 | |
| Pluto | XDMF | v1.1.0 | `h5py` |
## Usage
Integration with yt is seamless. *Installing* this plugin is all that's required to make yt
compatible with data formats supported by `yt_idefix` !
### Additional arguments to `yt.load`
The metadata are parsed from data file, definitions header file and inifile when loading dataset.
Definitions header file (`definitions.h` for Pluto, or `definitions.hpp` for Idefix) and inifile (`pluto.ini` and `idefix.ini` respectively) are discovered automatically if they match default names, are located along with data files, and unique. Otherwise, they can be specified explicitly as paths (either relative to data files or absolute paths) with parameters `definitions_header` and `inifile` respectively.
Geometry is parsed automatically whenever possible, but as a last resort, it can also be specified as a keyword argument (possible values are "cartesian", "spherical", "cylindrical" and "polar").
```python
# Examples
ds = yt.load("data.0010.vtk", definitions_header="../definitions.h", inifile="example.ini")
ds = yt.load("data.0010.vtk", geometry='spherical")
```
The data are loaded as physical quantities with units. The default unit system is `cgs` in yt. This frontend can convert data from code units into `cgs` properly, based on the unit definitions from metadata.
Users are able to choose the unit displayed in two ways, through `unit_system` ("code", "mks" and "cgs") and `units_override`(only valid for Pluto).
```python
# Examples on units
ds = yt.load("data.0010.vtk", unit_system='mks")
units_override = dict(length_unit=(100.0, "au"), mass_unit=yt.units.mass_sun)
ds = yt.load("data.0010.vtk", unit_override=unit_override) # Caution that other units will also be changed for consistency!!
```
With Pluto data, the rest of the system will be derived consistently with given units, within the following rules:
1. Temperature unit cannot be overridden (always set to Kelvin)
2. No more than three units can be overridden at once (overconstrained systems are never validated for simplicity)
3. When given less than three overrides, base units in Pluto (ordered: velocity_unit, density_unit, length_unit) are assumed
4. The following combinations are not allowed
```python
{"magnetic_unit", "velocity_unit", "density_unit"},
{"velocity_unit", "time_unit", "length_unit"},
{"density_unit", "length_unit", "mass_unit"},
```
yt is able to provide some derived fields from existed fields, e.g., `"cell_volume"`. Fields related to element species can be created according to primordial abundances of H and He, through `default_species_fields` (`"neutral"` and `"ionized"`) parameters.
```python
# Example
ds = yt.load("data.0010.vtk", default_species_fields="ionized")
```
### Convention of field names
The outputs are loaded from disk with field names in uppercase. This normalization is only applied to the standard outputs but user-defined outputs and Pluto's ion fraction outputs.
```python
# Example
ds.field_list
# Output:
# [('pluto-vtk', 'PRS'), # standard output
# ('pluto-vtk', 'RHO'), # standard output
# ('pluto-vtk', 'VX1'), # standard output
# ('pluto-vtk', 'VX2'), # standard output
# ('pluto-vtk', 'VX3'), # standard output
# ('pluto-vtk', 'temp')] # This is a user-defined output
```
%prep
%autosetup -n yt_idefix-2.2.0
%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-yt-idefix -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Jun 09 2023 Python_Bot <Python_Bot@openeuler.org> - 2.2.0-1
- Package Spec generated
|
