Friday, August 17, 2018

How to successfully submit a conference session proposal

Conferences are a wonderful place to learn about exciting research happening in your field, to meet new people and/or potential collaborators and to catch up with old friends. Recently, I attended the annual Joint Statistical Meetings (JSM) in Vancouver, Canada, which is the largest conference for statisticians in North America. One of the features of this conference is the program committee invites anyone to submit a proposal for an Invited Session. In terms of JSM, the due date is almost a year in advance of the conference. For example, Invited Session proposals for JSM 2019 (July 27-Aug 1, 2019) are due September 6, 2018. There are also other types of sessions called Topic-contributed Sessions and Contributed Sessions with due dates a bit later in the year. The problem is because this conference is so large, it requires a long time to read through the proposals and to organize all the sessions.

In previous years, I helped organize and participated in an invited session at JSM. This year, I submitted a proposal for a topic-contributed session, but it was elevated to a late-breaking session. Most recently, I organized an Invited Session, which was just accepted, for the 2019 Eastern North American Region (ENAR) International Biometric Society conference. Finally, I am on the program committee for the 2019 Symposium on Data Science and Statistics (SDSS).

Given my recent experiences organizing sessions for conferences and the JSM 2019 Invited Session proposals are due in a few weeks, I thought I would it would be relevant to write a blog post on strategies I use when putting together a proposal.

1. Come up with a interesting, timely and relevant topic. You might bounce ideas off of your colleagues to see if the topic would have wide enough interest and might be of interest or be relevant to a particular conference. This is often the most difficult part of organizing a session. If your topic is not really of interest to a wide enough audience, it is highly unlikely that it will be selected. However, you want it to be focused enough that you can reasonably talk about the topic in 1-2 hours.

2. Create a title and abstract for your session proposal. If you have thought carefully about the topic, this should be an easier step. The title should be succinct and representative of what you want your session to be about. The abstract should contain (1) why this topic is important and relevant, (2) the focus and goal of the session, (3) what the speakers will discuss. Ask a colleague to review the title and abstract to give you feedback.

3. Decide on speakers and send out invitation emails. First, think carefully about who is in your audience and who you want to invite. Some things to think about when coming up a list of potential speakers: their backgrounds, their expertise, their perspective, their ability to give good presentations and the diversity of the speakers. The last one is most commonly overlooked, but can bring such rich and valuable discussions if you have a diverse set of speakers.

Here is a suggested format to send the invitation emails:

Hi ____, 

I am organizing a <add name of session> session for the <add name of conference> conference in <add location> next year. The session will be focused on <add topic of session>. 

My goal with this session is for <add goal of session>. Instead of focusing on <a previously discussed topic>, I want to focus on <a new topic>. My hope for the session is that audience members will be able to <add what you want the audience to get out of the session>. 

As the <add the person's title, etc>, I would like to invite you to speak in the session <(or) join as a panel member to share your insight and perspectives (if a panel)>. Your expertise in <all the reasons why this person would be a good speaker> would be highly valuable and a great contribution to the session. 

I hope you will join the session if you plan to attend and aren’t otherwise committed. Could you let me know by <fill in the date> if you would be willing to speak? I plan to include 3-4 speakers <(or) panel members> and welcome suggestions for additional speakers. 

I am happy to answer any other questions that you may have. 

All the best, 
<add your name here>
<add your affiliation here>

Some will say yes, some will say no. If needed, send out more email requests. The main things are to explain (1) the details of the conference and session, (2) the focus and goal of the session, (3) why you are inviting them or why you think they would be a good contribution to the session, (4) and the date you need for them to respond to you by.

4. Submit a proposal to the conference by the due date. This usually includes at minium a title and an abstract. You also want to include the name of all the speakers who have agreed to participate in your session, their affiliations (departments / institutions / company name, etc), and usually an email address. This helps the conference organizers get a better idea of what will be discussed. This last one is often required, so check out what is needed for your specific conference.

5. Wait for a response from the conference organizers. This can be a quick or very long process, depending on how large the conference is. Typically the larger the conference, the longer it takes to go through all the proposals. JSM's Invited Session proposals are notoriously long:

And my favorite response from the amazing Shannon Ellis:

If your proposal is accepted, CONGRATULATIONS! Send an email to all the speakers to share the good news. They will need to register and may need to submit individual abstracts for each of their respective talks. Remind the speakers of any upcoming deadlines. If not, consider trying again next year!

Most importantly, if you are a student or postdoc, organizing a conference session can be a fantastic way to meet people in your field! You have the opportunity to craft a session on a topic that excites you the most and chair that session. Conferences need fresh perspectives and new ideas, and I find students and postdocs actively working on a research topic have some of the most insightful suggestions.

