Skip to content

Latest commit

 

History

History
85 lines (59 loc) · 11.8 KB

README.md

File metadata and controls

85 lines (59 loc) · 11.8 KB
Raw

ManyIndividuals

We are a global network of researchers with field sites investigating hypotheses that involve generalizing across many individuals (e.g., populations or species). We conduct the same tests in the same way across species to determine whether the results of particular experiments are generalizable beyond that population or species.

Research questions

  • Can behavioral flexibility be increased by experimentally increasing environmental heterogeneity (via serial reversal learning)?
  • Can such an increase in flexibility help species (particularly threatened species) succeed in human modified environments?

Registered reports (passed pre-study peer review at Peer Community in Registered Reports)

Founders

  • Dr. Kelsey McCune - designed the foraging predictability experiment and conducts experiments in California and Florida scrub-jays at her field site in Oregon and at Archbold Biological Station in Florida. Developed the reproducible workflow
  • Dr. Rachael Shaw - conducts experiments in the threatened toutouwai at her field site in New Zealand, then assesses the manipulation’s impact on their ability to survive in a human modified environment
  • Dr. Corina Logan - designed the serial reversal manipulation and conducts experiments in great-tailed grackles at her field site in northern California. Developed the reproducible workflow

Collaborators

  • Dr. Dieter Lukas - customized the analyses for the reversal learning and feeder experiments, generated Bayesian "power analyses" to determine what level of differences will be detectable with which sample size, validated the serial reversal passing criterion, and made the analyses generalizeable across species

The tools: an open and verifiable workflow that makes research better and faster

We use a replicable infrastructure where all programs are free to use (and some are open source) - feel free to try it out!

Materials shared within the network

  • Slack group for coordinated conversations that don’t clog up inboxes (can use Mattermost [open source] instead of Slack, but you have to host the conversations on your own server)
  • Google Sheets for all data sheets so everyone can enter/edit/see everything at the same time. What to code in each column is clearly defined in the Protocol…
  • Keeper is an online data back up space with ready-made folders for each experiment. Experimenters upload data sheets and videos daily. File naming instructions are included in each protocol here at GitHub (IndividualID_YYYY-MM-DD_ExpName_SessionNumber_TrialNumber)

Materials shared within each lab

  • Signal for when experimenters need immediate access to coordinators while testing
  • Google Calendar for each lab to coordinate the project internally
  • Google Photos album for each lab so experimenters can add photos and everyone can access them for their presentations/articles/websites

Public materials

  • GitHub organization with a public repository (this page that you are reading) for registered reports, final data sheets, bibliography, etc., and a private repository for links to google sheets with the budget, receipt tracking, registered report subimission plan and data collected for each, the Slack workspace, and Google Drive folder. For each repository, make one folder called “Files” and put everything in there (except for the readme file) using…
  • GitHub Desktop to push and pull files between your computer and your GitHub repo using folders (you can make folders on your computer, but not at GitHub directly)
  • Rmarkdown (rmd) is a reproducible manuscript where we write registered reports/articles. Rmd files contain all of the analysis code and text in one document. Put data sheets at the public GitHub repository and call them in the R code inside the rmd file and then anyone anywhere can download your rmd file and run your analyses in the same way you did. Open rmd files in RStudio (e.g., https://github.com/corinalogan/grackles/blob/master/Files/Preregistrations/gxpopbehaviorhabitat.Rmd)
  • Google Docs to write experimental protocols and link to them in the registered reports and articles at GitHub (e.g., http://corinalogan.com/Preregistrations/gxpopbehaviorhabitat.html#Protocols_and_open_materials)
    • Make the shareable link VIEW ONLY so the public can’t edit it; share directly with collaborators and experimenters and list them as editors so they can update as testing progresses
    • Write exceptions at the protocols as you go for anything that comes up that was not planned or had to be tweaked
  • Peer Community in Registered Reports to submit our registered reports for pre-study peer review and acceptance (then we collect the data and submit it back to PCI RR for its post-study peer review)

Code of conduct

We conduct open, verifiable, ethical research

  • All research that generates experimental data starts off as a registered report
  • If research outputs are disseminated via a journal (rather than only at Peer Community In), the journal must have the following features (why? See Logan 2017 and Corina's website):
    • Be 100% open access
    • Select articles based on scientific validity, not subjective impact
    • Be published by an ethical publisher (e.g., non-profit, researcher run)
    • Is not part of a contract where institutes pay to publish open access (e.g., read and publish agreements, transformative agreements - read why these are unethical here) (note: institutes pre-paying APCs in batches at a journal is ok as long as there is no contract)
    • The review history must be publicly available
    • The article must be published under a CC BY license
    • It should be free to publish (no APCs) or very cheap

We strive to take anti-racist and anti-sexist action

  • Selection of new team members is designed to counteract racist/sexist biases (details here)
  • We recognize that some lab members require additional supports to safely conduct their work. We strive to work together to develop and implement these supports
  • We implement learnings from anti-racist and anti-sexist resources such as those from Dr. Romero-Olivares lab.

We cultivate a harassment-free and welcoming environment

All members of the lab, along with visitors, are expected to agree with the following code of conduct. We will enforce this code as needed. We expect cooperation from all members to help ensure a safe and welcoming environment for everybody.

The Quick Version The lab is dedicated to providing a harassment-free and welcoming experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). We do not tolerate harassment of lab members in any form. Sexual language and imagery is generally not appropriate for any lab venue, including lab meetings, presentations, or discussions. (However, do note that we work on biological matters so work-related discussions of, for example, animal reproduction are appropriate.) We value individual differences and strive to create a welcoming environment for lab members.

The Less Quick Version Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Members asked to stop any harassing behavior are expected to comply immediately. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact Corina Logan (corina_logan [at] eva.mpg.de) immediately. If Corina is the cause of your concern, contact another member of the network.

We realize that people come from all over the world to work on research projects with our network, and we strive to make everyone feel welcome. For example, English may not be the native language of many lab members; therefore, we will take the time to go slowly and prioritize understanding over speed or convenience. As well, many lab members are multi-lingual, which can help facilitate communication.

We expect members to follow these guidelines at any lab-related event.

These Lab Interpersonal Interactions are based on Titus Brown's who cites the original source and credit: http://2012.jsconf.us/#/about & The Ada Initiative. Please help by translating or improving: http://github.com/leftlogic/confcodeofconduct.com. This work is licensed under a Creative Commons Attribution 3.0 Unported License