Lab Roles - Revision history

Chris: /* Data Triage and Organization: Unassigned */

2019-05-07T20:43:20Z

Data Triage and Organization: Unassigned

← Older revision		Revision as of 16:43, 7 May 2019
Line 54:		Line 54:

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==
	Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders so that no data gets lost, and that everyone can access the data for whatever projects they are working on. If data are acquired on a Sunday, I'd like to have the data uploaded to ubfs ~~no later than Tuesday~~.		Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders so that no data gets lost, and that everyone can access the data for whatever projects they are working on. If data are acquired on a Sunday, I'd like to have the data uploaded to ubfs by the end of Monday.

	===MRI Data===		===MRI Data===

Chris: /* Data Triage and Organization: Unassigned */

2019-05-07T20:42:53Z

Data Triage and Organization: Unassigned

← Older revision		Revision as of 16:42, 7 May 2019
Line 54:		Line 54:

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==
	Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders so that no data gets lost, and that everyone can access the data for whatever projects they are working on.		Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders so that no data gets lost, and that everyone can access the data for whatever projects they are working on. If data are acquired on a Sunday, I'd like to have the data uploaded to ubfs no later than Tuesday.

	===MRI Data===		===MRI Data===
	The raw MRI data for a participant should go in a folder with the participant name in the /raw/ folder underneath the appropriate project directory. For example, new data for Subject 001 Session 1 in the Semantic Categories experiment (''SemCat'') would be found in:		The raw MRI data for a participant should go in a folder with the participant name in the /raw/ folder underneath the appropriate project directory. For example, new data for Subject 001 Session 1 in the Semantic Categories experiment (''SemCat'') would be found in:

Chris: /* Data Triage and Organization: Unassigned */

2019-05-07T20:41:55Z

Data Triage and Organization: Unassigned

← Older revision		Revision as of 16:41, 7 May 2019
Line 54:		Line 54:

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==
	Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders		Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders so that no data gets lost, and that everyone can access the data for whatever projects they are working on.
	===MRI Data===		===MRI Data===
	The raw MRI data for a participant should go in a folder with the participant name in the /raw/ folder underneath the appropriate project directory. For example, new data for Subject 001 Session 1 in the Semantic Categories experiment (''SemCat'') would be found in:		The raw MRI data for a participant should go in a folder with the participant name in the /raw/ folder underneath the appropriate project directory. For example, new data for Subject 001 Session 1 in the Semantic Categories experiment (''SemCat'') would be found in:

Chris: /* MRI Scheduling */

2019-05-07T20:40:27Z

MRI Scheduling

← Older revision		Revision as of 16:40, 7 May 2019
Line 44:		Line 44:
	15:45: Participant 3 arrives, completes all safety screening sheets and prepares for scanning		15:45: Participant 3 arrives, completes all safety screening sheets and prepares for scanning
	16:00: Participant 2 exits the scanner, Participant 3 goes in the scanner		16:00: Participant 2 exits the scanner, Participant 3 goes in the scanner
	...etc., with each successive participant arriving 15 minutes before the ~~next hour~~.		...etc., with each successive participant arriving 15 minutes before the end of the previous scan.
	Of course, there's sometimes a delay, so with additional participants, later scans might get backed up. But assuming everything goes smoothly, this would be an ideal schedule where we plan to have each participant arrive about 15 minutes before we intend to put them into the scanner.		Of course, there's sometimes a delay, so with additional participants, later scans might get backed up. But assuming everything goes smoothly, this would be an ideal schedule where we plan to have each participant arrive about 15 minutes before we intend to put them into the scanner.

Chris: /* MRI Scheduling */

2019-05-07T20:35:06Z

MRI Scheduling