Thursday, June 21, 2018

Using Slack for Academic Departmental Communication

This is a joint blog post joint between Leonardo Collado-Torres and Stephanie Hicks. It has been cross-posted on Leo's blog too! We want to share with you our experience using Slack and why you should join us. This post is in an interview style.
What is Slack?

[SH] Slack is a communication tool for teams. The main idea is you have individual chat rooms (referred to as channels that always begin with the # symbol), which are organized by topics. Traditionally, if an email is sent to everyone on your team, each person must decide how tag or organize emails in their account. In contrast, Slack provides the structure and organization for all users on the team. Each user clicks on a specific topic, or channel, and all the messages related to that topic are already there, thereby reducing the organizational burden. In a slack team used by academic department, topics can be anything from announcements of #conferences, #workshops, #jobs, #seminars, #working_groups, #good_reads, #food_alerts, #payroll, and #IT_help. You can write public messages in the individual channels or send private direct messages to anyone on your team. Everything in Slack is searchable (e.g. files, conversations, people). Finally, Slack includes a lot of functionality and integration with other useful tools such as Google Drive.


[LCT] Slack is a website that provides access to a group of message channels bundled together in what they call a workspace. These channels can have specific purposes and different sets of members. Slack also provides many integrations with other software that we commonly use, like integration with GitHub, todo lists, Google Calendar, Google Docs, etc. The idea of using Slack is to keep your communications with close colleagues organized and make them more fluid than email. You might use the general channel for making broad announcements, such as an interesting talk from a guest. Then switch to a private channel with your 4 colleagues for that new secret project you are working on and discuss some ideas that would be useful to explore in more detail. And finally, switch to a one-on-one channel with your advisor and ask if you can meet for a few minutes that later today. Like many websites, Slack is also available as its own desktop and phone applications.


How do you use Slack?

[SH] While I communicate with colleagues everyday on Slack, I think it’s important to distinguish between Slack and email. Both are important, I just use them for different purposes. I view communication on Slack to be for instant, real-time messaging and discussion to increase collaboration. These are usually short messages compassing a single idea. In contrast, I view email to be a slower, more deliberate medium. There is less expectation for immediate response. In both cases, you can always turn them off completely and enjoy some peace too!

versus

[LCT] I’m part of multiple Slack workplaces (collections of channels and users) but I mostly use one with my genomics collaborators. There, we have a channel per project, some of which can be silent for weeks/months. But that’s ok, because I can always jump back to them and revise what we were talking about. We have a channel for R questions, one for the team that I’m a part of (Andrew Jaffe’s lab), one for organizing when and where to eat lunch, another one with the recount2 team, a diversity channel, one for our computing cluster JHPCE, among others. I also frequently ask and get asked questions on one-on-one channels with Andrew’s lab members and people elsewhere from our genomics workplace. I love using Twitter for networking in academia and keeping myself updated. So I also tend to share relevant news to specific channels I’m a part of. For the project specific channels I also use the integration with GitHub to keep everything in one place and reduce the chance of git merge issues :P


What do you like about Slack?

[SH] I recently transitioned from being a postdoctoral research fellow to an assistant professor. Many people warned me about the increase in the number of emails that I would receive. While that is certainly true, I would attribute Slack to being the biggest mitigator in reducing the number of emails that I have received. It reduces my email burden and increases communication between collaborators and colleagues. When an email sometimes seems too formal, Slack is perfect for sending out quick messages.

[LCT] It greatly reduces the amount of emails and email chains. Also, I like having the option of more communication with all my colleagues than would be typically allowed via email. Like no one would like an email about some interesting R package tweet or emails about lunch. Also, it was very useful this past year when I advised two students. I could get them involved in different projects, get them observe how we do some things, but also provide them a space to ask me questions during the week outside of our weekly meeting slot. Ultimately, I like to be organized and Slack helps me stay organized.


Any more tips?

[SH] I have found that the more I engage and write messages in channels on a Slack team, the more I get in return. As conversations flow in a given channel on a particular topic, I may or may not have anything useful to contribute. If it’s the former, I try to pass along links, advice, knowledge or whatever is appropriate. If it’s the latter, I still gain knowledge by being able to read other people’s responses and learning how others would have approached or solved a problem. Either way it’s a win-win!

[LCT] Regardless of what channel you use, it’s important to keep your messages polite. Basically, following a code of conduct similar to this one. This is not the anonymous internet, here you are interacting with your colleagues and you have to be aware of biases you might have, otherwise you might perpetrate some problems like sexism. Remember, you share the responsibility of making sure that your Slack workspace is a welcoming environment where anyone is allowed to ask questions. I also think that it’s very important to keep your boundaries clear between work and home. I highly recommend going to your preferences and automatically disabling notifications outside work hours as shown below. That’s something you can’t do with Google Chat: yes, I might be available after work hours, but I want to choose whether to respond or not and I don’t want others to expect an immediate answer if they see me online.
If you want more, check this great presentation about Slack by Stephanie Hicks.

Wednesday, June 6, 2018

Addressing Sexual Misconduct in Statistics

The cultural revolution from the recent #metoo movement has demonstrated that sexual harassment and sexual assault are far too common and often go unreported in professional settings, including in the field of Statistics. In response to this, I have organized a late breaking session at the Joint Statistical Meetings on Addressing Sexual Misconduct in Statistics on Monday July 30, 2018 2-3:50pm in Vancouver, Canada.

The focus of this session is to bring together seven panelists to discuss how sexual misconduct can negatively impact the careers of the victims and how we as a community can make positive changes. Our goal is to open the dialogue on recognizing and condemning predatory sexual behavior, and provide support and inclusion to all members of the statistics community.

This session will be a positive discussion to address this topic and will offer perspectives from conference participants, elected leaders of professional societies, academic journal editors, academic department chairs, and program committee members. In addition, this session will also include the perspective of individuals who have been directly impacted by sexual harassment or assault, which is particularly relevant to other individuals in the audience who have also been impacted by sexual harassment or assault, but may not have discussed it publicly. Keegan Korthauer will chair the session and our panelists will include:

If you are planning on attending #JSM2018, I invite you to join us.  

Friday, February 9, 2018

Lessons learned from applying for scholarships

As a graduate student (many moons ago), I applied for the Gertrude M. Cox Scholarship from the American Statistical Association. The purpose is "to encourage more women to enter statistically oriented professions". I was a woman pursing a PhD in Statistics and wanted to enter a statistically oriented profession, so I wrote an essay and submitted an application. In the essay, I explained how I got interested in statistics and why I decided to pursue a PhD. At the time, I did not have many examples of "acts of leadership", but I had done some community service and/or mentoring as an undergraduate student. Afterwards, I was sad to find out I was not selected. However, forcing myself to go through that process taught me a few general lessons when applying for scholarships (and more general things e.g. grants, papers) that have stuck with me over the years. I figured it might be worth sharing them here.

  1. As a student, it is easy to feel like your resume/CV is sparse or you do not have much to write about. You may have started a graduate program right after completing your undergraduate degree without any work experience. You may still be taking a lot of classes or not have much teaching experience. You may be early in your graduate program without any research experience or peer-reviewed publications. What is most important is your ability to communicate why you are interested in your area, why it is exciting, and why others should be excited about it. If you have done work or made contributions in the area, great. Write about it. However, as someone who now reviews applications for a full-tuition scholarship for women interested in STEM funded by Cards Against Humanity I believe it is much more important to say why you are passionate by whatever you are interested in, irrespective of how much you may or may not have accomplished. 
  2. Recommendation letters matter. You want to ask individuals who really know you. If you ask a professor who only knows that you made an A in their class and can't say much more, that comes across loud and clear in the recommendation letter. You want to ask individuals who will actively advocate for you. 
  3. Rejection is part of life and do not it deter you from pursing your passions or dreams. I will be honest: I am still struggling with this one even to this day. However, it has gotten easier over the years because I have learned to not take it personally. But seriously, some days I want to scream at the top of my lungs 'WHY DIDN'T YOU PICK ME? WHY DIDN'T YOU SELECT MY GRANT? WHY DIDN'T YOU ACCEPT MY PAPER?', etc. During those moments, I just remind myself I only have control over the next award I apply for, the next paper I submit, the next grant I write. 
Anyways, if you are woman in a full-time graduate Statistics program (MS or PhD) and a citizen or permanent resident of the US or Canada, I would encourage you to apply for the Gertrude M. Cox Scholarship. Applications are due two weeks from today (February 23, 2018). For what it's worth, I posted my (unsuccessful) application essay for the scholarship. Maybe it will help someone else write their essay! 


Saturday, October 14, 2017

Rainbow Chocolate Cake



My husband's birthday was two months ago and we really didn't get a chance to celebrate it at the time. As we were walking through the grocery store today, I asked him if he would like to make a birthday cake / dessert this weekend to properly celebrate it! I left him in the baking aisle to ponder all the possibilities. A few minutes later, he rounded the corner with a box of Rainbow "Tie-Dye" cake mix and chocolate funfetti icing!


When we got home, I started reading and following the instructions. The beginning was pretty straight forward. Mix cake mix, water, oil and, interestingly, only egg whites (no yolks). I can only assume that is to not tint the colors? Not sure though. Then, I split the cake batter into six bowls with approximately 2/3 cup cake batter in each bowl.

The box came with three packets of dye (yellow, red, and blue) and instructions on how many drops of each color to fill the six bowls of cake mix. I really liked the brightness of the red ad blue colors.


I don't have two 8" round cake pans, but the instructions said a greased 9x13 pan would work. For this pan, I poured all the cake batter from each individual bowl into the 9x13 pan in the following order: red, orange, yellow, green, blue, and finally purple. The trick is to pour the next color directly in the middle of where the last color was poured. Each layer will slowly spread out as you add an additional layer. The last step is to lightly jiggle the pan to even out any cake batter that may have been uneven. This was the cake after I jiggled it a bit.


I baked the cake in a 350F oven for 32 minutes and tested with a knife to see if it was done. Looked good to me! Then I let it cool an hour before trying to decorate it with icing.


After letting it cool, I removed it from the pan and covered it in chocolate funfetti icing! We sang Happy (belated) Birthday to him and enjoyed it after our dinner tonight. Hopefully, this post will inspire a little color creativity in your next baking adventure!


Wednesday, February 8, 2017

Sampling Points Proportional to Intensity in an Image

A few months ago Aaron Lun shared some code with me to sample points based on intensity of pixels in an image. With his permission, I thought it would be fun to share it here!


The idea is you start with some image (either in a JPEG or PNG format). Here I'm using Rafa's twitter profile picture in a JPEG format.


I'm using the readJPEG() function from the R jpeg package to read in the JPEG image. Alternatively, you can use the readPNG() function from the R png package to read in a PNG image. If you read the help file of readJPEG(), it says it "reads an image from a JPEG file/content into a raster array". OK, first off what do we mean by raster? You can think of a raster image as a rectangular grid of pixels. In the help file for the readJPEG() function, it states "most common files decompress into RGB channels (3 channels)" where RGB stands for red, green and blue.

So, this means for each pixel in the original image, we should expect 3 values (one for red, green and blue). These values range between 0 and 1 and can be thought of the intensity of each color in the image. Below, I'm showing the intensity values from the three channels colored on the same scale (top row) and colored in the red, green and blue scales (bottom row).

To get the intensity of how light a particular pixel is, we can just average the values across the three channels. Next, we flip the intensity scale by subtracting the intensity scale from 1 to see how dark/black a particular pixel is. This makes the previously dark areas now light and vice versa (top left figure below). To control the contrast of intensity, you can just take powers of the intensity values. The lighter the background, the better the contrast will be between the individual and background on the original scale. Depending on the background in the original image, the skin tone, etc you may need to tinker with the contrast. I've shown the original scale and powers of 2, 4, and 8 below.

Next, we sample points proportional to the (powered) intensity level, add a bit of random noise and then plot the sample points along the x and y axis. In the picture below, you can really see how the power is very important to control the contrast levels.


Happy sampling!


Thursday, January 5, 2017

Women in Statistics and Data Science Conference 2016

Happy New Year everyone! After a wonderful holiday break, I was excited to find my copy of AMSTAT News from the American Statistical Association in my mailbox! Someone pointed out to me that if you look close enough, I can be found standing in the background on the front cover of the Dec 2016 issue. So, apparently I can check off 'being on the cover a magazine' from my bucket list. ;)


