-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathFossee Demo Video Caption.srt
More file actions
263 lines (198 loc) · 4.61 KB
/
Fossee Demo Video Caption.srt
File metadata and controls
263 lines (198 loc) · 4.61 KB
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
1
00:00:00,620 --> 00:00:03,453
Hi I am Mausam Kar. This is my
2
00:00:03,453 --> 00:00:04,870
hybrid chemical equipment visualizer.
3
00:00:04,870 --> 00:00:07,704
Let's jump straight in. I am logging into
4
00:00:07,704 --> 00:00:10,183
the web app first. First I will
5
00:00:10,183 --> 00:00:12,662
demonstrate the CSV upload by I am
6
00:00:12,662 --> 00:00:14,787
selecting the required sample CSV. The
7
00:00:14,787 --> 00:00:17,267
Jango back end parses this using pandas
8
00:00:17,267 --> 00:00:19,392
and instantly returns the analytics. Here
9
00:00:19,392 --> 00:00:21,684
are the. Visualizations using Chart JS.
10
00:00:21,684 --> 00:00:24,333
As we can see, the visualizations are
11
00:00:24,333 --> 00:00:26,225
the distribution by equipment type,
12
00:00:26,225 --> 00:00:28,118
correlation between pressure and flow
13
00:00:28,118 --> 00:00:30,388
rate, and temperature trends over time.
14
00:00:30,388 --> 00:00:33,038
Here are the visualization. As we can
15
00:00:33,038 --> 00:00:35,687
see, we also have a history management
16
00:00:35,687 --> 00:00:38,336
saving the last five uploads for quick
17
00:00:38,336 --> 00:00:41,180
access for each user. And also we
18
00:00:41,180 --> 00:00:43,848
have a global log for all the user
19
00:00:43,848 --> 00:00:46,183
uploads. We also have a dedicated feature
20
00:00:46,183 --> 00:00:48,517
and guides page and a context section.
21
00:00:48,517 --> 00:00:50,518
For now switching to the desktop
22
00:00:50,518 --> 00:00:52,853
application built with Pyqt 5, I am
23
00:00:52,853 --> 00:00:54,854
logging in with same credentials. Notice
24
00:00:54,854 --> 00:00:57,522
how the data I just uploaded on the
25
00:00:57,522 --> 00:00:59,523
web is immediately available here. This
26
00:00:59,523 --> 00:01:01,680
proves the share back end. Integration
27
00:01:01,680 --> 00:01:04,620
Instead of web charts, we are using
28
00:01:04,620 --> 00:01:07,140
native matplotlib figures here for high
29
00:01:07,140 --> 00:01:08,820
performance offline analysis. For
30
00:01:08,820 --> 00:01:11,760
reporting I will just generate a PDF
31
00:01:11,760 --> 00:01:14,700
report which is created server side with
32
00:01:14,700 --> 00:01:17,220
report lab containing all the critical
33
00:01:17,220 --> 00:01:19,740
statistics and equipment lists. Also we
34
00:01:19,740 --> 00:01:22,676
can see the user information for. Each
35
00:01:22,676 --> 00:01:24,956
user logged in into the website within
36
00:01:24,956 --> 00:01:27,236
the dashboard for both web and the
37
00:01:27,236 --> 00:01:29,190
desktop app. Here how it looks.
38
00:01:30,970 --> 00:01:33,468
The entire stack is containerized using
39
00:01:33,468 --> 00:01:35,550
Docker. My Docker compose setup
40
00:01:35,550 --> 00:01:38,049
orchestrates this Django API, React front
41
00:01:38,049 --> 00:01:40,963
end and database volumes as we can
42
00:01:40,963 --> 00:01:43,878
see in our Docker desktop the images
43
00:01:43,878 --> 00:01:46,793
that we have created for the front
44
00:01:46,793 --> 00:01:49,707
end and back end services and also
45
00:01:49,707 --> 00:01:51,892
the containers. On which both the
46
00:01:51,892 --> 00:01:54,082
services are being running. Also we can
47
00:01:54,082 --> 00:01:56,586
see the detailed log of the back end
48
00:01:56,586 --> 00:01:59,089
requests sent to the front end. For back
49
00:01:59,089 --> 00:02:01,592
end hosting we have used render. So this
50
00:02:01,592 --> 00:02:03,783
is our render platform where we have
51
00:02:03,783 --> 00:02:06,286
hosted the back end. For front end we
52
00:02:06,286 --> 00:02:08,477
have used versal for deployment. This is
53
00:02:08,477 --> 00:02:10,667
my versal dashboard where I have hosted
54
00:02:10,667 --> 00:02:13,520
it. So as we can see, for
55
00:02:13,520 --> 00:02:16,427
24/7 availability of the back end we have
56
00:02:16,427 --> 00:02:18,607
used something called Uptime Robot. So
57
00:02:18,607 --> 00:02:20,787
this is the Django administration panel
58
00:02:20,787 --> 00:02:23,693
through which I can manage all the users
59
00:02:23,693 --> 00:02:25,510
who are using my application.
60
00:02:28,380 --> 00:02:31,177
The entire project is available in GitHub
61
00:02:31,177 --> 00:02:33,973
and the documentation for the same is
62
00:02:33,973 --> 00:02:36,370
being provided along with the preview
63
00:02:36,370 --> 00:02:38,368
images for the application. The
64
00:02:38,368 --> 00:02:40,366
architecture diagrams for both dockerized
65
00:02:40,366 --> 00:02:42,763
and non dockerized development are being
66
00:02:42,763 --> 00:02:45,160
provided in the README as well.