Lab Rules

Lab Manual for the Slab


Table of Contents



Code of Conduct

Expectations and Responsibilities

General Policies



It looks like you recently joined the Salomon Lab in Bar Ilan University. We’re really glad to have you here at the Slab. We hope you’ll learn a lot about psychology and neuroscience, develop new skills (coding, data analysis, writing, giving talks), make friends, and have a great deal of fun through the whole process.

This lab manual was inspired by several others, and borrows heavily from them (e.g.,  this one and this one). It’s also a work in progress. If you have ideas on things to add, or what to clarify, talk to me (Roy Salomon, the PI) or the lab manager (Amir Harduf).

When you join the lab, you’re expected to read this manual and sign a form indicating that you have done so.


The Salomon Lab at Gonda Brain Research Center (SLab) aims to produce high quality research into: 1) the cognitive and neural basis of the construct of the “Self”, 2) the neural underpinnings of conscious experience, 3) novel interventions to help populations with deficits in 1 & 2.

The lab supports Open Science practices including pre-registration of studies, open data, open code and open access.   

SLab aims at advancing scientific knowledge as well as developing the careers of its members by providing an excellent and constructive scientific workplace.

Code of Conduct

The lab should be a safe, fun and supportive environment. Any behavior which is not in line with this is unacceptable. All conduct must be fair, respectful and honest. Specific university regulations regarding  sexual harassment can be found here, student ethics here and general scientific conduct here.  These will not be elaborated further in this Manual.

Expectations and Responsibilities


Big Picture

Science is hard. But it’s also fun. In SLab, we want to make sure that everyone experiences a positive, engaging, challenging, and rewarding lab environment. To maintain that environment, we all have to do a few things.

  • Work on what you’re passionate about, work hard at it, and be proud of it.
  • Scientists have to be careful. Don’t rush your work. Double and triple check it. Incorporate sanity checks. Ask others to look at your code or data if you need help or something looks off. It’s ok to makes mistakes, but mistakes shouldn’t be because of carelessness or rushed work.
  • If you do make a mistake, tell your collaborators (especially if the paper is being written up, is already submitted, or already accepted). We admit our mistakes, and then we correct them and move on.
  • We all want to get papers published and do great things. But we do this honestly. It is never ok to plagiarize, tamper with data, make up data, omit data, or fudge results in any way. Science is about finding out the truth, and null results and unexpected results are still important
  • Be supportive of your lab mates. We are a team.
  • Respect your fellow lab-mates. Respect their desire for quiet if they need it, and for support and a kind ear when they need that. Respect their culture, their religion, their beliefs, their sexual orientation.   
  • Respect the administrative staff of the department, they work hard to help us!
  • If you’re struggling, tell someone (feel free to tell Roy!). Your health and happiness come first. The lab looks out for the well-being of all its members.
  • If there is any tension or hostility in the lab, something has to be done about it immediately. We can’t thrive in an environment we aren’t comfortable in, and disrespect or rudeness will not be tolerated in the lab. If you don’t feel comfortable confronting the person in question, tell Roy.
  • Science is a marathon, not a sprint. Take personal time/ vacation when you need it and cultivate a life outside of the lab. Respect that other lab members also have a life outside of lab.
  • Academia may feel different from other types of jobs, but it is still a job. You should treat coming into lab with the same respect that you would treat any other position. See Hours.


Small Picture