The picture was a snapshot of an audience at talk from the Women in Statistics and Data Science Conference (WSDS) 2016 which was held in Charlotte, North Carolina Oct 20-22, 2016. The cover story can be found here. In 2014, I attended the inaugural Women in Statistics Conference and was fortunate enough to attend the conference again this year! Looking back through blogposts this fall, I realized I did not write a blog entry after I returned from the conference, but I did manage keep a few notes in a Github repo of a few of the talks. Here, I want to summarize some of my thoughts and experiences of WSDS 2016 and at the end I describe a few suggestions for future WSDS conferences. I was not able to attend all the talks mostly because there were many concurrent sessions happening at the same time, but I hope this highlights at least a portion of the conference!

The picture above was taken in a talk by one of my favorite speakers from the 2016 conference, Erin Anika Wiley from Westat, titled "Do you Hear What I Hear?: An Examination of Effective Communication". I managed to slip into the back of jammed packed room and furiously write down notes on the results of a survey she conducted asking about opinions of presentations from statisticians. I love that this was the front cover of the magazine because Erin really had the audience laughing and engaged for her entire talk. Also, it was humbling and enlightening to hear the survey responses on how non-statisticians perceive statisticians based on talks and presentations. Definitely motivation for how we can communicate our results more effectively!


The first keynote address was from Cynthia Clark titled "Consider your legacy". She gave inspirational talk discussing what her contributions have been in her personal and professional life. As a new mother, I sincerely appreciated hearing how she prioritized her family throughout her life.



