03 Call Digest [ 2022-noaa-afsc ]

[jules32]

Hi @Openscapes/2022-noaa-afsc-team @Openscapes/2022-noaa-afsc-assist ,

Thanks for a great third session last Friday. Last week we talked about psychological safety and team culture, and Ileana Fenwick shared some perspectives about tidy data. Below is a light digest of Call 03. 

Our next Cohort Call is next Friday, Feb 25. We'll focus on open communities and coding strategies for future us, including RMarkdown. And we have co-working times this week and next if you'd like to join to work on your things and be able to screenshare and ask questions.

Sean Lucey will be giving an AFSC seminar at 10 am PST on March 1  (link coming soon) about how he has implemented some of the open data science approaches NEFSC. 

See you next Friday if not before,

Julie, Megsie, Josh, and Em

Digest: Cohort Call 03 [ 2022-noaa-afsc ]

CohortCalls folder - contains video recordings and completed agendas

Cohort webpage: https://openscapes.github.io/2022-noaa-afsc/ 

Goals: We discussed culture and data strategies for future us, with guest teacher Ileana Fenwick (https://twitter.com/_ileanaf)

Task for next time: Continue your Pathway - shifting to "Next Steps", think about Onboarding/Offboarding

Slide Decks:

These are also available publicly from openscapes.org/series

• Psychological safety (slides) 

• Data strategies for Future Us (slides)

Co-working times

• Julie: Tuesday Feb 15, 1pm PST\ Video call link: https://ucsb.zoom.us/j/969805691\ Or dial: ‪(US) +1 347-389-1999‬ PIN: ‪993 656 960‬#

• Josh: Wednesday Feb 16, 2pm PST :  Add to Your Calendar

• Em: Thursday Feb 17, 11am PST: 

  • Add to your calendar: https://calendar.google.com/event?action=TEMPLATE&tmeid=MjE4dWxvMXBlZ2dhZW9tcXFqZDNkNGlsODJfMjAyMjAyMTdUMTkwMDAwWiBlbWlseS5tYXJrb3dpdHpAbm9hYS5nb3Y&tmsrc=emily.markowitz%40noaa.gov&scp=ALL 

  • Video call link: https://meet.google.com/hcf-dyfy-mti

  • Or dial: ‪(US) +1 617-675-4444‬ PIN: ‪526 854 015 6665‬#

  • More phone numbers: https://tel.meet/hcf-dyfy-mti?pin=5268540156665

• Megsie: 💫different this week !!💫 Thursday Feb 17, 10:00am PST: 

  • Google Meet joining info

  • Video call link: https://meet.google.com/jnw-puxq-gfb

  • Or dial: ‪(US) +1 617-675-4444‬ PIN: ‪101 095 694 4846‬#

  • More phone numbers: https://tel.meet/jnw-puxq-gfb?pin=1010956944846

 

A few lines from shared notes in the Agenda doc:

Re: psychological safety

• We're safe talking to each other but not sharing our code. We'll share our graphs, no probs. But code feels more judgmental

  • +1 - we are wrestling with it bc it exposed we all use different writing styles and grades of documentation!

  • My take home was that even talking about safe psychological spaces is a big change for us, and the acknowledgement that spaces have been unsafe in the past is a big deal.

• starting out by showing empathy and vulnerability will be contagious.  Psychological safety has to be kind of a learned thing.  At times it's hard to remove the "competitive" aspects of expertise 

• Ensure that no one's physical safety is compromised because they did not feel comfortable speaking up  - critical for shipboard work

• Our group acknowledged the 'culture' for openness and inclusion starts at the top - which our agency seems to do a good job with.

• Important to ask questions and consider how questions are framed.

Re: tidy data

• What is an example of a tidy data tool? I have a hard time comprehending that

  • Another fun example is lubridate (https://lubridate.tidyverse.org/ ) which helps format dates. Dates and locations are such a headache sometimes... they're always in different formats!

  • Janitor R package: http://sfirke.github.io/janitor/  - this renames columns in a "tidy" way programmatically so you don't have to by hand. For example  changing "Temp (°C)" to "temperature_c" +1

  • Thanks! Great examples :)

• So glad to see you guys teaching these principles---so many of us learned them the hard way fumbling through our own data.  I could have saved at least a couple of years if I'd been taught tidy data principles at the start of my grad career... +1+1+1+1+1

• All of this resonates in a huge way. All the old data i'm working with is messy and I'm just now seeing the significance of data wrangling and tidying so that code can be repeated or just altered slightly to work across different datasets over time +1

•  Wonderful overview and plug for taking the time at the beginning to tidy and keep your data consistent for your future self and others +1+1 +1+1

[MargaretSiple-NOAA]

A few folks have asked about working shared google docs into their Markdown report workflows. It just so happens that Eli Holmes made a pleasant tutorial about that and Emily added to it and posted it on nmfs-openscapes! So, if you are interested in that, check it out: https://github.com/nmfs-openscapes/GoogleDrive1

I remember @larogers123 , @BFadely , and @JenCahalan-NOAA were thinking about doing something like this. 🧪 Thank you Emily for reminding me that it exists and for putting together an example!

[jules32]

Next week we'll be discussing RMarkdown, which we know a lot of you are excited about! If you're curious about it beforehand, we had a 1-hour conversation with Alison Hill, "the RMarkdown Whisperer" who was then at RStudio. Here's a brief summary about the conversation and a link to the Youtube video: https://www.openscapes.org/blog/2021/10/01/alison-hill/.