There are a few day-to-day things to keep in mind to keep the lab running smoothly.

  • If you’re sick, stay home and take care of yourself. Because you need it, and also because others don’t need to get sick. If you’re sick, reschedule your meetings and participants for the day (or the next couple of days) as soon as you can.
  • Notify the lab manager or me if you will be out, either due to illness or vacation. Make a note on the lab calendar. If you are sick and you had experiments or meetings scheduled that day, notify your participants or collaborators and reschedule.
  • Vacation should be arranged sufficiently far in advance to ensure cover is available for your tasks (e.g., testing participants), in consultation with the PI.  
  • You aren’t expected to come into lab on weekends and holidays, and you aren’t expected to stay late at night. You are expected to get your work done (whatever time of day you like to do it).
  • Show up to your meetings, show up to run your participants, show up to your classes, and show up to lab meetings. You do not have to be in at 9am every day – just show up for your commitments, and work the hours you need to work to get stuff done.
  • Working from home is generally ok but discuss this with the PI in advance so your absence is made known.  
  • Make sure the door to the lab is locked if no one is inside. Turn off the lights if you’re the last one leaving for the day.
  • Keep the lab tidy. Eating in lab is fine, but clean up food waste, crumbs, spills. Put lab equipment back where you found it. Keep common areas uncluttered.
  • The dress code in academia is generally casual. My only request is that you look semi-professional when interacting with participants and when presenting your work. Jeans are fine, gym clothes and pajamas are not.
  • Be on time. Especially when you are running participants – in fact, show up 15-20 minutes early to set everything up. And be on time for your meetings: respect that others have packed days and everyone’s time is valuable.


Principal Investigator

All of the above, and I promise to also…

  • Maintain a vision of where the lab is going
  • Provide the funding necessary to keep the lab going
  • Meet with you regularly to discuss your research projects. The definition of “regularly" may change over time or over the course of a project, but for now, I mean once a week or more often as needed
  • Give you my perspective on academia and issues related to professional development
  • Support your career development by introducing you to other researchers in the field, writing recommendation letters for you, providing you with opportunities to attend conferences when possible, and promoting your work in talks
  • Care about you as a person and not just a scientist



All of the above, and you will also be expected to…

  • Develop your own independent line of research
  • Help train and mentor students in the lab (both undergraduate and graduate) when they need it – either because they ask, or because I ask you to
  • Present your work at departmental events, at other labs (if invited), and at conferences
  • Apply for external funding. I will hire postdocs only when there is funding available for at least a year; however, applying for external funding is a valuable experience and, if awarded, it will release those dedicated funds for other purposes.
  • Apply for jobs (academic or otherwise) when you’re ready, but no later than the beginning of your 4th year of post-doc. If you think you’d like to leave academia, that’s completely ok – but you should still treat your post-doc seriously, and talk to me about how to best train for a job outside academia
  • Challenge me (Roy) when I’m wrong or when your opinion is different, and treat the rest of the lab to your unique expertise


PhD /MsC Students

All of the above, and you will also be expected to…

  • Develop your dissertation research. Your dissertation should have at least 3 substantial experiments that answer a big-picture question that you have. Much of your work has to be done independently, but remember that others in lab (especially Roy!) are there to help you when you need it
  • Help mentor undergraduate students in the lab when they need it – either because they ask, or because I ask you to. Undergrads can also help you collect data.
  • Present your work at departmental events, at other labs (if invited), and at conferences
  • Apply for grants. It’s a valuable experience, and best to get it early.
  • Think about what you want for your career (academia – research or teaching, industry, science writing, something else), and talk to Roy about it to make sure you’re getting the training you need for that career
  • Make sure you meet all departmental deadlines (e.g., for your exams and thesis) — and make sure Roy is aware of them!
  • Prioritize time for research. Coursework and Teaching are important, but ultimately your research gets you your Masters or PhD and prepares you for the next stage of your career. However, it is your responsibility to get the grades you need for your career (e.g. for MSC, PhD.).


Undergraduate Students

All of the above, and you will also be expected to…

  • Assist other lab members with data collection and analysis (unless you are working on your own independent project under the mentorship of another lab member, in which case you should work on that)
  • Develop your weekly schedule by talking to your graduate student mentor or your post-doc mentor. You should be coming in every week, and scheduling enough time to get your work done
  • If you are earning course credit for research, you must also attend lab meetings when your schedule permits, present at one of these lab meetings, and submit a write-up of your research by the end of the semester