Another great keynote address was from Stacy Lindborg at Biogen with a talk titled "Know your power". Stacy is a natural at connecting with the audience by sharing personal stories from her life. In this talk, she shared five reflections/tips on having a successful career in the face of many challenges (both personal and professional). One of my favorite quotes from her talk was "We love the things that we are good at", which really resonated with me.

Keeping with theme of careers, a topic I found particularly interesting is how to navigate changes in your career. Michelle Dunn, Donna LaLonde, and Nancy Flournoy shared very honest and personal experiences of following non-traditional career paths, recognizing and moving forward when you have failed, and knowing when to leave a job. A central theme from each of their talks was to always be growing your network and find trusted individuals/mentors to help you navigate these experiences.

Similar to the session in 2014, the 2016 conference included a fantastic panel of the past, current and future ASA Presidents. These women were able to persevere in the face of a highly male-dominated field to become ASA Presidents and become role models for women in the early stages of their career like me. Even with all this progress, I agree with Mary Ellen Bock that there is so much more work still to do with supporting more specific minority groups in this field. For example, she eloquently described her hope of one day seeing a non-white woman on this panel of presidents.


In my opinion, one of the coolest sessions was listening to the amazing Mary W. Gray from American University giving a fascinating discussion on what US laws exist to protect women. If you don't know who she is, you can read a summary on wikipedia, which is pretty incredible! One of my favorite things that I learned about her was that she wears a 3/4 euro lapel pin (noting pay inequality is not limited to the US) to promote "equal pay for equal work" referring to the Equal Pay Act in 1963 and Title VII in 1964.  Sadly I didn't get a picture of the lapel pin, but I love the idea!


