-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfeed.xml
More file actions
executable file
·414 lines (378 loc) · 17.5 KB
/
feed.xml
File metadata and controls
executable file
·414 lines (378 loc) · 17.5 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
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
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>OSU CIA</title>
<description>OSU Cyberinsfrastructure Association</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
<pubDate>Thu, 21 Sep 2017 10:12:57 -0500</pubDate>
<lastBuildDate>Thu, 21 Sep 2017 10:12:57 -0500</lastBuildDate>
<generator>Jekyll v3.3.1</generator>
<item>
<title>Fourth General Meeting</title>
<description><h2 id="cyberinfrastructure-association">Cyberinfrastructure Association</h2>
<h3 id="meeting-minutes">Meeting Minutes</h3>
<p><strong>4:03</strong> Call to order</p>
<p><strong>4:03</strong> Overview of software and hardware meetings</p>
<ul>
<li>One or two per month each</li>
<li>Software
<ul>
<li>Working toward solving Tulsa competition code</li>
<li>Learning MPI</li>
</ul>
</li>
<li>Hardware
<ul>
<li>We’ll be using a loaned RPi cluster for now.</li>
<li>Will be doing a tour of Cowboy for members new to supercomputering</li>
</ul>
</li>
</ul>
<p><strong>4:05</strong> Tulsa Competition</p>
<ul>
<li>We can use Dr. Brunson’s Raspberry Pi cluster</li>
<li>Barring unforeseeable events, we will be able to attend the competition</li>
</ul>
<p><strong>4:06</strong> Club sponsorship</p>
<ul>
<li>Looking at CEAT Student Council for sponsor
<ul>
<li>Required bi-weekly meetings</li>
<li>Must provide service hours as club (E.G. At least one member)</li>
</ul>
</li>
</ul>
<p><strong>4:07</strong> Discuss Events</p>
<ul>
<li>Meet and greet
<ul>
<li>Would probably want to get some funding (people like these more with food)</li>
<li>Looking at doing something like a game night w/ food and occasional breaks for info regarding supercomputing etc.</li>
</ul>
</li>
<li>MPI Training session
<ul>
<li>We welcome members from software team to come as helpers</li>
<li>Like a “new user training” - fairly basic</li>
<li>Being developed by Software Team Leader, who will be working with Phillip from HPC class</li>
</ul>
</li>
</ul>
<p><strong>4:09</strong> Scheduling</p>
<ul>
<li>Option one:
<ul>
<li>1st week - general meeting</li>
<li>2nd week - software meeting</li>
<li>3rd week - hardware meeting</li>
<li>4th week - event/officer meeting</li>
</ul>
</li>
<li>Option two:
<ul>
<li>Biweekly general meetings which breakout into hardware and software team meetings</li>
<li>Benefit: We’re not dragging people out for 5 minutes if we don’t have a lot to discuss at the general meeting</li>
<li>Detriment: People would have to choose hardware or software, since they’re going at the same time<br />
<strong>Option two chosen</strong> after short discussion</li>
</ul>
</li>
</ul>
<p><strong>4:13</strong> Goals and Focus for the semester</p>
<ul>
<li>Software team
<ol>
<li>Learn the basics of MPI</li>
<li>Code for the Tulsa competition</li>
<li>Find code challenges online and complete them using parallel coding</li>
</ol>
</li>
<li>Hardware Team Goals
<ol>
<li>Learn methods for internally connecting the cluster</li>
<li>Learn how to install the OS and basic necessary programs</li>
<li>Learn how to install and use administrative programs - schedulers, assignment, etc
*Club focus for the semester</li>
<li>Learning</li>
<li>Growth</li>
<li>Competitions
<ul>
<li>Agreed that competitions and teaching events will spur growth, so focus on those for now</li>
</ul>
</li>
</ol>
</li>
</ul>
<p><strong>4:18</strong> Funding</p>
<ul>
<li>Due to a mixup, not eligible to apply for AFAP funding
<ul>
<li>Potentially able to get some funding from them after we become eligible by another process</li>
</ul>
</li>
<li>Can still apply for SGA co-sponsorship events</li>
<li>Fundraising
<ul>
<li>Benefit nights in restuarants (Not reliably funding, but potentially good for outreach)</li>
<li>Sporting events (Low pay to help with concession stands etc.)</li>
<li>Penny wars (?) or selling things (not available to us really)
*Discussion: If we get money, do we use it now or save it for next semester when we also have other resources for funding?</li>
<li>Save it for next semester - people are less likely to join mid-semester</li>
</ul>
</li>
</ul>
<p><strong>4:25</strong> Competition</p>
<ul>
<li>Do we want to host a competition?</li>
<li>We could start with internal competitions this semester, instead of trying to get a larger one going
<ul>
<li>Gives us some practice runs with less pressure, plus more time to schedule and plan a larger one.</li>
</ul>
</li>
<li>We could potentially enlist the German SC16 team in one competition via webstreaming or other
<ul>
<li>Tons of learning opportunity from a more established group</li>
</ul>
</li>
</ul>
<p><strong>4:29</strong> Closing statements</p>
<ul>
<li>Meeting in two weeks</li>
<li>Will have hardware and software meetings that week</li>
<li>Call to fill out doodle poll if interested in software/Tulsa competition</li>
</ul>
<p><strong>4:30</strong> Meeting Adjourned</p>
<p><strong>4:30</strong> Meeting re-opened</p>
<p><strong>4:30</strong> Develop quote of “what we are”</p>
<ul>
<li>“The Cyberinfrastructure Association’s goal is guiding educational and networking opportunities for OSU students interested in
Cyberinfrastructure and High-Performance Computing. “</li>
</ul>
<p><strong>4:35</strong> April 12th Conference</p>
<ul>
<li>Conference on how groups use computers/technology to improve their research</li>
<li>Can lead a student breakout session on how student clubs use tech
<ul>
<li>Would gather some other clubs to speak as well, we would just lead the event</li>
</ul>
</li>
</ul>
<p><strong>4:41</strong> Business School Outreach</p>
<ul>
<li>MSIS</li>
<li>A lot of them deal with big data</li>
<li>Marketting chair will look into getting some contacts for informing students about events etc.</li>
</ul>
<p><strong>4:45</strong> Meeting adjourned</p>
</description>
<pubDate>Wed, 08 Feb 2017 12:00:00 -0600</pubDate>
<link>/2017/02/08/GeneralMeeting/</link>
<guid isPermaLink="true">/2017/02/08/GeneralMeeting/</guid>
</item>
<item>
<title>Third General Meeting</title>
<description><h2 id="cyberinfrastructure-association">Cyberinfrastructure Association</h2>
<h3 id="meeting-agenda">Meeting Agenda</h3>
<ol>
<li>
<p>Call to Order: 6:13 p.m.</p>
</li>
<li>Roll Call
<ul>
<li>Officers present: Matthew Whitlock (President), Patrick McDonald (VP), Brandon White (Treasurer), Cameron Mehmken (Membership Chair), Christian Griffith (Marketing Chair)</li>
<li>Total Present: 10</li>
</ul>
</li>
<li>Open Issues:
<ul>
<li>Membership Fees
<ul>
<li>Reviewed wording for by-laws, merged pull request since last voted on</li>
</ul>
</li>
</ul>
</li>
<li>New Business
<ul>
<li>Cluster discussion
<ul>
<li>Brandon created a spreadsheet to compare specs</li>
<li>Orange Pi’s brought up as an option - a little more expensive but possibly more capable (also less documentation = could be more fun)</li>
</ul>
</li>
<li>Creation of “Teams”
<ul>
<li>Software and Hardware Team Leaders were voted on to be created last meeting</li>
<li>Elections done on Slack as a possibility - also looking at poll conductors, forms, etc.</li>
<li>Leaders don’t need to be experts but need to be committed and organized, willing to ask and learn, and keep their teams on task</li>
<li>Software Leader could help guide “Virtual Machine Cluster”
<ul>
<li>Get the virtual machine running without having to wait for hardware</li>
</ul>
</li>
</ul>
</li>
<li>Training Sessions
<ul>
<li>New User Training</li>
<li>Software Carpentry workshops</li>
<li>Polls for content &amp; dates</li>
</ul>
</li>
<li>Competitions
<ul>
<li>Too late for SC16, look at putting an “Oklahoma team” together for SC17 or SC18</li>
<li>SC cluster competitions involve: 48 hours, need vendors</li>
<li>Tulsa Competition - April 2017
<ul>
<li>One day, need SD cards, programming involved - look at vendors</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>Adjournment - 6:50 p.m.</li>
</ol>
</description>
<pubDate>Mon, 10 Oct 2016 13:00:00 -0500</pubDate>
<link>/2016/10/10/GeneralMeeting/</link>
<guid isPermaLink="true">/2016/10/10/GeneralMeeting/</guid>
</item>
<item>
<title>First General Meeting</title>
<description><h2 id="cyberinfrastructure-association">Cyberinfrastructure Association</h2>
<h3 id="meeting-agenda">Meeting Agenda</h3>
<ol>
<li>
<p>Call to Order</p>
</li>
<li>Roll Call
<ul>
<li>Officers present: Matthew Whitlock (President), Brandon White (Treasurer), Cameron Mehmken (Membership Chair)</li>
<li>Total Present: 10</li>
<li>Slack sign up:</li>
</ul>
</li>
<li>Open Issues:
<ul>
<li>Election of Hardware and Software team leaders</li>
<li>Meeting frequency - team leaders will coordinate meetings outside of general meeting times</li>
<li>Elections on Slack? Or at the meetings?</li>
<li>Orange Pi alternative for hardware - Brandon composed a detailed spec sheet comparing a few board options</li>
<li>Virtual machine for software - could look at setting up a training session to get experience with virtual machines</li>
</ul>
</li>
<li>New Business
<ol>
<li>HPC Training Session
<ul>
<li>Goals and dates</li>
<li>HPCC New User Training Session - November 11 at 4 p.m. in MSCS 514 - sign up on Slack</li>
</ul>
</li>
<li>Cluster competitions
<ul>
<li><a href="https://engineering.utulsa.edu/academics/computer-science/oklahoma-high-performance-computing-competition/">Tulsa HPC competition</a> - probably the easiest one to compete in, location &amp; requirements</li>
<li>SC17 - here is information about <a href="http://sc16.supercomputing.org/studentssc/student-cluster-competition/">SC16’s competition</a> and <a href="http://sc16.supercomputing.org/studentssc/student-cluster-competition/team-proposal-guidelines/">team guidelines</a> - probably won’t be ready for SC17, but good to keep in mind and maybe use as motivation to start preparing for SC18</li>
</ul>
</li>
<li>Call for further topics - Discussion
<ul>
<li>None</li>
</ul>
</li>
</ol>
</li>
<li>Adjournment</li>
</ol>
</description>
<pubDate>Thu, 29 Sep 2016 13:00:00 -0500</pubDate>
<link>/2016/09/29/GeneralMeeting/</link>
<guid isPermaLink="true">/2016/09/29/GeneralMeeting/</guid>
</item>
<item>
<title>First General Meeting</title>
<description><h2 id="cyberinfrastructure-association">Cyberinfrastructure Association</h2>
<h3 id="meeting-agenda">Meeting Agenda</h3>
<ol>
<li>
<p>Call to Order</p>
</li>
<li>Roll Call
<ul>
<li>Officers present: Matthew Whitlock (President), Brandon White (Treasurer), Cameron Mehmken (Membership Chair)</li>
<li>Total Present: 12</li>
</ul>
</li>
<li>Open Issues:
<ol>
<li>Current Communication and services - Discussion
<ul>
<li>Sign up for slack to recieve up-to-date information on club meetings, etc.</li>
<li>Email with be used sparingly</li>
</ul>
</li>
<li>Membership Fees - Yea or Nay
<ul>
<li>Vote was ‘all in favor’ or $5 annual membership fee</li>
<li>Special Fun Distribution - Yea or Nay
<ul>
<li>Vote was ‘all in favor’ to earmark the membership fees to be used for membership discounts. Alternative uses require a supermajority vote.</li>
</ul>
</li>
</ul>
</li>
<li>Club funds - Discussion
<ul>
<li>AFAP at the end of the fall semester - have a plan to present to SGA</li>
<li>College Councils are good funding sources but usually stipulations (A&amp;S, CEAT, etc.)</li>
<li>Also think of offices with a common/similar mission who could provide cosponsorship - again, usually with stipulations</li>
<li>Corporate sponsorship for special projects (Like building the cluster?)</li>
</ul>
</li>
<li>Club goals for the year - Discussion
<ul>
<li>Main foal this year: to provide educational and skil-building opportinuties for CIA members - building the cluster, attending conferences, competitions, workshops, etc.</li>
</ul>
</li>
<li>Attendance requirements - Yea or Nay
<ul>
<li>Those in attendance feel the $5 membership is probably enough incentive to keep members involved, but encourage Slack communication among regular members</li>
</ul>
</li>
</ol>
</li>
<li>New Business
<ol>
<li>New Cluster Computer - Discussion
<ul>
<li>Members will contribute ideas for cluster components, ideas, etc. over the next month before meeting in the Tiny Titan Slack channel</li>
</ul>
</li>
<li>Creation of “Teams” - Yea or Nay
<ul>
<li>All in attendance agreed project teams were a good idea, but suggested that it’s important to make sure the teams stay connected and don’t get siloed</li>
</ul>
</li>
<li>Call for further topics - Discussion
<ul>
<li>Association of Computing Machinery - Meeting was at 5:30 that day
<ul>
<li>The “unofficial” computer science club</li>
</ul>
</li>
<li>2016 OK-LSAMP Research Symposium - Sept. 24</li>
</ul>
</li>
</ol>
</li>
<li>Adjournment</li>
</ol>
</description>
<pubDate>Wed, 31 Aug 2016 13:00:00 -0500</pubDate>
<link>/2016/08/31/GeneralMeeting/</link>
<guid isPermaLink="true">/2016/08/31/GeneralMeeting/</guid>
</item>
</channel>
</rss>