All of the above, and you will also be expected to…

  • Help Roy manage the lab
  • Maintain the lab IRB protocols and paperwork (e.g., archiving consent forms).
  • Make purchases and payments on the lab’s behalf.
  • Oversee the hiring, scheduling, and training of undergraduate research assistants.
  • Assist with participant recruitment and scheduling.
  • Assist other lab members with data collection or analysis (typically you will be assigned to particular projects).
  • Help to maintain an atmosphere of professionalism within the lab.
  • Work on your own research project.
  • Be in the lab on a regular basis — more than other lab members, your presence in lab when others are around is essential.


General Policies


Like other labs, we will follow the APA guidelines with respect to authorship:

“Authorship credit should reflect the individual's contribution to the study."

At the start of a new project we will discuss authorship. Roy will typically be the last author. Authorship will primarily reflect the contribution to the project, and will be decided by Roy. We will try to make this clear in advance so no surprises occur. We can always talk about authorship, but best to have it made clear from the start.



Being in lab is a good way of learning from others, helping others, building camaraderie, having fast and easy access to resources (and people). That said, hours in academia are more flexible than other jobs — but you should still treat it as a real job (40 hours/week) and show up to the lab. My primary concern is that you get your work done, so if you find that you are more productive at home (lab-mates can be chatty sometimes), feel free to work at home occasionally. If you have no meetings, no participants, and no other obligations that day, it might be a good day to work at home – but you can’t do this all the time, and I expect to see everyone in the lab on a regular basis.

The only exception to this is lab managers / research assistants, who must keep more regular hours.

For graduate students, I understand having to be away for classes and TA-ing, but show up to the lab on a regular basis when you don’t have those obligations.

To encourage lab interaction, try to be in most weekdays during ‘peak’ hours (assuming no other obligations) – e.g., between 11am and 4pm. This is not a hard rule, you can work at home occasionally, and I understand other obligations.

PI Office Hours

In addition to weekly meetings (see below), and occasionally dropping by the lab, you can usually find Roy in his office (Gonda 217). The door is almost always open; if it is, feel free to ask for a chat. If the door is closed, if urgent knock once and see if I holler back, otherwise email me.

Lab Resources


Google Calendars

The lab uses Google calendars:

  1. SLab calendar: used to keep track of lab events, including any lab meetings just for our lab, and birthdays!
  2. Experimental Room & Equipment  calendar: used to keep track of experiments in the lab.
  3. We may add additional calendars as needed.


Emails and documents

We use email a lot so this communication must be optimized.

  1. Don’t Spam.
  2. Keep it short and clear.
  3. We will be sharing many documents over email. Make sure to label them well. For example “results” or “project” are no help. Pls write in the subject line what project this is e.g. MRHI_EEG_Pilot  or VR_Agenncy_Meta. Files should have meaningful names including the project name and their content “JoV_intorduction_V3” , MRHI_EEG_Results_12_SS”.
  4. When we are working on a document together always use Track Changes option in word so we can have some version control. When sending back and forth corrections on a version add you initials at the end e.g. “Dvir_Thesis_Intro_V3_RS”.
  5. Before Sending an Email or Document Always check it using Spellinmg and Graammer (F7 in word).


Slab Website

The Slab website can be found here  all our papers are there. When you join the lab please send Roy a picture you like and a short bio as found here . The lab site will be maintained by a student form the lab (Currently Roy).




You can email me anytime.


Slab articles is only for articles and resources

Slab is for fun, lunch and gossip

We can create ad hoc groups for tight and quick communication.

You can Whatsapp me personally for urgent stuff otherwise mail me.


During business hours call me if needed urgently otherwise email.

If very urgent/ emergency call me anytime 



We have lots of equipment some is very expensive (e.g. EEG at 300000 NIS) and some less but all of the equipment is critical for our work and should be taken care of. All equipment must be cleaned, charged and returned to its place after use.  This is the responsibility of all lab members but to make it more personal:

EEG equipment- Dvir

LEAP and Leap platforms- Amit

