-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.Rmd
1549 lines (1025 loc) · 51.9 KB
/
index.Rmd
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
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
title: "R for better science in less time"
subtitle:
author: 'Julia Stewart Lowndes, PhD'
role: 'Marine Data Scientist & Mozilla Fellow'
institute: 'National Center for Ecological Analysis & Synthesis<br>University of California at Santa Barbara, USA'
date: "useR! 2019 Keynote<br>Toulouse, France"
output:
xaringan::moon_reader:
seal: false
chakra: libs/remark-latest.js # with @bjungbogati tidyverse dev toulouse: need to save this file to knit offline!
lib_dir: libs
nature:
slideNumberFormat: "" # if you want to disable
highlightStyle: github
highlightLines: true
countIncrementalSlides: false
ratio: "16:10" # https://github.com/apreshill/talks/blob/master/sdss-blogdown/index.Rmd#L16, http://user2019.r-project.org/information_for_presenters/
output:
css: ["default", "css/my-fonts.css", "css/my-theme.css"] #https://github.com/apreshill/talks/blob/master/uo-sad-plot-better/index.Rmd#L7
includes:
in_header: header.html
# http://arm.rbind.io/slides/xaringan.html
# https://github.com/rstudio-education/arm-workshop-rsc2019/blob/master/static/slides/xaringan.Rmd
---
```{r setup, include=FALSE}
options(htmltools.dir.version = FALSE, warning=FALSE, message=FALSE, verbose = FALSE)
knitr::opts_chunk$set(echo = FALSE, message=FALSE, warning=FALSE)
library(xaringan)
library(fontawesome)
```
class: title-slide, right, bottom
background-image: url(img/horst-starwars-rey.png)
background-size: contain
background-position: bottom left
# `r rmarkdown::metadata$title`
### `r rmarkdown::metadata$author`
### `r rmarkdown::metadata$role`
### `r rmarkdown::metadata$institute`
[`r icon::fa("twitter")` @juliesquid](https://twitter.com/juliesquid)
[`r icon::fa("paper-plane")` [email protected]](mailto:[email protected])
[`r icon::fa("desktop")` jules32.github.io/useR-2019-keynote](http://jules32.github.io/useR-2019-keynote)
<img src="img/mozilla.png" alt="mozilla" style="float:right;width:154px;"/>
<img src="img/nceas.png" alt="nceas" style="float:right;width:150px;"/>
???
Well thank you so much, I am so excited to be here with all of you and I want to thank the organizers for this invitation.
I am a marine scientist and R as a language and as a community has been game-changing for my science, and my life.
So much so that over the past six years I have been moving away from doing my own research so I can pay forward what I've learned and focus on enabling other scientists to better science in less time, together.
Throughout this I've learned several lessons, and I want to share them up front:
---
# Lessons learned
<br>
### Open data science is a mindset
### Teamwork starts with openness
### Harness the power of welcome
???
The 3 lessons are Open data science is a mindset, Teamwork starts with openness, and Harness the power of welcome.
I'm going to spend the whole talk building out these lessons.
But first I wanted to tell a bit about me and the main experiences that have driven these lessons.
I am often asked why a marine scientist would use R, so I want to make sure you leave here knowing that marine scientists, as well as environmental scientist more broadly, work with data every single day to do our science, and it is critical that we are supported to work with data responsibly.
So let me start off when I was a graduate student in a marine research group, which we also call laboratories in the US.
---
## @juliesquid
```{r sq-tag2, out.width = '40%', fig.align='center'}
knitr::include_graphics("img/*JulieReleaseAugerIMG_9311-crop.png")
# *JulieReleaseAugerIMG_9397.jpg # release to water
# *IMG_9268.JPG # measure
```
.footnote[
photo: Greg Auger
]
???
I am actually a squid ecologist, which is why many of you know me as juliesquid.
That is me on the right, holding a squid that can be nearly as big as I am.
We caught it and I am releasing it alive back into the ocean with a little electronic tag on it. The tag turns this squid little oceanographer, because it will collect data about it environment as it swims through the ocean. i collected data every second, which means I could actually see the squid breathe, since its breathing and movement are coupled through jet propulsion.
My whole PhD research group focused on squid. We were interested because squid have huge impact on ecosystems since they eat a lot and grow quickly and they also have huge impact on economies because globally there is such high consumption of calamari. In our lab some focused on ecology like me, others on locomotion, camouflage, or early life development.
---
<br>
.pull-left[
```{r fieldwork, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/sq-ctd-fieldwork.JPG")
```
]
.pull-right[
<br>
<br>
```{r fieldwork2, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/DannaJulieAshleyNOAA.JPG")
```
]
.footnote[
web: [Gilly Lab](https://gillylab.stanford.edu/)
]
???
Our research required a lot of teamwork, both at sea and in the laboratory.
We were a typical research group because we worked like a team about our scientific questions.
We were also a typical research group because we didn't act like a team when it came to data. Analyzing data was something that was left to each of us to figure out as individuals.
In in all my education I had never learned computing or how to work responsibly with data. So for me it was a super demoralizing experience to get the tag back and actually hold data in my hand but not be able to analyze it.
transition: It felt like this.
---
```{r luke}
```
class: center, middle
background-image: url(img/horst-starwars-luke.png)
background-size: contain
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst)
]
???
This is Luke Skywalker after he crashed his plane in the swamp on Degobah.
He cannot solve the the challenge in front of him with the skillsets he has.
He is demoralized and alone. And if you imagine him attempting to use whatever pulleys and ropes he might have with him, you know it wouldn't be pretty, it wouldn't be reproducible, and it probably wouldn't get him where he needs to be on time.
transition: but luckily what happens next is that he meets Yoda
---
class: top, center
```{r yoda, out.width = '88%'}
knitr::include_graphics("img/horst-starwars-yoda.png")
```
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst)
]
???
Yoda uses the Force to solve Luke's problem in a way Luke never imagined was possible.
This is going to open up Luke's whole world because he can learn from Yoda and not only solve his current but it will broaden his mind to what is possible in the future.
transition: But Luke didn't go on to defeat the Empire himself, he had a whole community.
---
```{r hands}
```
class: center, middle
background-image: url(img/horst-starwars-hands.png)
background-size: contain
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst)
]
???
And this community is powerful because of the diversity of backgrounds and expertise, and although not everyone is a Jedi, everyone contributes in really critical ways.
transition: So just to recap,
---
```{r rey}
```
class: center, middle
background-image: url(img/horst-starwars-rey.png)
background-size: contain
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst)
]
???
R is the Force that enables us as scientists to do better science in less time.
It empowers us to get our own data out of the swamp.
It empowers us and build off of our confidence and experiences and broaden the scope of scientific challenges that we can tackle, which for environmental scientists, includes food security, disease transmission, and climate change.
For me, I didn't fully feel the power of R until I finished graduate school and joined a research group where I am today, where we learned to work with data as a team.
---
```{r OHI hex, out.width = '55%', fig.align='center'}
knitr::include_graphics("img/OHI-hex.png")
```
.footnote[
web: [ohi-science.org](http://ohi-science.org); [@OHIscience](https://twitter.com/OHIscience)
]
???
The Ocean Health Index is a scientific endeavor to quantify impacts and benefits of oceans around the world using the best publically available data.
It is being used by the United Nations and by 20 groups around the world.
There is a lot to it but what is relevant here is that we combine lots of data, we repeat our analyses every year, and we do it as a team.
But we are marine scientists, and we were never trained to work responsibly with data.
So we found out the hard way that our default approaches were not reproducible by even ourselves.
Getting through this involved quite a reckoning, but when we got through it, we knew we had a story to tell.
---
class: middle, center
```{r nature-bsilt, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/nature-screenshot-title.png")
```
.footnote[
source: [Lowndes *et al.* 2017](https://www.nature.com/articles/s41559-017-0160); web: [ohi-science.org/betterscienceinlesstime](http://ohi-science.org/betterscienceinlesstime/)
]
???
We found our path to better science in less time with open data science tools.
And by this I mean R and GitHub and friends.
transition: We shared how these tools enabled us to more reproducible science faster each year, as we illustrated in this figure
---
class: middle, center
```{r fig 1-whiteout, out.width = '80%'}
knitr::include_graphics("img/bsilt-fig1-nature-whiteout.jpg")
# lowndes-nature-figure1-slides2.png
# https://docs.google.com/drawings/d/1d25T1fD9irluhQhPvNHZSt3uUBXebxqV9hFabOLZUz4/edit
```
.footnote[
source: [Lowndes *et al.* 2017](https://www.nature.com/articles/s41559-017-0160)
]
???
Shown here as the circles get smaller and moving up the y axis. It also go easier for us to collaborate each year, along the x axis.
This let us focus on making improvements either on the data science side or the science side
---
class: middle, center
```{r fig 1, out.width = '80%'}
knitr::include_graphics("img/bsilt-fig1-nature.jpg")
# lowndes-nature-figure1-slides2.png
# https://docs.google.com/drawings/d/1d25T1fD9irluhQhPvNHZSt3uUBXebxqV9hFabOLZUz4/edit
```
.footnote[
source: [Lowndes *et al.* 2017](https://www.nature.com/articles/s41559-017-0160)
]
???
We couldn't overhaul everything all at once, but focused on different pieces incrementally each year.
We started off focused on R and RStudio, and then on using Git and GitHub, then on tidy data and then documentation and Rmd. And ever since we've focused on leading a training program to teach students how to maintain it.
Having all of this coding infrastructure in place is what enables those 20 independent groups I mentioned to study ocean health in the places they care about.
But just like Luke, we were able to do this because of community.
---
class: center, middle
```{r community-logos, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/ods-community-logos.png")
```
???
These communities in particular have been so transformative for our work.
So many of you in this room and listening around the world have welcomed us and supported us and enabled us.
And like I said, I've been paying it forward by teaching with the Carpentries and leading local communities —
---
# Eco-Data-Science & RLadies SB
```{r eds, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/eds-rladies-hex.png")
```
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst); twitter: [@ecodatasci](https://twitter.com/ecodatasci); [@RLadiesSB](https://twitter.com/RLadiesSB)
]
???
leading local study groups like Eco-Data-Science and RLadies chapters, and generally telling everybody how awesome R is.
This is how I got a fellowship with Mozilla.
---
class: center, middle
```{r moz, out.width = '100%'}
knitr::include_graphics("img/moz-fellow-announcement.png")
```
.footnote[
blog: [blog.mozilla.org](https://blog.mozilla.org/blog/2018/08/21/mozilla-announces-25-new-fellows-in-openness-science-and-tech-policy/)
]
???
Yes Moz is firefox, but also the internet for good.
Spent the last year developing a program with Mozilla and NCEAS, the ecology center where I am based.
---
```{r openscapes hex, out.width = '55%', fig.align='center'}
knitr::include_graphics("img/openscapes-hex.png")
```
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst);
web: [openscapes.org](https://openscapes.org); [@openscapes](https://twitter.com/openscapes)
]
???
The program is called Openscapes, and it is mentorship program for research groups.
Openscapes helps them establish and maintain shared practices around data and work as a team.
It is modeled after our experiences from the Ocean Health Index, which is one of the most visible examples of what open data science can look like in an environmental context.
---
<br>
```{r openscapes grassland, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/horst_openscapes_grassland_1500px-text.png")
```
<br>
.pull-left[
### Welcome and empower scientists as labs
]
.pull-right[
### Increase visibility and value by amplifying labs
]
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst);
web: [openscapes.org](https://openscapes.org)
]
???
welcome and empower scientists as research groups
increase visibility and valuee by amplifying labs and creating more examples of how powerful open data science can be for environmental science
---
<br>
```{r openscapes desert, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/horst_openscapes_desert_1500px.png")
```
.pull-left[
### Mentorship program for early career scientists & their labs
]
.pull-right[
### Normalize open data science in the lab & seed change beyond
]
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst);
web: [openscapes.org/champions](https://openscapes.org/champions)
]
???
Centered mentorship program for early career scientists & their labs
Normalize open data science in the lab & seed change beyond
---
```{r env-r4ds}
```
class: center, middle
background-image: url(img/horst-eco-r4ds.png)
background-size: contain
.footnote[
.left[
art: [@allison_horst](https://twitter.com/allison_horst);
updated from [Wickham & Grolemund](https://r4ds.had.co.nz/)
]
]
???
This is the vision I see for environmental science.
Where the elements that environmental scientsts are great at, like theory, and experimental design are streeamlined together by ODS, and help us communicate around environmental solutions.
I know this graphic looks familiar from R4DS, but notice that all of the data science components here are ringed by communities and support that our OHI team has found so critical to our success.
So this is the vision I'm working towards with Openscapes, and I am optimistic we can do this because the first cohort of Openscapes participants are well on their way after only 5 months.
---
```{r env-comm}
```
class: center, middle
background-image: url(img/horst-eco-r4ds-env-comm-only.png)
background-size: contain
.footnote[
art: [@allison_horst](https://twitter.com/allison_horst)
]
???
But right now environmental science looks like this. We rarely have formal training with coding or computing or data and so folks learn in pockets and are unsupported at broader institutional levels.
And often they are not supported even at level of the research group, which is already poised to work like a team.
Helping complete this picture drives my work now. I want to figure out how to best introduce open data science and teamwork to this picture.
I've found that scientists are often not aware of what tools are availabe. But that is just the first sliver of the challenge.
The real challenge is about mindset around open data science, and helping scientists feel included so that it can be part not only of their future, but of their present.
---
# Lessons learned
<br>
### Open data science is a mindset
### Teamwork starts with openness
### Harness the power of welcome
???
<water>
So the first is that open data science is a mindset.
---
class: center, middle
# Open data science is a mindset
### expect a better way • build confidence & willingness • reimagine science communication
???
<br>
This involves expecting there is a better way with data science,
Building confidence & willingness with open science,
and reimagining what is possible with the available tools.
---
class: middle, center
# Expect there is a better way
???
It can be really hard to expect that there is a better way to do something when you do not know what is possible and you don't see any examples within your own context.
It's like how Luke would have never expected the Force to have been a thing if he hadn't run into ObiWan and Yoda.
When I struggled with my squid data, I couldn't expect there was a better way because I thought my challenges with column renaming was a part of my squid research, not something separate like data wrangling.
So this mindset drained weeks of my time, because I didn't have the mindset or the vocabulary to articulate my struggles and ask for help.
transition: so when I talk about data science with Openscapes —
---
```{r data-science}
```
.whisper[Data science]
???
I make it clear that it is not just about big data, machine learning, and artifical intelligence, which is basically all you ever hear about in the news.
I think this narrow definition really excludes scientists, who then feel that data science tools are not meant for them.
transition: I like this definition:
---
```{r data-science}
```
.whisper[Data science is the discipline of turning raw data into understanding]
<br>
```{r data-science-r4ds, out.width = '90%', fig.align='center'}
knitr::include_graphics("img/r4ds_data-science.png")
```
.footnote[
source: [Wickham & Grolemund](https://r4ds.had.co.nz/)
]
???
This definition resonates with me because I can see myself included in it — and then with the graphic I can actually walk through the steps.
This clearly describes what many scientist like me I have been fumbling around trying to every time from scratch.
The idea of tidying your data first and then being streamlined with the tools you can use for science is amazing. Rather than accommodating around weird data.
transition So expecting there is a better way is a big part of a shifting mindset towards open data science. And along with it comes
---
class: middle, center
# Build confidence & willingness
???
Building confidence & willingness to engage in a completely different way to work.
Open science is a big part of this confidence and willingness to engage.
transition: but Open science has many different definitions and even more interpretations.
---
```{r open-science}
```
.whisper[Open science]
???
For many environmental scientists, open science can be a negative thing. It's seen as extra work and high risk on already overburdened scientists, particularly those who are early career.
And that is because it often also has a narrow definition of sharing your data and code at the end of your study, at the risk of people stealing your work and misconstuing your science.
In this narrow mindset it's not considered that open science could ever be a benefit to the scientist who pays such cost in terms of time and risk.
transition: So in Openscapes, we talk about open science with this definition:
---
```{r open-science}
```
.whisper[Open science is the concept of transparency at all stages of the research process, coupled with free and open access to data, code, and papers]
```{r spectrum, out.width = '90%', fig.align='center'}
knitr::include_graphics("img/spectrum-haha.png")
```
.footnote[
source: [Hampton et al. 2015](https://esajournals.onlinelibrary.wiley.com/doi/full/10.1890/ES14-00402.1)
]
???
I like this definition of open science
I teach that open science is a spectrum, with many entryways to engage
I like this too because it helps dispell the idea that you're either doing open science or you're not, but that you can always engage more as you are able.
In Openscapes we talk about how entryways can include sharing slides from a talk online.
We also practice working openly with their own teams, even if it is within a private repository, because it is practicing the tools and taking the first steps.
transition: and these 2 pieces really trigger you to reimagine what data science and open science can do for communication
---
class: center, middle
# Reimagine science communication
???
In environmental science, communication is something we really value.
We are very similar to the open source community like R and Moz in that all of our work is for the public good, and thus communication about it is critical
transition: But For a lot of people, science communication still largely occurs at the end of a study, when everything is complete.
---
.whisper[Communication tools]
???
And I think this mindset is rooted in the fact that for a long time, sharing your work was hard to do.
It involved a lot of bookkeeping and formatting and physically printing in many cases, and then distribution was also limited to mail, either phyical or electronic.
But the internet provides amazing channels to share our work not only at the end, but throughout all of the process. This is critical to establish trust and action for environmental solutions.
---
.whisper[Communication tools]
```{r ods-software, out.width = '65%', fig.align='center'}
knitr::include_graphics("img/screenshot-paur-talk-ods.png")
```
.footnote[
source: [OHI slides](https://docs.google.com/presentation/d/12m8dUpIOz16x1RlZWLtj9u5E9wMxtYuP0T_HxoDnyKw/edit?usp=sharing)
]
???
So these are the communication tools I use for open data science — it is a small suite, primarily based with R, RStudio, Git, and GitHub.
And keeping it so simple really streamlines how manageable it is to focus on science communication, because we use the exact same tools for analysis.
I may as well also say that I can be a big curmudgen about introducing extra software into my life and having to create new user accounts.
I remember in one NSSD episode, Roger Peng said that if he has to create a new user account, he's like 50% out. For me it's like 80%.
But anyways, these tools have reimagined what communication means, and I'll show you a few examples from the OHI.
<next go quickly>
---
exclude: TRUE
class: center, middle
```{r global-map, out.width = '100%'}
knitr::include_graphics("img/global_map_Index_2018_mol.png")
```
.footnote[
source: [ohi-science.org/ohi-global](http://ohi-science.org/ohi-global/)
]
???
We create ocean health index maps like these, in R, with scores reflecting how healthy oceans are for every coastal country around the world. and making these every year by modeling almost 100 data sets forces documentation and decision making to be part of science communication.
---
class: center, middle
```{r ohi-science-github, out.width = '100%'}
knitr::include_graphics("img/github-ohi-science.png")
```
.footnote[
web: [github.com/ohi-science](https://github.com/ohi-science)
]
???
We put all of our code online, pubically, in a GitHub organization for the OHI. This means that others can discover, access, and run our code, understanding what we've done and doing assessments of their own.
But GitHub repositories are not a friendly landing page for everyone. So —
---
class: center, middle
```{r ohi-science-homepage, out.width = '100%'}
knitr::include_graphics("img/ohi-science-homepage.png")
```
.footnote[
web (Jekyll): [ohi-science.org](http://ohi-science.org)
]
???
So we built a website that we can maintain ourselves. And here we can put addition information and tutorials and blogs.
---
class: center, middle
```{r rmd-global-web, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/web-rmd-global.png")
```
.footnote[
web (simple RMarkdown): [ohi-science.org/ohi-global](http://ohi-science.org/ohi-global)
]
???
We also can spin up lighter-weight websites that will render with the most recent information we have
This is not only useful for us, but for our colleagues leading their own assessments on their coastlines.
---
```{r ohi-esw, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/ohi-esw-web.png")
```
.footnote[
web (simple RMarkdown): [ohi-science.org/esw](http://ohi-science.org/esw)
]
???
Another way science communication has changed is that
---
class: center, middle
```{r toolbox-training, out.width = '80%'}
knitr::include_graphics("img/ohi-toolbox-training.png")
```
.footnote[
web: [ohi-science.org/toolbox-training](http://ohi-science.org/toolbox-training/)
]
???
We can create really nicely formatted guides and documentation also using these same tools.
---
<br>
```{r shiny-ne, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/jafflerbach-shiny-ne.png")
```
.footnote[
dashboard (Shiny): [@jafflerbach](https://twitter.com/jafflerbach), work in progress.
inspiration: [Imagine Boston](https://analytics.boston.gov/app/imagine-boston)
]
???
And when we are working closely with partners who are engaged with data analysis decisions, we have been able to create dashboards as well.
---
<br>
```{r openscapes-web, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/web-blogdown-openscapes.png")
```
.footnote[
web (blogdown): [openscapes.org](https://openscapes.org)
]
???
Additionally, these tools have been amazing for blogging and sharing Openscapes stories
---
<br>
```{r user-xaringan, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/user-keynote-titleslide.png")
```
.footnote[
slides (xaringan): [jules32.github.io/useR-2019-keynote](https://jules32.github.io/useR-2019-keynote)
]
???
And for fun, for creating talks at useR
transition:
---
```{r r4ds-env-reprise}
```
class: center, middle
background-image: url(img/horst-eco-r4ds.png)
background-size: contain
.footnote[
.left[
<br>
art: [@allison_horst](https://twitter.com/allison_horst);
updated from [Wickham & Grolemund](https://r4ds.had.co.nz/)
]
]
???
So open data science as a mindset is the framing that we start with in Openscapes.
But the way we actually start acting on all of this is through teamwork, which starts with openness.
---
class: center, middle
# Teamwork starts with openness
### working openly • vertical & horizontal leadership • community
???
--water
Teams to me mean rings of people you respect, innovate with, and can rely upon. It does not have to be limited to a certain deliverable, location, discipline or anything else really.
Teamwork is critical in science because no one it can do it all. And for the sake for innovation as well as for emotional well-being we need to shed the expectation that we should be able to. Instead, we need to value teamwork.
So I've categorized teamwork here but there are definitely a lot of blurred lines.
But actually one of the coolest things to me throughout everything I've learned is how teamwork and collaboration and leadership and community all intertwine when you work openly.
---
class: center, middle
# Working openly
???
Open data science streamlines working with data but also working with each other.
Shared workflows like tidyverse and GitHub mean that even when you aren't working on the same project or interest, you have the same skills and are equipped to help each other out.
As an OHI team, these tools let us co-develop things, share early drafts, and we can constantly giving feedback and iterating with each other.
transition: But working openly is something you have to feel safe doing.
---
# Ocean Health Index team
```{r team, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/ohi-team-2018b-crop.jpeg")
```
???
We as an OHI team have spent years building up trust with each other, and that makes us be able to do our best work.
This trust really centers on respect for each other and also kindness.
But on an individual level, we all have had to get comfortable with sharing things before they are perfect and being vulnerable to critique, which gets easier when you can assume the best intentions from anyone's feedback.
But this has resulted in a really positive team culture, where we are comfortable with trying new things & learning from failure, and we are comfortable asking for help.
---
# Ocean Health Index team
```{r team2, out.width = '90%', fig.align='center'}
knitr::include_graphics("img/ohi-team-2019-crop.jpg")
```
???
Another thing about our team is that we prioritize social time, obviously, since it is impossible to find a picture of our team that is not at happy hour.
But seriously, getting along well together builds resilience into our team and has helped avoid burnout. And it helps us us manage as people come and go into our group, as is common in science.
transition: one of the ways to start working on this as a team is to create safe spaces where you can deliberately talk about shared stuff.
And in Openscapes, that's what we do in our cohort calls.
---
# Openscapes Cohorts
```{r zoom, out.width = '70%', fig.align='center'}
knitr::include_graphics("img/Cohort1_zoom.png")
```
.footnote[
blog: [openscapes.org](https://www.openscapes.org/blog/2019/01/28/introducing-champions-program/)
]
???
This is the first cohort from Openscapes!
These are scientists from 7 labs, with the faculty or lecturers of each lab participating along with their lab members, who are graduate students, postdocs, technicians, lab managers, visiting faculty.
We all meet twice each month to discuss open data science concepts and to build community.
In our calls, I try to model the behavior I want to see, so that they can bring it to their labs. We start off every meeting with a Code of Conduct.
transition: I said that what I teach in Openscapes is modeled after OHI —
---
class: center, middle
```{r olx, out.width = '90%'}
knitr::include_graphics("img/moz-open-leaders.png")
```
.footnote[
web: [Mozilla Open Leaders](https://foundation.mozilla.org/en/opportunity/mozilla-open-leaders/) (Apply for OLX by August 1!)
]
???
But the whole program architecture is modeled after Mozilla Open Leaders.
Mozilla Science Lab and Open Leaders & Events team has run this program 7 times, with up to 6 cohorts concurrently, so they have really dialed in the program architecture, and it is awesome.
This includes a deliberate focus on creating a safe and welcoming space, and is focused on dicussion rather than lecturing or hands-on coding, so that participants can think through how this is relevant for them and learn from other labs. The program is led remotely, leveraging the power of the internet; it is led through video calls and Google Docs.
Participants get more comfortable talking about open data science topics, and then their homework is to bring these conversations back to their larger lab groups.
---
# [Sea]side chats & hackathons
<br>
```{r seaside-chat, out.width = '80%', fig.align='center'}
knitr::include_graphics("img/seaside-chats-wood.png")
```
.footnote[
blog: [openscapes.org](https://www.openscapes.org/blog/2019/03/10/seaside-chats/); [Wood lab](https://github.com/wood-lab/wood-lab-resources#wood-lab-resources)
]
???
We call these conversations Seaside Chats, or Bayside, Bluffside or Fishbowl chats. They are specific times and places to talk about reproducible research, discuss coding issues, and learn about cool new packages relevant for research.
This something that our OHI team has been doing for years now in addition to our weekly science lab meetings. This is a dedicated space to discuss and develop shared systems for the lab start weaving open data science into their every day work
We have also coopted the term hackathon, which is when our OHI team we will all drop our own projects and come together for a day or an afternoon to do something that will benefit the whole group, but is no one person's responsibility,like upgrading our filepath strategies with the "here" package.
Some labs have also done hackathons too, and gotten metadata organized and developed onboarding procedures for the lab, so that new teammembers can get on board with the lab's workflow as soon as possible.
---
# Openscapes lesson series
.pull-left[
<br>
<br>
```{r series, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/openscapes-series.png")
```
.footnote[
lesson series: [openscapes.org/series](https://openscapes.github.io/series)
]
]
.pull-right[
```{r thread, out.width = '95%', fig.align='center'}
knitr::include_graphics("img/tweet-openscapes-series-thread.png")
```
.footnote[
tweet thread: [@openscapes](https://twitter.com/openscapes/status/1131243910200668160)
]
]
???
We covered a lot of other things in our cohort calls, and I'm working on capturing them all in the lesson series that anyone is able to use.
transition: and in addition to these cohort calls, we focused a lot on leadership, both vertical and horizontal.
---
class: center, middle
# Vertical & horizontal leadership
???
continue ->
---
# Ocean Health Index team
.pull-left[
```{r halpern0, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/Halpern-UCSB_UCOP-30.jpg")
```
.footnote[
web: [National Center for Ecological Analysis & Synthesis](https://www.nceas.ucsb.edu/);
]
]
.pull-right[
```{r shiny-laughing0, out.width = '100%', fig.align='center'}
knitr::include_graphics("img/shiny-conf-2016-crop.jpeg")
# knitr::include_graphics("img/tweet-juliesquid-shinydevcon2016.png")
```
.footnote[
tweet: [@juliesquid](https://twitter.com/juliesquid/status/693324555704610816)
]
]
???
On the left here is Ben Halpern, he's the lead of OHI and he has played a huge role in our data science even though he is not a coder himself.