This repository was archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.xml
More file actions
241 lines (189 loc) · 12.7 KB
/
index.xml
File metadata and controls
241 lines (189 loc) · 12.7 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
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Apollo Group Site</title>
<link>https://stride-apollo.github.io/</link>
<description>Recent content on Apollo Group Site</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Tue, 27 Jun 2017 22:21:17 +0100</lastBuildDate>
<atom:link href="https://stride-apollo.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Final Demo</title>
<link>https://stride-apollo.github.io/post/FinalDemo/</link>
<pubDate>Tue, 27 Jun 2017 22:21:17 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/FinalDemo/</guid>
<description><p>Tomorrow, we&rsquo;ll show you our project.</p>
<p>We&rsquo;ll present the following features:</p>
<ul>
<li>Population generating.</li>
<li>Our Stride visualisation tool.</li>
<li>Multi region shared memory.</li>
<li>Checkpointing functionality.</li>
</ul>
<p>A more detailed description can be found in the <a href="https://stride-apollo.github.io/pdfs/DraaiboekFinal.pdf">script</a>
and the <a href="https://stride-apollo.github.io/pdfs/PowerPointFinal.pdf">powerpoint</a>.</p>
</description>
</item>
<item>
<title>Final deadline</title>
<link>https://stride-apollo.github.io/post/FinalDeadline/</link>
<pubDate>Sun, 25 Jun 2017 23:09:56 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/FinalDeadline/</guid>
<description><p>The Apollo project is done.</p>
<p>After 5-6 months, it&rsquo;s over.
We&rsquo;ve implemented the following features:</p>
<ul>
<li>A visualization tool with lots of graphs.</li>
<li>Multi region shared memory.</li>
<li>HDF5 checkpointing (works with Multi region).</li>
<li>A generator of synthetic populations (whose performance was drastically improved during the project).</li>
<li>A library for multithreaded programming, giving the user the choice to use TBB or OpenMP.</li>
</ul>
<p>However, we&rsquo;ve failed to implement some features:</p>
<ul>
<li>Multi region MPI: We were very close to a solution. The reason this part is delayed, is because MPI consists of very old C code.</li>
<li>The performance report concerning multithreading: We gave Multi region MPI priority over this.</li>
<li>Paraview: Due to the inability to compile Paraview, we couldn&rsquo;t work on this feature.</li>
</ul>
<p>We hope our efforts will help the Stride project in its future endeavours.</p>
<p>Sincerely, The Apollo Team</p>
</description>
</item>
<item>
<title>Beta Version</title>
<link>https://stride-apollo.github.io/post/Beta%20Version/</link>
<pubDate>Sun, 21 May 2017 23:26:45 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/Beta%20Version/</guid>
<description><p>We are proud to tell you that our beta version of the Apollo project is ready for takeoff.</p>
<p>Upcoming Tuesday, we&rsquo;ll show you the following:</p>
<ul>
<li>UniPar, a multithreading library using OpenMP and TBB.</li>
<li>Our Stride visualisation tool.</li>
</ul>
<p>For our presentation, we&rsquo;ll use the following <a href="https://stride-apollo.github.io/pdfs/Draaiboek.pdf">script</a>
and this <a href="https://stride-apollo.github.io/pdfs/PowerPoint.pdf">powerpoint</a>.</p>
</description>
</item>
<item>
<title>Visualisation technologies</title>
<link>https://stride-apollo.github.io/post/Visualisation%20technologies/</link>
<pubDate>Tue, 09 May 2017 22:33:00 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/Visualisation%20technologies/</guid>
<description><p>The visualisation extension is taking large strides towards making a great product into an excellent product!</p>
<p>After some turbulences in the choice of our technologies for the visualisation, we finally cut the knot. We are now on an escape trajectory towards success!
To design our GUI, we chose to use a browser. We made this choice because there are many JavaScript visualisation libraries. <br/>
One of these libraries is &ldquo;mapbox&rdquo;. Mapbox helps us to put the data on an interactive world map. It looks amazing and it is easy to use. <br/>
But mapbox alone isn&rsquo;t enough. We need graphs, lots and lots of graphs! This is why we decided to use &ldquo;plotly&rdquo;. Plotly has great, interactive graphs and is also easy to use. <br/>
To run all this, we used electron. This allows us to read local files without getting safety errors from certain browsers.</p>
<p>mapbox: <a href="https://www.mapbox.com/mapbox.js/api/v3.1.0/">https://www.mapbox.com/mapbox.js/api/v3.1.0/</a> <br/>
plotly: <a href="https://plot.ly/javascript/">https://plot.ly/javascript/</a> <br/>
electron: <a href="https://electron.atom.io/">https://electron.atom.io/</a> <br/></p>
<p>Great libraries, great team, excellent software.</p>
<p>Apollo is shooting for the stars.</p>
</description>
</item>
<item>
<title>Alpha Version</title>
<link>https://stride-apollo.github.io/post/Alpha%20Version/</link>
<pubDate>Sun, 30 Apr 2017 14:23:45 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/Alpha%20Version/</guid>
<description><p>We are proud to tell you that our alpha version of the Apollo project is ready for takeoff.</p>
<p>Upcoming Tuesday, we&rsquo;ll present the following:</p>
<ul>
<li>The population Generator in its full glory!</li>
<li>Checkpointing functionality like you&rsquo;ve never seen before!</li>
<li>The multi region aspect (shared memory), which is working like a charm!</li>
<li>A fantastic, hardworking team, destined to build the greatest software ever known to mankind.</li>
</ul>
</description>
</item>
<item>
<title>Planning update</title>
<link>https://stride-apollo.github.io/post/planning2/</link>
<pubDate>Mon, 03 Apr 2017 12:12:56 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/planning2/</guid>
<description><p>Our planning has changed:</p>
<p>You can take a look by following this link: <a href="https://app.teamweek.com/#p/zljsu_cs82erwwr0vaz-">https://app.teamweek.com/#p/zljsu_cs82erwwr0vaz-</a></p>
</description>
</item>
<item>
<title>Progress update</title>
<link>https://stride-apollo.github.io/post/deadlines2/</link>
<pubDate>Mon, 03 Apr 2017 11:57:00 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/deadlines2/</guid>
<description><p>Time for another update. Here you can find a summary of our deadlines:</p>
<ol>
<li>Population Generator 3.a:
<ul>
<li>A working version is available.</li>
<li>Not all requirements are met at the moment.</li>
<li>The performance of the generator is very bad and will need further inspection.</li>
<li>Current tests are successful</li>
</ul></li>
<li>HDF5 implementation and tests 1.d: OK.</li>
<li>MR shared memory 4.b: This was a lot harder than we foresaw. We didn&rsquo;t make much progress.</li>
</ol>
<p>Due to missed deadlines, we&rsquo;ll have to adjust our planning.</p>
</description>
</item>
<item>
<title>Planning update</title>
<link>https://stride-apollo.github.io/post/planning1/</link>
<pubDate>Sat, 25 Mar 2017 12:08:00 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/planning1/</guid>
<description><p>Due to previous mentioned problems, our planning has changed:</p>
<p>You can take a look by following this link: <a href="https://app.teamweek.com/#p/tgzpamvj5-echgwme5zc">https://app.teamweek.com/#p/tgzpamvj5-echgwme5zc</a></p>
</description>
</item>
<item>
<title>Progress update</title>
<link>https://stride-apollo.github.io/post/deadlines1/</link>
<pubDate>Sun, 19 Mar 2017 16:33:00 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/deadlines1/</guid>
<description><p>Up until now, we have passed the end date of 5 deadlines. Here you can find a summary of these deadlines:</p>
<ol>
<li>Pubsub: OK.</li>
<li>HDF5 prototype: OK.</li>
<li>Population generator: Not OK. We found some inconsistencies in the assignment. There is not yet a solution for these problems. We temporarily made our own solution.</li>
<li>HDF5 format: OK.</li>
<li>MR architecture: OK.</li>
</ol>
</description>
</item>
<item>
<title>Our Git Workflow</title>
<link>https://stride-apollo.github.io/post/git/</link>
<pubDate>Fri, 24 Feb 2017 17:05:05 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/git/</guid>
<description><p>We use both Github and Bitbucket to host our code. Our git workflow is based on the use of branches and pull requests. When trying to add or change something significant in size, the expected workflow is as follows:</p>
<ol>
<li>Create a new branch, based on <code>master</code>.</li>
<li>Add commits to the branch. If needed, one can merge <code>master</code> into the branch to prevent merge conflicts later on. This is useful when development on the branch is taking a long time and <code>master</code> has significantly deviated from when the branch was started.</li>
<li>When the branch is in a finished state, the developer(s) submits a pull request. For this, we use Github because of its superior support:
<ul>
<li><strong>CI</strong>: Github shows the status of the CI server. If some tests fail, Github will warn us.</li>
<li><strong>Reviews</strong>: One can request reviews from other developers, which can then give comments both in general and relating to a specific line of code.</li>
<li><strong>Milestones</strong>: A pull request can be coupled to a milestone in order to better track progress.</li>
</ul></li>
<li>Based on the feedback, a developer can add more commits (which will show up in Github&rsquo;s interface)</li>
<li>When everyone (including the CI server) agrees, the branch is merged into <code>master</code> and deleted.</li>
</ol>
<p>Although the pull requests themselves aren&rsquo;t visible in Bitbucket (they are not part of git), all branches, commits and merges are basic git features and will therefore be perfectly visible in Bitbucket.</p>
<p>Apart from the <code>master</code> branch and the feature branches, we have two other branches:</p>
<ul>
<li><code>original</code> is for the original code coming from the central stride repository on Bitbucket. When new functionality is released, this will get merged into <code>master</code>.</li>
<li><code>blessed</code> will simply be a more stable version of <code>master</code>, updated every week.</li>
</ul>
</description>
</item>
<item>
<title>Hello World</title>
<link>https://stride-apollo.github.io/post/welcome/</link>
<pubDate>Wed, 15 Feb 2017 14:09:08 +0100</pubDate>
<guid>https://stride-apollo.github.io/post/welcome/</guid>
<description><p>Welcome to our new site. The site is built with <a href="https://gohugo.io/">Hugo</a> using the <a href="http://themes.gohugo.io/prologue/">Prologue</a> theme (although heavily modified), hosted on <a href="https://pages.github.com/">Github Pages</a>. If we have something interesting to say during the development process, we will post it as a blog article, otherwise this site serves as reference to point to other online resources.</p>
</description>
</item>
</channel>
</rss>