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
|
%global _empty_manifest_terminate_build 0
Name: python-microconventions
Version: 1.0.0
Release: 1
Summary: Conventions used at MicroPrediction.Org
License: MIT
URL: https://github.com/microprediction/microconventions
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/0f/f7/19d9ad8cf763446e3b6958f9eb0732680acb82acf90aea26c4956e9c2e10/microconventions-1.0.0.tar.gz
BuildArch: noarch
Requires: python3-muid
Requires: python3-getjson
Requires: python3-pymorton
Requires: python3-tdigest
Requires: python3-numpy
Requires: python3-scipy
Requires: python3-deepdiff
Requires: python3-schema
%description
If you participate, it is worth a glance at this little library. It is intended to be readable code documenting some choices made.
## Stream conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stream_conventions.py))
Governs which names can be top level streams, as compared with derived streams involving tildes. The main thing to remember is that stream names end in .json
mystream.json
There is a small chance the author regrets the '.json' (though it keeps open various possibilities).
## Key conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/key_conventions.py))
Refers to the use of Memorable Unique Identifiers. This code wraps the functionality provided at www.muid.org and the MUID Python Package so that it need not be used directly. There are minor distinctions between MUIDs and write_keys. For one thing, MUIDs are often binary strings whereas write_keys are str. This mixin also provides you with conversions between private write_key's, public hashes of the same using shash() that are referred to as codes sometimes, and the spirit animals suggested by the leading characters of the codes.
## Value conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/value_conventions.py))
Refers to kinds of values. Generally you will not need to worry about this. A time of writing only scalar float values are the subject of community prediction. However other types of value can be stored and the manner in which this is done can depend on the size.
## Horizon conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/horizon_conventions.py))
A horizon is a combination of a data stream and a time interval measured in seconds, called a delay. Usually the combination is represented as a string with double colon separator. For example
70::mystream.json
might reference a 1 minute (roughly) ahead forecast.
## Leaderboard conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/leaderboard_conventions.py))
Names for various types of leaderboards. I don't think it is important to study this but the client library needs it.
## Stats conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stats_conventions.py))
Not much here, just some backward compatability for norminv, default abscissa for CDFs and the like.
## Z-Curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
Refers in part to naming conventions for derived streams. For example:
z1~mystream::70.json
is a data stream generated by computing the community implied z-score of points in the stream mystream.json. A community implied z-score is a z-score computed relative to the distribution implied by everyone's predictions. We need to choose a prediction horizon (delay) to specify this. So this particular example refers to z-scores relative to the short horizon predictions (1 minute ahead of time). On the other hand,
z1~mystream::3555.json
would refer to z-scores relative to 1 hour ahead forecasts.
### Space filling curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
The zcurve conventions also specify maps [0,1]^2 -> R and [0,1]^3->R that are used to take pairs and triples of z-scores and create univariate
data streams. These are space filling curves arrived at by interleaving the digits in the binary representations. In the case of two dimensions this is similar to geohashing. These streams are
denoted as follows:
z2~bob~mary::3555.json
refers to embeddings of z-scores from streams bob.json and mary.json. Here is a [video](https://www.swarmprediction.com/zcurves.html) that explains the embedding better than I can.
### Miscellaneous ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/misc_conventions.py))
I dare say some of these might migrate, but the code in misc_conventions provides a collection of naming conventions that you will need to know if you wish to use
the fairly powerful /live API (see https://api.microprediction.org and scroll to "Live"). This API can be used to extract various quantities in the database, not
all of whom have their own standalone APIs. For example you can get lagged time/value pairs in two ways:
https://api.microprediction.org/live/lagged::cop.json
https://api.microprediction.org/lagged/cop.json
however if you really just want the values you can only get it as
https://api.microprediction.org/live/lagged_values::cop.json
Similarly you can get confirms, warnings, errors, transactions and so on all using /live. This may or may not help if you want to quickly write a client
in another language.
%package -n python3-microconventions
Summary: Conventions used at MicroPrediction.Org
Provides: python-microconventions
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-microconventions
If you participate, it is worth a glance at this little library. It is intended to be readable code documenting some choices made.
## Stream conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stream_conventions.py))
Governs which names can be top level streams, as compared with derived streams involving tildes. The main thing to remember is that stream names end in .json
mystream.json
There is a small chance the author regrets the '.json' (though it keeps open various possibilities).
## Key conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/key_conventions.py))
Refers to the use of Memorable Unique Identifiers. This code wraps the functionality provided at www.muid.org and the MUID Python Package so that it need not be used directly. There are minor distinctions between MUIDs and write_keys. For one thing, MUIDs are often binary strings whereas write_keys are str. This mixin also provides you with conversions between private write_key's, public hashes of the same using shash() that are referred to as codes sometimes, and the spirit animals suggested by the leading characters of the codes.
## Value conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/value_conventions.py))
Refers to kinds of values. Generally you will not need to worry about this. A time of writing only scalar float values are the subject of community prediction. However other types of value can be stored and the manner in which this is done can depend on the size.
## Horizon conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/horizon_conventions.py))
A horizon is a combination of a data stream and a time interval measured in seconds, called a delay. Usually the combination is represented as a string with double colon separator. For example
70::mystream.json
might reference a 1 minute (roughly) ahead forecast.
## Leaderboard conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/leaderboard_conventions.py))
Names for various types of leaderboards. I don't think it is important to study this but the client library needs it.
## Stats conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stats_conventions.py))
Not much here, just some backward compatability for norminv, default abscissa for CDFs and the like.
## Z-Curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
Refers in part to naming conventions for derived streams. For example:
z1~mystream::70.json
is a data stream generated by computing the community implied z-score of points in the stream mystream.json. A community implied z-score is a z-score computed relative to the distribution implied by everyone's predictions. We need to choose a prediction horizon (delay) to specify this. So this particular example refers to z-scores relative to the short horizon predictions (1 minute ahead of time). On the other hand,
z1~mystream::3555.json
would refer to z-scores relative to 1 hour ahead forecasts.
### Space filling curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
The zcurve conventions also specify maps [0,1]^2 -> R and [0,1]^3->R that are used to take pairs and triples of z-scores and create univariate
data streams. These are space filling curves arrived at by interleaving the digits in the binary representations. In the case of two dimensions this is similar to geohashing. These streams are
denoted as follows:
z2~bob~mary::3555.json
refers to embeddings of z-scores from streams bob.json and mary.json. Here is a [video](https://www.swarmprediction.com/zcurves.html) that explains the embedding better than I can.
### Miscellaneous ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/misc_conventions.py))
I dare say some of these might migrate, but the code in misc_conventions provides a collection of naming conventions that you will need to know if you wish to use
the fairly powerful /live API (see https://api.microprediction.org and scroll to "Live"). This API can be used to extract various quantities in the database, not
all of whom have their own standalone APIs. For example you can get lagged time/value pairs in two ways:
https://api.microprediction.org/live/lagged::cop.json
https://api.microprediction.org/lagged/cop.json
however if you really just want the values you can only get it as
https://api.microprediction.org/live/lagged_values::cop.json
Similarly you can get confirms, warnings, errors, transactions and so on all using /live. This may or may not help if you want to quickly write a client
in another language.
%package help
Summary: Development documents and examples for microconventions
Provides: python3-microconventions-doc
%description help
If you participate, it is worth a glance at this little library. It is intended to be readable code documenting some choices made.
## Stream conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stream_conventions.py))
Governs which names can be top level streams, as compared with derived streams involving tildes. The main thing to remember is that stream names end in .json
mystream.json
There is a small chance the author regrets the '.json' (though it keeps open various possibilities).
## Key conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/key_conventions.py))
Refers to the use of Memorable Unique Identifiers. This code wraps the functionality provided at www.muid.org and the MUID Python Package so that it need not be used directly. There are minor distinctions between MUIDs and write_keys. For one thing, MUIDs are often binary strings whereas write_keys are str. This mixin also provides you with conversions between private write_key's, public hashes of the same using shash() that are referred to as codes sometimes, and the spirit animals suggested by the leading characters of the codes.
## Value conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/value_conventions.py))
Refers to kinds of values. Generally you will not need to worry about this. A time of writing only scalar float values are the subject of community prediction. However other types of value can be stored and the manner in which this is done can depend on the size.
## Horizon conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/horizon_conventions.py))
A horizon is a combination of a data stream and a time interval measured in seconds, called a delay. Usually the combination is represented as a string with double colon separator. For example
70::mystream.json
might reference a 1 minute (roughly) ahead forecast.
## Leaderboard conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/leaderboard_conventions.py))
Names for various types of leaderboards. I don't think it is important to study this but the client library needs it.
## Stats conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/stats_conventions.py))
Not much here, just some backward compatability for norminv, default abscissa for CDFs and the like.
## Z-Curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
Refers in part to naming conventions for derived streams. For example:
z1~mystream::70.json
is a data stream generated by computing the community implied z-score of points in the stream mystream.json. A community implied z-score is a z-score computed relative to the distribution implied by everyone's predictions. We need to choose a prediction horizon (delay) to specify this. So this particular example refers to z-scores relative to the short horizon predictions (1 minute ahead of time). On the other hand,
z1~mystream::3555.json
would refer to z-scores relative to 1 hour ahead forecasts.
### Space filling curve conventions ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/zcurve_conventions.py))
The zcurve conventions also specify maps [0,1]^2 -> R and [0,1]^3->R that are used to take pairs and triples of z-scores and create univariate
data streams. These are space filling curves arrived at by interleaving the digits in the binary representations. In the case of two dimensions this is similar to geohashing. These streams are
denoted as follows:
z2~bob~mary::3555.json
refers to embeddings of z-scores from streams bob.json and mary.json. Here is a [video](https://www.swarmprediction.com/zcurves.html) that explains the embedding better than I can.
### Miscellaneous ([code](https://github.com/microprediction/microconventions/blob/master/microconventions/misc_conventions.py))
I dare say some of these might migrate, but the code in misc_conventions provides a collection of naming conventions that you will need to know if you wish to use
the fairly powerful /live API (see https://api.microprediction.org and scroll to "Live"). This API can be used to extract various quantities in the database, not
all of whom have their own standalone APIs. For example you can get lagged time/value pairs in two ways:
https://api.microprediction.org/live/lagged::cop.json
https://api.microprediction.org/lagged/cop.json
however if you really just want the values you can only get it as
https://api.microprediction.org/live/lagged_values::cop.json
Similarly you can get confirms, warnings, errors, transactions and so on all using /live. This may or may not help if you want to quickly write a client
in another language.
%prep
%autosetup -n microconventions-1.0.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-microconventions -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.0-1
- Package Spec generated
|