RHI- Amir

fMRI Equipment (e,g, dongle, MRHI fmri.. etc..)- Amir

Arduino and peripherals- Yaniv

VR- Yaniv

Amir as lab manager has oversight for all equipment and if you have a question go to him or come to me.  



Weekly Lab Meetings

Weekly lab meetings (~1.5 hours each) are meant to be a forum for trainees to present project ideas and/or data to get feedback from the rest of the group. Projects at any level of completion (or even not yet started!) can benefit from being presented. These lab meetings can also be used to talk about methods, statistical analyses, new papers, and career development. For paper discussions, everyone must come to lab meeting having read the paper and prepared with comments and questions to contribute. Some weeks we may explore a particular issue and have people read different papers – in that case, come to lab meeting having read your paper and be prepared to summarize it for the group.

The lab meeting is a course and lab member MUST be registered. Each person is expected to present at least once every semester. These meetings are informal, and you can do what you wish with your slot – just be prepared to contribute something substantive. Lab members are also expected to attend every meeting (obviously, illnesses, doctor appointments, family issues, etc are a valid reason for missing a meeting). Undergraduate students are encouraged to attend as often as possible (assuming it fits in their course schedule). SLab meeting agendas and notes will be kept in the SLab calendar.

Individual Meetings

At the beginning of each semester, we will set a schedule for weekly meetings. Each full-time lab member (RAs, graduate students, post-docs) will have a one-hour slot set aside to meet with Roy. If scheduling conflicts arise (e.g., because of travel), we can try to reschedule for another day that week. If there is nothing to discuss, feel free to cancel the meeting or just drop by for a brief chat.

Roy will meet with undergraduate students every other week (or according to need); post-docs and graduate students should meet with their undergraduate mentee on a regular basis.



Deadlines are important to make things happen, so we will use them both for you and for me.

For students:

I suggest setting clear deadlines for your work. Typically, this should be a 1-2 week deadline set by you indicating what you will have accomplished by our next meeting.

For me:

Give Roy at least one week’s notice to do something with a hard deadline that doesn’t require a lot of time (e.g., reading/commenting on conference abstracts, filling out paperwork, etc).

Give Roy at least two weeks’ notice to do something with a hard deadline that requires a lot of time (e.g., a letter of recommendation). For manuscript revisions, Thesis versions etc , give him at least 3 weeks, because these will require multiple back-and-forths.

For manuscript submissions (i.e., no hard deadline), you can still bug Roy to give you feedback if he hasn’t responded in a week or two – papers are important!



Learning to present your research is important. Very few people will read your papers carefully (sad, but true) but you can reach a lot of people at conference talks and posters. Also, if you plan on staying in academia, getting a post-doc position and getting a faculty position both significantly depend on your ability to present your data. Even if you want to leave academia, presentations are likely to be an important part of your job. Additionally, every time you present your work, you are representing not just yourself but the entire lab.

It is therefore highly encouraged that you seek out opportunities to present your research, whether it is at departmental talk series and events, to other labs (within or outside of Bar Ilan), at conferences, or to the general public. If you are going to give a presentation (a poster or a talk), be prepared to give a practice presentation to the lab at least one week ahead of time (two weeks or more are advisable for conference presentations, and many weeks ahead of time are advisable for job talks, which require much refining).  Practice talks will help you feel comfortable with your presentation, and will also allow you to get feedback from the lab and implement those changes well in advance of your real presentation.

Templates for posters (add link), and talks (add link) are available and should be kept visually similar to the lab style. Some general rules for posters should be followed: minimize text as much as possible (if you wrote a paragraph, you’re doing it wrong), make figures and text large and easy to see at a distance, label your axes, and make sure different colors are easily discriminable


Recommendation Letters

Letters of recommendation are extremely important for getting new positions and grants. You can count on Roy to write you a letter if you have been in the lab at least one year (it’s hard to really know someone if they have only been around for a few months). Exceptions can be made if students or post-docs are applying for fellowships shortly after starting in the lab.