← Older revision		Revision as of 16:35, 7 May 2019
Line 49:		Line 49:
	Because we are trying to find times that accommodate as many participants as possible in a single afternoon block, tools like [https://doodle.com/ Doodle Poll] could be quite helpful. I would probably write an email to all potential participants (using the BCC field for all email addresses) along the following lines:		Because we are trying to find times that accommodate as many participants as possible in a single afternoon block, tools like [https://doodle.com/ Doodle Poll] could be quite helpful. I would probably write an email to all potential participants (using the BCC field for all email addresses) along the following lines:
	Thank you for your interest in the CCN Lab fMRI Experiment!		Thank you for your interest in the CCN Lab fMRI Experiment!
	We are currently scheduling participants for '''$DATE''' between '''$START_TIME''' and '''$END_TIME'''. The scan session should last about 75 minutes, and you will be reimbursed ~~via~~ Amazon Gift Card ~~$30~~. Below is a link to a doodle poll where you can indicate your availability. Please reply to the doodle poll in the next day, indicating your first name and the time slots you can attend so that we can accommodate as many participants as possible. If we don't hear from you in the next day or so, we'll follow up to see if you're still interested.		We are currently scheduling participants for '''$DATE''' between '''$START_TIME''' and '''$END_TIME'''. The scan session should last about 75 minutes, and you will be reimbursed with a $30 Amazon Gift Card. Below is a link to a doodle poll where you can indicate your availability. Please reply to the doodle poll in the next day, indicating your first name and the time slots you can attend so that we can accommodate as many participants as possible. If we don't hear from you in the next day or so, we'll follow up to see if you're still interested or have any questions. Of course, if you have any questions before then or are having problems replying to the doodle poll, please reply to this email to let us know right away!
			Sincerely,
			The CCN Lab at the University at Buffalo

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==

Chris: /* MRI Scheduling */

2019-05-07T20:33:12Z

MRI Scheduling

← Older revision		Revision as of 16:33, 7 May 2019
Line 46:		Line 46:
	...etc., with each successive participant arriving 15 minutes before the next hour.		...etc., with each successive participant arriving 15 minutes before the next hour.
	Of course, there's sometimes a delay, so with additional participants, later scans might get backed up. But assuming everything goes smoothly, this would be an ideal schedule where we plan to have each participant arrive about 15 minutes before we intend to put them into the scanner.		Of course, there's sometimes a delay, so with additional participants, later scans might get backed up. But assuming everything goes smoothly, this would be an ideal schedule where we plan to have each participant arrive about 15 minutes before we intend to put them into the scanner.

			Because we are trying to find times that accommodate as many participants as possible in a single afternoon block, tools like [https://doodle.com/ Doodle Poll] could be quite helpful. I would probably write an email to all potential participants (using the BCC field for all email addresses) along the following lines:
			Thank you for your interest in the CCN Lab fMRI Experiment!
			We are currently scheduling participants for '''$DATE''' between '''$START_TIME''' and '''$END_TIME'''. The scan session should last about 75 minutes, and you will be reimbursed via Amazon Gift Card $30. Below is a link to a doodle poll where you can indicate your availability. Please reply to the doodle poll in the next day, indicating your first name and the time slots you can attend so that we can accommodate as many participants as possible. If we don't hear from you in the next day or so, we'll follow up to see if you're still interested.

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==

Chris: /* Initial Scheduling (Prescreening) */

2019-05-07T20:22:39Z

Initial Scheduling (Prescreening)

← Older revision		Revision as of 16:22, 7 May 2019
Line 33:		Line 33:
	*Able to lay relatively still for extended periods of time without discomfort		*Able to lay relatively still for extended periods of time without discomfort
	**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>		**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>

			Prescreening scheduling should be done in collaboration with the pool of experimenters who will be running the experiment so that we know what times we can invite prospective participants to the lab. As many as two participants can be scheduled simultaneously.

	===MRI Scheduling===		===MRI Scheduling===

Chris: /* Scheduling: Andrew Hall */

2019-05-07T20:20:03Z

Scheduling: Andrew Hall

← Older revision		Revision as of 16:20, 7 May 2019
Line 13:		Line 13:
	The person responsible for scheduling should always have available the pool of available time slots for any in-lab or MRI appointments. Responsible experimenters should ensure that this pool is kept up-to-date. Interested participants may contact us via the lab gmail email address or the lab phone number. The person responsible for scheduling should check the lab voicemail at least weekly and the gmail account more often, with the goal of replying to interested participants within 1 week of contact.		The person responsible for scheduling should always have available the pool of available time slots for any in-lab or MRI appointments. Responsible experimenters should ensure that this pool is kept up-to-date. Interested participants may contact us via the lab gmail email address or the lab phone number. The person responsible for scheduling should check the lab voicemail at least weekly and the gmail account more often, with the goal of replying to interested participants within 1 week of contact.

			===Initial Scheduling (Prescreening)===
	Initial scheduling for an fMRI experiment should begin by filtering for eligibility to avoid wasting time and money, and only potentially eligible participants should be scheduled for initial prescreening:		Initial scheduling for an fMRI experiment should begin by filtering for eligibility to avoid wasting time and money, and only potentially eligible participants should be scheduled for initial prescreening:
	*<span style="color:green">Healthy adult (18+ years of age) able to give informed consent</span>		*<span style="color:green">Healthy adult (18+ years of age) able to give informed consent</span>
Line 32:		Line 33:
	*Able to lay relatively still for extended periods of time without discomfort		*Able to lay relatively still for extended periods of time without discomfort
	**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>		**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>

			===MRI Scheduling===
			We ideally will scan multiple participants on a given day, usually Sundays. We usually scan after 2 PM, but that can vary. It's also preferred that we schedule a scan two or more weeks in advance. Once we have a small pool of participants who are eligible to be scanned, look ahead to the next available scan date to find the window of scan times that are available. We have recently found that a scan takes about 60 minutes, plus about 15 minutes to prepare. We can therefore have some overlap in participants, where one participant arrives while the previous one is still in the scanner. A suggested timeline might be the following, assuming a start time of 2 PM (14:00):
			13:45: Participant 1 arrives, completes all safety screening sheets and prepares for scanning
			14:00: Participant 1 goes in the scanner
			14:45: Participant 2 arrives, completes all safety screening sheets, and prepares for scanning
			15:00: Participant 1 exits the scanner, Participant 2 goes in the scanner
			15:45: Participant 3 arrives, completes all safety screening sheets and prepares for scanning
			16:00: Participant 2 exits the scanner, Participant 3 goes in the scanner
			...etc., with each successive participant arriving 15 minutes before the next hour.
			Of course, there's sometimes a delay, so with additional participants, later scans might get backed up. But assuming everything goes smoothly, this would be an ideal schedule where we plan to have each participant arrive about 15 minutes before we intend to put them into the scanner.

	==Data Triage and Organization: Unassigned==		==Data Triage and Organization: Unassigned==

Chris: /* fMRI Experiments */

2019-05-07T20:02:27Z

fMRI Experiments

← Older revision		Revision as of 16:02, 7 May 2019
Line 9:		Line 9:
	*Initial training		*Initial training

	=fMRI Experiments=		=fMRI Experiments (SemCat)=
	==Scheduling: Andrew Hall==		==Scheduling: Andrew Hall==
	The person responsible for scheduling should always have available the pool of available time slots for any in-lab or MRI appointments. Responsible experimenters should ensure that this pool is kept up-to-date. Interested participants may contact us via the lab gmail email address or the lab phone number. The person responsible for scheduling should check the lab voicemail at least weekly and the gmail account more often, with the goal of replying to interested participants within 1 week of contact.		The person responsible for scheduling should always have available the pool of available time slots for any in-lab or MRI appointments. Responsible experimenters should ensure that this pool is kept up-to-date. Interested participants may contact us via the lab gmail email address or the lab phone number. The person responsible for scheduling should check the lab voicemail at least weekly and the gmail account more often, with the goal of replying to interested participants within 1 week of contact.

Chris: /* Data Triage */

2019-05-07T19:59:30Z

Data Triage

← Older revision		Revision as of 15:59, 7 May 2019
Line 33:		Line 33:
	**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>		**<span style="color:red">This may preclude individuals with orthopaedic conditions (e.g., back problems)</span>

	==Data Triage==		==Data Triage and Organization: Unassigned==
	Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders		Following a scan, we will have several MRI files and several MATLAB runtime data files for each participant (theoretically: 1 for each completed run). It should be a priority to ensure that these data are transferred to the UBFS/openfmri folders
	===MRI Data===		===MRI Data===