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
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
|
%global _empty_manifest_terminate_build 0
Name: python-analysis-engine
Version: 2.0.11
Release: 1
Summary: Analysis for the UK Department for Transport's major projects portfolio
License: MIT License
URL: https://github.com/banillie/analysis_engine
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ca/09/13dd5ab6f8ec21a5362ae364f20c0b72e3f91302745ea03cfc092623b07a/analysis_engine-2.0.11.tar.gz
BuildArch: noarch
Requires: python3-datamaps
Requires: python3-docx
Requires: python3-openpyxl
Requires: python3-matplotlib
Requires: python3-pdf2image
Requires: python3-xlrd
%description
# analysis_engine
Software for portfolio management reporting and analysis in the UK Department for Transport, operated via command line
interface (CLI) prompts.
## Installing
Python must be installed on your computer. If not already installed, it can be installed via the python website
[here](https://www.python.org/downloads/). **IMPORTANT** ensure that `Add Python to PATH` is ticked when provided
with the option as part of the installation wizard.
Open the command line terminal (Windows) or bash shell and install via `pip install analysis_engine`.
## Directories, file paths and poppler.
In order to operate the correct directories and files must be set-up and saved on the user's computer.
`analysis_engine` is able to handle different operating systems.
Create the following directories in your `My Documents` directory:
|-- ipdc
|-- core_data
|-- json
|-- input
|-- output
|-- top250
|-- core_data
|-- json
|-- input
|-- output
Each reporting process e.g. ipdc and top250, respective `core_data` directorates require:
1) excel master data files;
2) excel project information file; and,
3) A confi.ini file. This file lists and master data and project information file names.
As a minimum the `input` folder should have the following documents `summary_temp.docx`,
`summary_temp_landscape.docx`. In addition `ipdc\input` should have the
`dashboards_master.xlsx` file.
All outputs from analysis_engine will be saved into the `output` directory.
The `json` folder is where analysis_engine saves master data in an easily accessible
format (.json) and after setup can be ignored by the user.
Unfortunately there is one further manual installation, related to a package within analysis_engine
which enables high quality rendering of graphical outputs to word documents. On Windows do the following:
1) Download zip of poppler release from this link https://github.com/oschwartz10612/poppler-windows/releases/download/v21.03.0/Release-21.03.0.zip.
2) unzip and move the whole directory to My Documents.
3) Add the poppler bin directory to PATH following these instructions
https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/
4) Reboot computer.
Mac users should follow instructions here https://pypi.org/project/pdf2image/
Most Linux distributions should not require any manual installation.
## Operating analysis_engine
To operate analysis_engine the user must enter the initial **_command_**
`analysis` followed by a _**subcommand**_ to specify the reporting process e.g
`ipdc` or `top250` and then finally an analytical output **_argument_**, the options
for which are set out below.
**NOTE** the `--help` option is available throughout the entire command
line prompt construction process and the user should use it for guidance on what subcommands
and arguments are available for use.
analysis_engine currently has the following _arguments_:
`initiate` The user must enter this command
every time master data, contained in the core_data directory, is updated.
The initiate checks and validates the data in a number of ways.
`dashboards` populates the IPDC PfM report dashboard. A blank template dashboard
must be saved in the ipdc/input directory. (Not currently available for top250.)
`dandelion` produces the portfolio dandelion info-graphic.
`costs` produces a cost profile trend graph and data. (Not currently available for top250.)
`milestones` produces milestone schedule graphs and data.
`vfm` produces vfm data. (Not currently available for top250.)
`summaries` produces project summary reports.
`risks` produces risk data. (Not currently available for top250.)
`dcas` produces dca data. (Not currently available for top250.)
`speedial` prints out changes in project dca ratings. (Not currently available for top250.)
`query` returns (from master data) specific data required by the user.
The default for each argument is to return outputs with current and last quarter data.
Further to each argument the user can specify one or many
further **_optional_arguments_** to alter the analytical output produced. There are
many optional_arguments available, which vary for each argument,
and the user should use the `--help` option to specify those that are available.
%package -n python3-analysis-engine
Summary: Analysis for the UK Department for Transport's major projects portfolio
Provides: python-analysis-engine
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-analysis-engine
# analysis_engine
Software for portfolio management reporting and analysis in the UK Department for Transport, operated via command line
interface (CLI) prompts.
## Installing
Python must be installed on your computer. If not already installed, it can be installed via the python website
[here](https://www.python.org/downloads/). **IMPORTANT** ensure that `Add Python to PATH` is ticked when provided
with the option as part of the installation wizard.
Open the command line terminal (Windows) or bash shell and install via `pip install analysis_engine`.
## Directories, file paths and poppler.
In order to operate the correct directories and files must be set-up and saved on the user's computer.
`analysis_engine` is able to handle different operating systems.
Create the following directories in your `My Documents` directory:
|-- ipdc
|-- core_data
|-- json
|-- input
|-- output
|-- top250
|-- core_data
|-- json
|-- input
|-- output
Each reporting process e.g. ipdc and top250, respective `core_data` directorates require:
1) excel master data files;
2) excel project information file; and,
3) A confi.ini file. This file lists and master data and project information file names.
As a minimum the `input` folder should have the following documents `summary_temp.docx`,
`summary_temp_landscape.docx`. In addition `ipdc\input` should have the
`dashboards_master.xlsx` file.
All outputs from analysis_engine will be saved into the `output` directory.
The `json` folder is where analysis_engine saves master data in an easily accessible
format (.json) and after setup can be ignored by the user.
Unfortunately there is one further manual installation, related to a package within analysis_engine
which enables high quality rendering of graphical outputs to word documents. On Windows do the following:
1) Download zip of poppler release from this link https://github.com/oschwartz10612/poppler-windows/releases/download/v21.03.0/Release-21.03.0.zip.
2) unzip and move the whole directory to My Documents.
3) Add the poppler bin directory to PATH following these instructions
https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/
4) Reboot computer.
Mac users should follow instructions here https://pypi.org/project/pdf2image/
Most Linux distributions should not require any manual installation.
## Operating analysis_engine
To operate analysis_engine the user must enter the initial **_command_**
`analysis` followed by a _**subcommand**_ to specify the reporting process e.g
`ipdc` or `top250` and then finally an analytical output **_argument_**, the options
for which are set out below.
**NOTE** the `--help` option is available throughout the entire command
line prompt construction process and the user should use it for guidance on what subcommands
and arguments are available for use.
analysis_engine currently has the following _arguments_:
`initiate` The user must enter this command
every time master data, contained in the core_data directory, is updated.
The initiate checks and validates the data in a number of ways.
`dashboards` populates the IPDC PfM report dashboard. A blank template dashboard
must be saved in the ipdc/input directory. (Not currently available for top250.)
`dandelion` produces the portfolio dandelion info-graphic.
`costs` produces a cost profile trend graph and data. (Not currently available for top250.)
`milestones` produces milestone schedule graphs and data.
`vfm` produces vfm data. (Not currently available for top250.)
`summaries` produces project summary reports.
`risks` produces risk data. (Not currently available for top250.)
`dcas` produces dca data. (Not currently available for top250.)
`speedial` prints out changes in project dca ratings. (Not currently available for top250.)
`query` returns (from master data) specific data required by the user.
The default for each argument is to return outputs with current and last quarter data.
Further to each argument the user can specify one or many
further **_optional_arguments_** to alter the analytical output produced. There are
many optional_arguments available, which vary for each argument,
and the user should use the `--help` option to specify those that are available.
%package help
Summary: Development documents and examples for analysis-engine
Provides: python3-analysis-engine-doc
%description help
# analysis_engine
Software for portfolio management reporting and analysis in the UK Department for Transport, operated via command line
interface (CLI) prompts.
## Installing
Python must be installed on your computer. If not already installed, it can be installed via the python website
[here](https://www.python.org/downloads/). **IMPORTANT** ensure that `Add Python to PATH` is ticked when provided
with the option as part of the installation wizard.
Open the command line terminal (Windows) or bash shell and install via `pip install analysis_engine`.
## Directories, file paths and poppler.
In order to operate the correct directories and files must be set-up and saved on the user's computer.
`analysis_engine` is able to handle different operating systems.
Create the following directories in your `My Documents` directory:
|-- ipdc
|-- core_data
|-- json
|-- input
|-- output
|-- top250
|-- core_data
|-- json
|-- input
|-- output
Each reporting process e.g. ipdc and top250, respective `core_data` directorates require:
1) excel master data files;
2) excel project information file; and,
3) A confi.ini file. This file lists and master data and project information file names.
As a minimum the `input` folder should have the following documents `summary_temp.docx`,
`summary_temp_landscape.docx`. In addition `ipdc\input` should have the
`dashboards_master.xlsx` file.
All outputs from analysis_engine will be saved into the `output` directory.
The `json` folder is where analysis_engine saves master data in an easily accessible
format (.json) and after setup can be ignored by the user.
Unfortunately there is one further manual installation, related to a package within analysis_engine
which enables high quality rendering of graphical outputs to word documents. On Windows do the following:
1) Download zip of poppler release from this link https://github.com/oschwartz10612/poppler-windows/releases/download/v21.03.0/Release-21.03.0.zip.
2) unzip and move the whole directory to My Documents.
3) Add the poppler bin directory to PATH following these instructions
https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/
4) Reboot computer.
Mac users should follow instructions here https://pypi.org/project/pdf2image/
Most Linux distributions should not require any manual installation.
## Operating analysis_engine
To operate analysis_engine the user must enter the initial **_command_**
`analysis` followed by a _**subcommand**_ to specify the reporting process e.g
`ipdc` or `top250` and then finally an analytical output **_argument_**, the options
for which are set out below.
**NOTE** the `--help` option is available throughout the entire command
line prompt construction process and the user should use it for guidance on what subcommands
and arguments are available for use.
analysis_engine currently has the following _arguments_:
`initiate` The user must enter this command
every time master data, contained in the core_data directory, is updated.
The initiate checks and validates the data in a number of ways.
`dashboards` populates the IPDC PfM report dashboard. A blank template dashboard
must be saved in the ipdc/input directory. (Not currently available for top250.)
`dandelion` produces the portfolio dandelion info-graphic.
`costs` produces a cost profile trend graph and data. (Not currently available for top250.)
`milestones` produces milestone schedule graphs and data.
`vfm` produces vfm data. (Not currently available for top250.)
`summaries` produces project summary reports.
`risks` produces risk data. (Not currently available for top250.)
`dcas` produces dca data. (Not currently available for top250.)
`speedial` prints out changes in project dca ratings. (Not currently available for top250.)
`query` returns (from master data) specific data required by the user.
The default for each argument is to return outputs with current and last quarter data.
Further to each argument the user can specify one or many
further **_optional_arguments_** to alter the analytical output produced. There are
many optional_arguments available, which vary for each argument,
and the user should use the `--help` option to specify those that are available.
%prep
%autosetup -n analysis-engine-2.0.11
%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-analysis-engine -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 2.0.11-1
- Package Spec generated
|
