-
Notifications
You must be signed in to change notification settings - Fork 8
Expand file tree
/
Copy pathexpectations.html
More file actions
597 lines (529 loc) · 22.6 KB
/
Copy pathexpectations.html
File metadata and controls
597 lines (529 loc) · 22.6 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
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
<title>Lab Expectations</title>
<script src="site_libs/header-attrs-2.30/header-attrs.js"></script>
<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
<style>h1 {font-size: 34px;}
h1.title {font-size: 38px;}
h2 {font-size: 30px;}
h3 {font-size: 24px;}
h4 {font-size: 18px;}
h5 {font-size: 16px;}
h6 {font-size: 12px;}
code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
pre:not([class]) { background-color: white }</style>
<script src="site_libs/navigation-1.1/tabsets.js"></script>
<link rel="alternate" type="application/rss+xml" title="POP:CORN Journal Club" href="https://rilab.github.io/feed.xml">
<script src="site.js" defer></script>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-5300959-3', 'auto');
ga('send', 'pageview');
</script>
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
</style>
<link rel="stylesheet" href="site.css" type="text/css" />
<style type = "text/css">
.main-container {
max-width: 940px;
margin-left: auto;
margin-right: auto;
}
img {
max-width:100%;
}
.tabbed-pane {
padding-top: 12px;
}
.html-widget {
margin-bottom: 20px;
}
button.code-folding-btn:focus {
outline: none;
}
summary {
display: list-item;
}
details > summary > p:only-child {
display: inline;
}
pre code {
padding: 0;
}
</style>
<style type="text/css">
.dropdown-submenu {
position: relative;
}
.dropdown-submenu>.dropdown-menu {
top: 0;
left: 100%;
margin-top: -6px;
margin-left: -1px;
border-radius: 0 6px 6px 6px;
}
.dropdown-submenu:hover>.dropdown-menu {
display: block;
}
.dropdown-submenu>a:after {
display: block;
content: " ";
float: right;
width: 0;
height: 0;
border-color: transparent;
border-style: solid;
border-width: 5px 0 5px 5px;
border-left-color: #cccccc;
margin-top: 5px;
margin-right: -10px;
}
.dropdown-submenu:hover>a:after {
border-left-color: #adb5bd;
}
.dropdown-submenu.pull-left {
float: none;
}
.dropdown-submenu.pull-left>.dropdown-menu {
left: -100%;
margin-left: 10px;
border-radius: 6px 0 6px 6px;
}
</style>
<script type="text/javascript">
// manage active state of menu based on current page
$(document).ready(function () {
// active menu anchor
href = window.location.pathname
href = href.substr(href.lastIndexOf('/') + 1)
if (href === "")
href = "index.html";
var menuAnchor = $('a[href="' + href + '"]');
// mark the anchor link active (and if it's in a dropdown, also mark that active)
var dropdown = menuAnchor.closest('li.dropdown');
if (window.bootstrap) { // Bootstrap 4+
menuAnchor.addClass('active');
dropdown.find('> .dropdown-toggle').addClass('active');
} else { // Bootstrap 3
menuAnchor.parent().addClass('active');
dropdown.addClass('active');
}
// Navbar adjustments
var navHeight = $(".navbar").first().height() + 15;
var style = document.createElement('style');
var pt = "padding-top: " + navHeight + "px; ";
var mt = "margin-top: -" + navHeight + "px; ";
var css = "";
// offset scroll position for anchor links (for fixed navbar)
for (var i = 1; i <= 6; i++) {
css += ".section h" + i + "{ " + pt + mt + "}\n";
}
style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
document.head.appendChild(style);
});
</script>
<!-- tabsets -->
<style type="text/css">
.tabset-dropdown > .nav-tabs {
display: inline-table;
max-height: 500px;
min-height: 44px;
overflow-y: auto;
border: 1px solid #ddd;
border-radius: 4px;
}
.tabset-dropdown > .nav-tabs > li.active:before, .tabset-dropdown > .nav-tabs.nav-tabs-open:before {
content: "\e259";
font-family: 'Glyphicons Halflings';
display: inline-block;
padding: 10px;
border-right: 1px solid #ddd;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
content: "\e258";
font-family: 'Glyphicons Halflings';
border: none;
}
.tabset-dropdown > .nav-tabs > li.active {
display: block;
}
.tabset-dropdown > .nav-tabs > li > a,
.tabset-dropdown > .nav-tabs > li > a:focus,
.tabset-dropdown > .nav-tabs > li > a:hover {
border: none;
display: inline-block;
border-radius: 4px;
background-color: transparent;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
display: block;
float: none;
}
.tabset-dropdown > .nav-tabs > li {
display: none;
}
</style>
<!-- code folding -->
</head>
<body>
<div class="container-fluid main-container">
<div class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html">Ross-Ibarra Lab</a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li>
<a href="index.html">Home</a>
</li>
<li>
<a href="people.html">People</a>
</li>
<li>
<a href="research.html">Research</a>
</li>
<li>
<a href="pubs.html">Publications</a>
</li>
<li>
<a href="software.html">Software</a>
</li>
<li>
<a href="https://github.com/RILAB/lab-docs">Lab Docs</a>
</li>
<li>
<a href="POPCORN.html">POP:CORN</a>
</li>
<li>
<a href="news.html">News</a>
</li>
</ul>
<ul class="nav navbar-nav navbar-right">
</ul>
</div><!--/.nav-collapse -->
</div><!--/.container -->
</div><!--/.navbar -->
<div id="header">
<h1 class="title toc-ignore">Lab Expectations</h1>
</div>
<p>I view my relationship with students and postdocs as a partnership. My job is to ensure people in the lab get the training and opportunities they need to advance in their chosen careers, whether in academia, industry, teaching, or other options. Below you can find information on the lab philosophy and expectations of lab members. Text and ideas in places borrow heavily from <a href="http://www.rrlab.org/expectations.html">Rubén Rellán-Álvarez</a>.</p>
<div id="general-rules" class="section level2">
<h2>General Rules</h2>
<div id="safety-first" class="section level3">
<h3>Safety first</h3>
<p>Your health and safety are more important than your research. This includes adhering to lab safety codes, as well as maintaining your physical and mental health. Never work in the lab if you are feeling sick, under medication that might affect your ability to work normally and definitely not under the effects of any kind of drugs. Avoid working in the lab by yourself doing potentially dangerous activities, and please be aware of UC Davis resources and training on <a href="http://safetyservices.ucdavis.edu/categories/laboratory-safety">lab safety</a>.</p>
</div>
<div id="respect" class="section level3">
<h3>Respect</h3>
<p>I expect lab members to contribute to a productive and friendly environment conducive to learning and research. This includes treating your colleagues with respect, listening to others’ viewpoints and ideas, and ensuring the lab is a place where everybody feels welcome and appreciated. Racist, sexist, or other inappropriate comments or behavior will not be tolerated under any circumstance. The university provides a number of <a href="http://studentexpression.ucdavis.edu/get-support/index.html">resources</a> (confidential and otherwise) to report or discuss any such activity you feel is inappropriate.</p>
</div>
<div id="expectations-for-all-members" class="section level3">
<h3>Expectations (for all members)</h3>
<div id="work-hours" class="section level4">
<h4>Work hours</h4>
<p>We are lucky enough to work in an area where flexible working hours are the norm. In order to be able to interact with the rest of the persons in the lab, we generally expect lab members to be present the majority of normal business hours (9-5pm) during the work week, since this is when most academic activities occur. There may be times when your project requires work late at night or on the weekends, but you are <em>not</em> expected to regularly work more than a normal 40-hour work week. It is important that you take time off for personal life, vacations, etc. I do ask, however, that you notify me if you will be absent for ≥1 day, and let me know in advance of any extended leave.</p>
</div>
<div id="seminars-journal-clubs-and-other-lab-and-institutional-activities" class="section level4">
<h4>Seminars, journal clubs and other lab and institutional activities</h4>
<p>Attendance to regular weekly lab meetings is expected of all lab members. Participation in weekly lab coffee, Zeavolution and other regular meetings, and <a href="jclub.html">journal club</a> is encouraged but not required. Note that if you are funded on one of the lab’s current grants, you are expected to attend those meetings as well. There are a number of seminars (Plant Biology, Genetics, Population Biology, Ecology & Evolution, Plant Sciences) each week, and these are usually posted in the office. You are strongly encouraged to regularly go to one or more each week.</p>
</div>
<div id="conferences" class="section level4">
<h4>Conferences</h4>
<p>Everyone is encouraged to attend at least one conference a year. Members of the lab regularly attend such meetings as the maize meeting, SMBE, Evolution, and ESA. The department and university offer travel funding for graduate students and postdocs, and you should apply for external sources of funding to help cover travel expenses. Whenever possible, I will help fund attendance at one conference per year for each member of the lab on the condition that you are presenting a poster or talk at the meeting. Please provide ample time before the deadline for reviewing abstracts and posters or practicing talks.</p>
</div>
<div id="authorship" class="section level4">
<h4>Authorship</h4>
<p>We follow the <a href="http://www.icmje.org/recommendations/browse/roles-and-responsibilities/defining-the-role-of-authors-and-contributors.html">ICJME rules for authorship rules</a>:<br />
1. Substantial contributions to the conception or design of the work; or the acquisition, analysis, or interpretation of data for the work; AND<br />
2. Drafting the work or revising it critically for important intellectual content; AND<br />
3. Final approval of the version to be published; AND<br />
4. Agreement to be accountable for all aspects of the work in ensuring that questions related to the accuracy or integrity of any part of the work are appropriately investigated and resolved. Projects evolve over time and authorship inclusion and author order will be re-evaluated accordingly.</p>
</div>
<div id="open-science" class="section level4">
<h4>Open Science</h4>
<p>We feel strongly that open science is important. We write papers on github or <a href="overleaf.com">overleaf</a>, often in public repos. We publish preprints as soon as a manuscript is ready for submission. We publish our data as soon as we can, and I am pushing to start doing so as separate data papers. We document our work – with github, R markdown, readme files, etc. – so it is intelligible and reusable in the future. I expect members of the lab to practice open science.</p>
</div>
</div>
</div>
<div id="specific-rules-for-the-different-members-of-the-lab" class="section level2">
<h2>Specific rules for the different members of the lab</h2>
<div id="postdocs-and-senior-phd-students" class="section level3">
<h3>Postdocs and senior PhD students</h3>
<div id="my-responsibilities-to-postdocs-and-senior-phd-students" class="section level4">
<h4>My responsibilities to postdocs and senior PhD students:</h4>
<ul>
<li>Assist with identifying and writing postdoctoral fellowships.<br />
</li>
<li>Develop project ideas, including independent projects that can be taken with the postdoc.</li>
<li>Interpret results.</li>
<li>Proof-read manuscripts.</li>
<li>Discuss future career goals (e.g., do you want to teach, go into academia, industry, continue in research?), and plan ways to facilitate these goals.</li>
<li>Meet weekly to discuss progress & pitfalls.</li>
</ul>
</div>
<div id="expectations-of-postdocs-and-senior-phd-students" class="section level4">
<h4>Expectations of postdocs and senior PhD students:</h4>
<ul>
<li>Prepare for our regular progress/pitfalls meetings and a follow up email of progress and goals.<br />
</li>
<li>Write and submit manuscripts. I strongly encourage collaboration, and a quick glance at our <a href="pubs.html">publications</a> should show that this generally works well. On average I expect your time as a postdoc in the lab to generate ~2 papers per year (first or co-authored), and in general this expectation seems to be not unreasonable.</li>
<li>Proof-read manuscripts from other lab members.<br />
</li>
<li>Apply for external funding (either individual postdoc fellowships or contributing to larger lab grant writing).<br />
</li>
<li>Maintain a set of lab notes, including directories of data, annotated codes & versions, detailed methods. These need to sufficient to reproduce results without additional instructions. A good working example can be found <a href="https://github.com/timbeissinger/Maize-Teo-Scripts">here</a>.</li>
<li>Participate in general lab responsibilities (servers, maintain common areas, taking turns hosting visitors). Participate in talk rehearsals of your colleagues.</li>
<li>Optional, but encouraged: Mentor at least one undergraduate student.</li>
</ul>
</div>
</div>
<div id="master-and-junior-phd-students" class="section level3">
<h3>Master and junior PhD students</h3>
<div id="my-responsibilities-to-master-and-junior-phd-students" class="section level4">
<h4>My responsibilities to Master and junior PhD students:</h4>
<ul>
<li>Develop project ideas.<br />
</li>
<li>Interpret results.<br />
</li>
<li>Proof-read and contribute to writing of thesis, abstracts and manuscripts.<br />
</li>
<li>Discuss future career goals (e.g., do you want to teach, go into academia, continue in research?), and plan ways to facilitate these goals.<br />
</li>
<li>Meet weekly to discuss progress and pitfalls.</li>
</ul>
</div>
<div id="expectations-of-master-and-junior-phd-students" class="section level4">
<h4>Expectations of Master and junior PhD students:</h4>
<ul>
<li>Prepare for our regular progress/pitfalls meetings and a follow up email of progress and goals.<br />
</li>
<li>Write and submit manuscripts. On average, I expect most students to produce three publications over the course of their PhD, including at least one first-author paper.</li>
<li>Maintain a set of lab notes, including directories of data, annotated codes & versions, detailed methods. These need to sufficient to reproduce results without additional instructions. A good working example can be found <a href="https://github.com/timbeissinger/Maize-Teo-Scripts">here</a>.</li>
<li>Write thesis in due time.<br />
</li>
<li>Proof-read manuscripts from other lab members. Participate in talk rehearsals of your colleagues.<br />
</li>
<li>Participate in general lab responsibilities (servers, maintain common areas, taking turns hosting visitors, communal sampling and field work etc). Participate in talk rehearsals of your colleagues.<br />
</li>
<li>Present multiple research talks/posters at conferences over the course of your time in the lab. You are encouraged to do so annually, but this isn’t always possible.</li>
<li>Optional, but encouraged: Mentor at least one undergraduate student.</li>
</ul>
</div>
</div>
</div>
<div id="ai-usage-policy" class="section level2">
<h2>AI Usage Policy</h2>
<p>This section outlines RILab guidelines for using AI tools in research, writing, and coding. The expectations differ by experience level: what is appropriate for an expert may not be appropriate for a beginner, because part of training is learning to do the work yourself first. Your relevant experience level will likely differ for different tasks, so please use your best judgment and ask for clarification if you are unsure. The goal is to ensure that you are learning the skills you need to be a successful researcher, while also using AI tools responsibly.</p>
<div id="general-best-practices" class="section level3">
<h3>General Best Practices</h3>
<p>These principles apply to everyone in the lab, regardless of experience level:</p>
<ul>
<li><strong>Always check</strong> AI output before relying on it.</li>
<li><strong>Ask for sources</strong> and verify them.</li>
<li><strong>Accountability</strong> — independently validate what the AI produces.</li>
<li><strong>Ask questions about assumptions</strong> the AI (or you) may be making.</li>
<li><strong>Ask before sharing others’ writing and code</strong> with AI tools.</li>
<li><strong>Feedback from a human</strong> will almost always be more helpful than AI.</li>
<li><strong>When in doubt, ask someone!</strong></li>
<li><strong>Should you learn it?</strong> If knowing this is important to your development, do it yourself. If not, you can use AI.</li>
<li><strong>Generally:</strong> Could you do it without AI? If not, do not use it until you can.</li>
<li><strong>Ask for point-by-point</strong> review of text, rather than have AI rewrite anything.</li>
<li><strong>Ask to see code</strong> rather than blindly accepting it.</li>
<li><strong>Reading, interpreting facts, and synthesizing content are core scholarly skills you are expected to develop and own.</strong></li>
<li><strong>AI should never</strong> outline a draft or rewrite your writing — the thinking embedded in drafting and writing is yours to do.</li>
</ul>
</div>
<div id="usage-guidelines-by-experience-level" class="section level3">
<h3>Usage Guidelines by Experience Level</h3>
<p>The tables below specify what is appropriate at each level across three task categories — writing, research, and coding & analysis — under three permission tiers:</p>
<ul>
<li><strong>Never okay</strong> — do not use AI for these tasks.</li>
<li><strong>Case-by-case</strong> — acceptable in some situations; use judgment and check in if unsure.</li>
<li><strong>Always okay</strong> — AI use is fine for these tasks.</li>
</ul>
<div id="beginner" class="section level4">
<h4>Beginner</h4>
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th>Category</th>
<th>Never okay</th>
<th>Case-by-case</th>
<th>Always okay</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>Writing</strong></td>
<td>Outline a draft; rewrite anything</td>
<td>—</td>
<td>Typos and spelling</td>
</tr>
<tr class="even">
<td><strong>Research</strong></td>
<td>Read; interpret facts; synthesize content</td>
<td>Find articles</td>
<td>Basic facts (with a source)</td>
</tr>
<tr class="odd">
<td><strong>Coding & analysis</strong></td>
<td>Basic syntax; writing functions; writing a whole pipeline</td>
<td>Code review (checking for errors)</td>
<td>Explaining code</td>
</tr>
</tbody>
</table>
</div>
<div id="intermediate" class="section level4">
<h4>Intermediate</h4>
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th>Category</th>
<th>Never okay</th>
<th>Case-by-case</th>
<th>Always okay</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>Writing</strong></td>
<td>Outline a draft; rewrite anything</td>
<td>Editing and feedback</td>
<td>Typos and spelling</td>
</tr>
<tr class="even">
<td><strong>Research</strong></td>
<td>Read; interpret facts; synthesize content</td>
<td>—</td>
<td>Find articles; basic facts (with a source)</td>
</tr>
<tr class="odd">
<td><strong>Coding & analysis</strong></td>
<td>Writing a whole pipeline</td>
<td>Writing functions; code review</td>
<td>Basic syntax; explaining code</td>
</tr>
</tbody>
</table>
</div>
<div id="expert" class="section level4">
<h4>Expert</h4>
<table>
<colgroup>
<col width="25%" />
<col width="25%" />
<col width="25%" />
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th>Category</th>
<th>Never okay</th>
<th>Case-by-case</th>
<th>Always okay</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>Writing</strong></td>
<td>Outline a draft; rewrite anything</td>
<td>Editing and feedback</td>
<td>Typos and spelling</td>
</tr>
<tr class="even">
<td><strong>Research</strong></td>
<td>—</td>
<td>Read; interpret facts; synthesize content</td>
<td>Find articles; basic facts (with a source)</td>
</tr>
<tr class="odd">
<td><strong>Coding & analysis</strong></td>
<td>—</td>
<td>Writing a pipeline; directly analyze data</td>
<td>Basic syntax; writing functions; code review; explaining code</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="site-footer">
<strong>Contact</strong><br>
Jeffrey Ross-Ibarra<br>
530-752-4565<br>
Dept. of Evolution and Ecology<br>
University of California<br>
Storer Hall, One Shields Ave<br>
Davis, CA 95616
</div>
</div>
<script>
// add bootstrap table styles to pandoc tables
function bootstrapStylePandocTables() {
$('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
}
$(document).ready(function () {
bootstrapStylePandocTables();
});
</script>
<!-- tabsets -->
<script>
$(document).ready(function () {
window.buildTabsets("TOC");
});
$(document).ready(function () {
$('.tabset-dropdown > .nav-tabs > li').click(function () {
$(this).parent().toggleClass('nav-tabs-open');
});
});
</script>
<!-- code folding -->
<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
(function () {
var script = document.createElement("script");
script.type = "text/javascript";
script.src = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
document.getElementsByTagName("head")[0].appendChild(script);
})();
</script>
</body>
</html>