10. Lab social events
The Data Diversity Lab aims to foster a supportive and inclusive community. As we go through the academic semester, we will aim to plan for at least 1 social event in which hopefully all the lab can participate in one form or another. In the past these have consisted of a dinner night out in Tucson, AZ, but these can really be anything. If you have suggestions about social events we as a lab could participate in, please mention them to Dr. Roman-Palacios or the lab manager.
-
Fall dinner: Lab members are invited to a restaurant in Tucson. The PI will cover food and drinks for every lab member who attends the event. Guests (family, friends) are welcome to join. However, the lab won't be able to pay for their meals (but please talk to the PI if you're in a situation where you would like to bring someone and would need support to do so).
-
Hikes and informal events: The PI will cover meals for lab members when there's a business reason behind the event (e.g. to introduce a new lab member).
Lab Writing Retreat
We tend to host a 2-day collaborative session to make progress on a given paper/project (not every year). The PI will cover lunch on those days.
Lab retreat Authorship Guidelines:
Overview
- 2 day session
- Identify a problem
- Session includes: background/introduction, data collection, analysis, methods, results, discussion, references, and figures
- Sessions typically include ~10 people
Author
- Writing contribution to the paper (paragraph/subsection)
- Figure (1 figure)
- Data processing and analyses (reproducible analyses; code on GitHub, brief description on methods/results)
- Managerial (Zotero + editing the paper + organizing GitHub)
Acknowledgements
- Formatting
- Zotero
After
- Door is open for more authors (aligned w/ the definitions presented above)
- Time allocation is subjective and contributions are the main definition to authorship
Use of AI
- Not for writing itself
- Accepted for editing (style/grammar)
- Analyses: Anything produced by AI needs to be understood by the person using the service
GitHub/NextCloud/Zotero Use
- Github: All the code should be stored in the repo (figures, analyses, not data), including Google Earth engine procedures
- Data: NextCloud - data folder
- All papers should be in Zotero