Wendy Martinez from the Bureau of Labor Statistics gave a great keynote address on what and how federal statistical agencies are thinking about when it comes to data science. Data science is something I am passionate about, so I really enjoyed this talk. I would have loved to see a larger emphasis on data science education though.


Unfortunately Bin Yu from UC Berkeley was unable to join us in person, but the conference organizers were able to set up a video chat and connect to the big screen!  Her talk was titled "A holistic approach to interdisciplinary research" where she began discussing how she has a people centric view of life and research (people are mysteries to unveil just like research). It was amazing to hear a little bit about her background and how she grew up in China during the cultural revolution (1966-1976) where the universities stopped for 10 years. Something I think that cannot be overstated was she noted that she most appreciates intellectual diversity in collaboration and research. Overall, it was an inspiring talk!


The conference ended with a festive dinner filled with new friends, awards, presentations and delicious desserts!


As the conference took place at a hotel, I managed to find a nice location to write down some notes from the talks on my GitHub page. :) Feel free to check them out for more details on the talks that I attended.



Finally, I want to finish this blogpost with a few suggestions for future WSDS conferences. My intention is for these suggestions to be viewed as constructive to help make this conference stronger and more accessible to women in the future.

  1. Fewer talks running concurrently and more posters/speed sessions. I appreciated that the keynote talks did not have other scheduled talks, but at other times I had to choose between 5-6 sessions running concurrently, which led to frustration and disappointment that I missed so many other talks. My arguments for this are similar to the ideas previously described to improve JSM (decreasing the number of contributed sessions and increasing the presence and importance of poster sessions)
  2. More talks from women in data scientist positions in academia, government, and industry. I recognize that the term "data science" is very much being actively debated in many settings, but as this conference now has "data science" in the title, I would love to see a larger discussion of data science and how that relates to statistics, here too. There was such a great representation of perspectives from women who pioneered this field. I think it would be equally beneficial to include the perspective from a new generation of women in data science positions. 
  3. Childcare. I was surprised to find out that no childcare was available at this conference. Considering a good portion of this conference was dedicated towards discussing issues related to balancing careers with families, I found a lack of childcare a bit ironic (?). This suggestion is motivated by my own personal experience of recently having a baby. I saw several other WSDS attendees who brought their children and probably could have benefited from a childcare service. There are great childcare examples broken down by cost, size of conference, childcare agency, fees charged, etc.  I hope this will be incorporated in future WSDS conferences. 
Thank you to all the conference organizers for putting together this conference. I look forward to the next one in La Jolla, CA Oct 19-21, 2017!