-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathabout.html
121 lines (107 loc) · 4.55 KB
/
about.html
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
---
layout: default
title: "About Me"
---
<!-- You can edit this whole page, remove it, or use it as basis for any non-post pages you have. -->
<section class="content">
<h1>About Me:</h1>
<h2>Madicken Munk</h2>
<section class="copy">
<p></p>
<p></p>
<p></p>
<b>Who I am: </b>
</p>
<p>
This is a weekly meeting for sharing skills and best practices for
scientific computation. Based on The Hacker Within Scientific Computing
Group from the University of Wisconsin Madison, a small group of nuclear
engineers at UC Berkeley had a couple such meetings in Fall 2013. In
spring semester of 2014, this grew into a more structured set of skill
sharing sessions for scientific software development (testing, data
management, version control, literate programming etc. ) The goal is to
learn cool skills and incorporate these practices into our workflows. This
meeting would be a great venue for introducing new libraries, showing off
useful features of a neutronics code you're using, or bringing up a
computational problem you're having.
</p>
<p>
<p></p>
<p></p>
<p></p>
<p></p>
<b>What I do for work: </b>
</p>
<p>
Room 190, Doe Library, The University of California - Berkeley
</p>
<p></p>
<p></p>
<p></p>
<p></p>
<p>
<b>What I do for fun:</b>
</p>
<p>
Anyone interested in software development best practices is welcome to
come to our meetings. Note that the first hour has a particular emphasis on
computational nuclear engineering and neutronics analysis best practices.
The second hour of the meeting, however, will be domain-inspecific!
</p>
<p></p>
<p></p>
<p></p>
<p></p>
<p>
<b>Contact Me</b>
</p>
<p>
Wednesdays at 3:30pm. The meeting should last about two hours. See the
<a href="http://thehackerwithin.github.io/berkeley">blog</a> or the
<a href="http://bit.ly/1cqFKuh">calendar</a> for the topic for this week.
To keep up with meetings, you may want to
<a
href="https://calmail.berkeley.edu/manage/list/listinfo/[email protected]">sign
up for the listhost</a>.
</p>
<p>
<b>How:</b>
</p>
<p>
Participating is really easy.
<li>At <b>3:30pm</b>, there is a short tutorial/discussion of some neutronics
topic.</li>
<li>Next, at <b>4:30pm</b>, there is a tutorial/discussion about a purely
computational topic. (feel free to only join for this part).</li>
<li>Finally, there will be a time for a couple of Lightning Talks, which
are 5-10 minute blasts of information about a particular topic or
question of interest to the group.</li>
To volunteer to give either of these talks,
just let the listhost know by email at <a
href="mailto:[email protected]">[email protected]</a>.
<b>Note</b> that the lightning talk time is a good way to bring a
question to the group. If you have a bug you need help with, here's the
place to ask many ears about it at once.
</p>
<p>
<b>Why: </b>
</p>
<p>
The tenets of scientific endeavor (e.g., data control, reproducibility,
comprehensive documentation, and peer review) suffer in projects that fail
to make use of current development tools such as unit testing, version
control, automated documentation, and others.</p>
<p>
To avoid these pitfalls, this weekly meeting exists for sharing skills and best practices for
computational scientific applications. This group is modeled after The
Hacker Within, which began as a student organization at the University of Wisconsin-Madison and
is now reborn as a collection of such chapters around the world. Each of
the chapters convenes a community of scientists, at all levels of their
education and training, to share their knowledge and best practices in
using computing to accomplish their work.</p>
<p>
<a href="http://twitter.com/share" class="twitter-share-button" data-count="none" data-via="{{ site.twitter }}">Tweet</a>
<a href="http://twitter.com/{{ site.twitter }}" class="twitter-follow-button" data-show-count="false">Follow @{{ site.twitter }}</a>
<script src="http://platform.twitter.com/widgets.js" type="text/javascript"></script>
</section>
</section>