Data Management

Storing Active Datasets

Lab data must be stored in two places:

  1. Your computer
  2. Shared Slab Onedrive (See Below for details on data structure).

I further recommend that you backup to Hard disk provided by the lab.

Each lab member should back up raw data on an external hard drive, as well as the code needed to reproduce all analyses.

Data Organization

If you have already run several independent projects and have a data organization structure that works well for you, feel free to use it. If not (or if you are looking for a change), the following structure is recommended (based on Neuropipe):

  • projectName/subjects
    • individual directories for each of your participants
    • projectName/subjects/{subj}/analysis
      • subject-specific analyses (e.g., 1st and 2nd level analysis – at the run level and experiment level)
    • projectName/subjects/{subj}/data
      • raw data for that participant, with the following directories…e.g.
        • behavioralData (for, well, behavioral data)
        • eyetrackingData (if applicable)
        • nifti (raw nifti files / raw MRI and fMRI data)
        • rois (participant-specific ROIs)
      • projectName/subjects/{subj}/design
        • timing files for that participant, with different directories for the different GLMs you’re running (and the different runs in the experiment)
      • projectName/subjects/{subj}/fsf
        • if you’re using FSL, put the .fsf fies here. If you’re using SPM or something else, save the files for setting up preprocessing and GLMs here
      • projectName/subjects/{subj}/scripts
        • Matlab, Python, R, or bash scripts that you used for that participant. You should keep the ‘template’ scripts elsewhere, but you can store scripts you modified specifically for that participant here
      • projectName/ Analysis_code
        • template scripts and that you may modify for each participant, as well as scripts and functions used for all participants and group analyses
        • recommend making subdirectories for each type of analysis (e.g., behavior, pattern analysis, functional connectivity, univariate)
        • if you have scripts that are the same for each participant, you can have symbolic links for them in your participant-specific scripts directories
      • projectName/results
        • figures with main results, powerpoint or keynote presentations, manuscripts if you wish
      • projectName/notes
        • detailed notes about the design, analysis pipeline, relevant papers, etc
      • projectName/group
        • group analyses
        • recommend making subdirectories for each type of analysis (e.g., behavior, pattern analysis, functional connectivity, univariate)
      • projectName/task
        • code for your behavioral experiment, stimuli, piloting information
        • if you are running your presentation code out of Dropbox, it will still be good to have a copy of the code here (but you can keep the stimuli only on Dropbox if you’d like)

When you leave the lab, your projects directories should be set up like this, or something similarly transparent, so that other people can look at your data and code. You must do this, otherwise your analysis pipeline and data structure will be uninterpretable to others once you leave, and this will slow everyone down (and cause us to bug you repeatedly to clean up your project directory or answer questions about it).

Archiving Inactive Datasets

Before you leave, or upon completion of a project, you must archive old datasets and back them up. We will develop the instructions for this when we reach our first inactive dataset.

Open Science

We’re all for open science including:

  1. Preregistration of projects
  2. Code Sharing
  3. Data Sharing
  4. Preprints
  5. Open Access

Lab members are required to share their code and data with others, whether they are in the lab or outside of it. Within lab, you can share your code and data whenever you like. But do not share your code or data with the outside world until you think (and Roy agrees) that the lab has finished working with it. This gives us an opportunity to work with the data before releasing it for other people to use. Currently, the best option for sharing smaller datasets might be the Open Science Framework, and the best option for sharing MRI datasets is OpenFMRI .

We will also share our work with the world as soon as we ready, which means preprints! The lab policy is to upload a preprint of a manuscript simultaneously with initial submission to a journal. The preferred preprint servers are bioRxiv and PsyArXiv. We will also put PDFs of all our papers on the lab website, and you should share PDFs of your paper with whoever asks.



Once you have read all of this please sign this form . If you have questions or you feel this guide can be improved talk to the lab manager (Amir) or the PI (Roy).

Good Luck!!