https://www.ccn.ucla.edu/wiki/api.php?action=feedcontributions&user=Soconnell&feedformat=atomCenter for Cognitive Neuroscience - User contributions [en]2024-03-28T08:00:31ZUser contributionsMediaWiki 1.39.3https://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2873EGI2015-01-28T23:06:35Z<p>Soconnell: </p>
<hr />
<div>NetStation 5 Communications:<br />
*[[editing software issues]]<br />
*[[acquisition timing issues]]<br />
<br />
NetStation 4 Communications:<br />
*[[amp timing issues]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Amp_timing_issues&diff=2872Amp timing issues2015-01-28T23:05:43Z<p>Soconnell: </p>
<hr />
<div>Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to supportteam, Wei, me <br />
Hi all. Can you confirm my interpretation of the following statement in the updated advisory. I am to understand that if we used NA300, and NS version 4.5.1 or 4.5.7, then the first column 250 s/s entry should read 8 ms not 36 ms as it currently stands. Furthermore can you confirm that the other entries (specifically 8ms delay for 1000 s/s) for N300 are still correct.<br />
<br />
"Furthermore, we found that for data recorded with Net Station versions 4.4 through 4.5.7, the correction values for the default 250 s/s sampling rate (which is likely used by the majority of customers) is 8 ms"<br />
<br />
Is that correct? This is relatively important to me - as we are in the process of submission corrections to published manuscript and re-processing our data. <br />
Thank you. <br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/2/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
The statement in the Advisory is correct, so let me describe this in another way. With the NA 300, for Net Station 4.4 through 4.5.x, the delay values for 125, 500 and 1000 s/s are correct. For 250 s/s, if you click on this sample rate to select it, then the value in the table is also correct. The exception occurs if your 250 s/s sample rate was the result of using the default sample rate associated with the NA 300 Control Panel. In this particular instance, you should use the 8ms delay value.<br />
<br />
Do let me know if helps clarify the situation or if you have further questions.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to Gaynor, supportteam, Wei, me <br />
Gaynor - How do I know - post-hoc - if the 250 s/s was "selected" or left as such "by default". For all practical purposes these are the same. If the default is on then wouldn't the control panel still show the 250 s/s "selected"?<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/2/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
Unfortunately there is no way for us to determine whether the 250 s/s was clicked to select it or used by default. There is the possibility that we can confirm the delay associated with your recordings by reviewing the latency of the sensory ERP components within your processed data. Would you like us to review your data in this way? If so, do you have a study that used visual stimuli?<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to Gaynor, supportteam, Wei, me <br />
Goodness - ok. So this is a real problem that has no immediate solution and we have to accept that in all/some subjects the onsets are just wrong. For instance let's say an RA opened up the control window, changed temporarily to 1000Hz, then changed it back. Would the result be 8 or 36 ms (b/c of the temporary change in the control panel setting) delay?<br />
Agatha<br />
P.S. I do not require external review of ERPs.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/4/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
In the scenario that you describe, a temporary change to the control panel setting, the result would be the 250 s/s expected delay value of 36 ms. It is only when there is no change to the default use of the 250 s/s sample rate that we see the 8 ms delay. <br />
<br />
I extend my sincere apologies to you for the additional work and frustration this error has caused you. Your second sentence does accurately describe the situation for you, and while I cannot change that I am here to help as much as I can. Please let me know if there is anything I can do.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@g.ucla.edu><br />
12/4/14<br />
<br />
to Gaynor, Agatha, supportteam, Wei, me <br />
Thank you Gaynor for your continued support. This is definitely not great but we'll survive. It should be fixable.<br />
To a smooth 2015 :)<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/5/14<br />
<br />
to Agatha, Agatha, supportteam, Wei, me <br />
Hear, hear … to a smooth 2015 :-)<br />
<br />
Thank you for your understanding, Agatha, it is much appreciated.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Acquisition_timing_issues&diff=2871Acquisition timing issues2015-01-28T23:04:55Z<p>Soconnell: </p>
<hr />
<div>Samantha O'Connell <samroconnell@gmail.com><br />
10/27/14<br />
<br />
to supportteam, Austin <br />
Hi EGI support, <br />
<br />
We're in the process of transitioning Net Station 5 into our EEG testing and have been running into some issues:<br />
<br />
1) We deliver our stimuli and manage our events from MATLAB. With that said, when we send simultaneous events from MATLAB to Net Station, it says in the event log that "events that exist at the same time as existing events will not be added". Is there a way to fix this issue? There are some experiments in our lab that depend in sending simultaneous events and this would present a big problem. This was not an issue that we had with earlier versions of Net Station.<br />
<br />
2) The events that we send to Net Station from MATLAB are recorded properly as they occur in time in the event log; however, when opening the recorded file in Net Station Review, all of the events have the same onset time and occur at the end of the recording, though durations of all events are preserved. We haven't had timing issues in the past and are wondering if there is a set up feature involving timing that we overlooked.<br />
<br />
If you could help us solve these issues, this would be great.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Are you using psychtoolbox? We are investigating a timing issue with the synch method used by Psychtoolbox. Do you have a script known to work with an older version of NS I could test with<br />
<br />
I'll need to investigate a bit more on how you were doing simultaneous events before. That was during acquisition I assume?<br />
<br />
Can you remind me which lab you are at?<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Thanks for your reply!<br />
<br />
Yes - we are using Psychtoolbox. I'll see if Austin (the one having trouble with the simultaneous events) can send you some code. And yes - we were delivering simultaneous events during acquisition.<br />
<br />
We're in Mark Cohen's lab at UCLA.<br />
<br />
Send you some code in a bit.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
I'll need to investigate the issues separately, so if you have an experiment known to run in 4.5 that does not have simultaneous events, that would be perfect.<br />
<br />
Thanks,<br />
<br />
Mark<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Here's a code that works fine in NS 4.5 that's been having timing issues in NS 5. Let us know how it goes. <br />
<br />
Thanks, <br />
Samantha<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Thank you, That's just what I needed.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/29/14<br />
<br />
to me, supportteam, Austin <br />
Dear Sam,<br />
<br />
I have verified your code works in 4.5 but not in 5.0, I've turned the issue over to the programmers and will let you know what a fix is available.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
11/3/14<br />
<br />
to Mark, me, supportteam <br />
Dear Mark,<br />
<br />
I'm a doctoral student working with Mark Cohen. Thank you for looking into our event problem. I'd like to share a few general comments on the new software as well as an interface issue that I've encountered.<br />
<br />
The interface feels much more cohesive and organized now that the various controls have moved from separate windows to a single sidebar. I'm glad that I no longer need to drag things around to search for a lost dialog box. This is a great improvement.<br />
<br />
I'm a big fan of the separate icons for Acquisition/Review/Tools. I also like the "Not Recording" text that shows up over the EEG waveforms; that indicator makes it so much easier to quickly check that things are working. I've noticed small touches like these that give the program a greater sense of polish.<br />
<br />
I do have one issue with the new interface. When the program first starts and whenever the recording stops, Net Station forces you to enter a new patient ID before you can further interact with the software. I assume that this behavior is intended to prevent users from accidentally recording a session without a patient ID. However, this can be rather disruptive, particularly when a user does not intend to save new data. For example, if I want to check the TCP/IP event settings that were in place for a recording that just ended, I first have to enter a patient ID before I can scroll through the control interface, even if I will not record another session. Personally, I would prefer a warning like the "Not Recording" text instead of a required dialog box.<br />
<br />
I recognize that the mandatory patient ID dialog box may be a design choice, but it also causes a bigger problem impacting the operating system as a whole. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). I discovered this bug because I needed to check a file to determine the correct patient ID. However, Finder opened in a window hidden behind Net Station. The top panel showed that Finder was the open application, but there was no way to bring the Finder window into view. My only option was to enter a placeholder patient ID so that I could use Finder before re-entering the correct ID. Perhaps you are aware of this issue, but I wanted to point it out just in case.<br />
<br />
Let me know if you would like any more feedback on these or any other issues.<br />
<br />
Best,<br />
Austin Head<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
11/4/14<br />
<br />
to Austin, me, supportteam <br />
Dear Austin,<br />
<br />
Thank you for the feedback.<br />
<br />
Yes what to do about the patient ID is an open issue, you're not the only person who does not like the current implimentation. I will log your comment into our feature request tracking system<br />
<br />
I'll also log the detail about NS blocking the finder.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/12/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Thank you for your help with the sync timing we've been experiencing with NS5.<br />
<br />
I wanted to check in on the progress of testing out our code with NS5. We're keen to keep working with NS5, but won't be able to make any progress without figuring out this road block.<br />
<br />
Please let us know at your earliest convenience.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/17/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Before we get hit with the holiday season, wanted to check in again and see if there's any updates on the sync issues we were having with NS5 and Psychtoolbox. Please let us know - we're eager to continue testing out the new program<br />
<br />
Thanks,<br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
11/17/14<br />
<br />
to me, Mark, Austin, supportteam, Agatha, Andrew <br />
Dear Sam,<br />
<br />
I am sorry but we do not have an update for you at the moment. We understand the need for this fix, and will provide you with an update as soon as it is made available to us.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Acquisition_timing_issues&diff=2870Acquisition timing issues2015-01-28T23:04:21Z<p>Soconnell: Created page with "Samantha O'Connell <samroconnell@gmail.com> 10/27/14 to supportteam, Austin Hi EGI support, We're in the process of transitioning Net Station 5 into our EEG testing and ha..."</p>
<hr />
<div>Samantha O'Connell <samroconnell@gmail.com><br />
10/27/14<br />
<br />
to supportteam, Austin <br />
Hi EGI support, <br />
<br />
We're in the process of transitioning Net Station 5 into our EEG testing and have been running into some issues:<br />
<br />
1) We deliver our stimuli and manage our events from MATLAB. With that said, when we send simultaneous events from MATLAB to Net Station, it says in the event log that "events that exist at the same time as existing events will not be added". Is there a way to fix this issue? There are some experiments in our lab that depend in sending simultaneous events and this would present a big problem. This was not an issue that we had with earlier versions of Net Station.<br />
<br />
2) The events that we send to Net Station from MATLAB are recorded properly as they occur in time in the event log; however, when opening the recorded file in Net Station Review, all of the events have the same onset time and occur at the end of the recording, though durations of all events are preserved. We haven't had timing issues in the past and are wondering if there is a set up feature involving timing that we overlooked.<br />
<br />
If you could help us solve these issues, this would be great.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Are you using psychtoolbox? We are investigating a timing issue with the synch method used by Psychtoolbox. Do you have a script known to work with an older version of NS I could test with<br />
<br />
I'll need to investigate a bit more on how you were doing simultaneous events before. That was during acquisition I assume?<br />
<br />
Can you remind me which lab you are at?<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Thanks for your reply!<br />
<br />
Yes - we are using Psychtoolbox. I'll see if Austin (the one having trouble with the simultaneous events) can send you some code. And yes - we were delivering simultaneous events during acquisition.<br />
<br />
We're in Mark Cohen's lab at UCLA.<br />
<br />
Send you some code in a bit.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
I'll need to investigate the issues separately, so if you have an experiment known to run in 4.5 that does not have simultaneous events, that would be perfect.<br />
<br />
Thanks,<br />
<br />
Mark<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Here's a code that works fine in NS 4.5 that's been having timing issues in NS 5. Let us know how it goes. <br />
<br />
Thanks, <br />
Samantha<br />
testNS5.m<br />
<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Thank you, That's just what I needed.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/29/14<br />
<br />
to me, supportteam, Austin <br />
Dear Sam,<br />
<br />
I have verified your code works in 4.5 but not in 5.0, I've turned the issue over to the programmers and will let you know what a fix is available.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
11/3/14<br />
<br />
to Mark, me, supportteam <br />
Dear Mark,<br />
<br />
I'm a doctoral student working with Mark Cohen. Thank you for looking into our event problem. I'd like to share a few general comments on the new software as well as an interface issue that I've encountered.<br />
<br />
The interface feels much more cohesive and organized now that the various controls have moved from separate windows to a single sidebar. I'm glad that I no longer need to drag things around to search for a lost dialog box. This is a great improvement.<br />
<br />
I'm a big fan of the separate icons for Acquisition/Review/Tools. I also like the "Not Recording" text that shows up over the EEG waveforms; that indicator makes it so much easier to quickly check that things are working. I've noticed small touches like these that give the program a greater sense of polish.<br />
<br />
I do have one issue with the new interface. When the program first starts and whenever the recording stops, Net Station forces you to enter a new patient ID before you can further interact with the software. I assume that this behavior is intended to prevent users from accidentally recording a session without a patient ID. However, this can be rather disruptive, particularly when a user does not intend to save new data. For example, if I want to check the TCP/IP event settings that were in place for a recording that just ended, I first have to enter a patient ID before I can scroll through the control interface, even if I will not record another session. Personally, I would prefer a warning like the "Not Recording" text instead of a required dialog box.<br />
<br />
I recognize that the mandatory patient ID dialog box may be a design choice, but it also causes a bigger problem impacting the operating system as a whole. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). I discovered this bug because I needed to check a file to determine the correct patient ID. However, Finder opened in a window hidden behind Net Station. The top panel showed that Finder was the open application, but there was no way to bring the Finder window into view. My only option was to enter a placeholder patient ID so that I could use Finder before re-entering the correct ID. Perhaps you are aware of this issue, but I wanted to point it out just in case.<br />
<br />
Let me know if you would like any more feedback on these or any other issues.<br />
<br />
Best,<br />
Austin Head<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
11/4/14<br />
<br />
to Austin, me, supportteam <br />
Dear Austin,<br />
<br />
Thank you for the feedback.<br />
<br />
Yes what to do about the patient ID is an open issue, you're not the only person who does not like the current implimentation. I will log your comment into our feature request tracking system<br />
<br />
I'll also log the detail about NS blocking the finder.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/12/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Thank you for your help with the sync timing we've been experiencing with NS5.<br />
<br />
I wanted to check in on the progress of testing out our code with NS5. We're keen to keep working with NS5, but won't be able to make any progress without figuring out this road block.<br />
<br />
Please let us know at your earliest convenience.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/17/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Before we get hit with the holiday season, wanted to check in again and see if there's any updates on the sync issues we were having with NS5 and Psychtoolbox. Please let us know - we're eager to continue testing out the new program<br />
<br />
Thanks,<br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
11/17/14<br />
<br />
to me, Mark, Austin, supportteam, Agatha, Andrew <br />
Dear Sam,<br />
<br />
I am sorry but we do not have an update for you at the moment. We understand the need for this fix, and will provide you with an update as soon as it is made available to us.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Amp_timing_issues&diff=2869Amp timing issues2015-01-28T22:57:56Z<p>Soconnell: Created page with "Agatha Lenartowicz <alenarto@ucla.edu> 12/2/14 to supportteam, Wei, me Hi all. Can you confirm my interpretation of the following statement in the updated advisory. I am to..."</p>
<hr />
<div>Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to supportteam, Wei, me <br />
Hi all. Can you confirm my interpretation of the following statement in the updated advisory. I am to understand that if we used NA300, and NS version 4.5.1 or 4.5.7, then the first column 250 s/s entry should read 8 ms not 36 ms as it currently stands. Furthermore can you confirm that the other entries (specifically 8ms delay for 1000 s/s) for N300 are still correct.<br />
<br />
"Furthermore, we found that for data recorded with Net Station versions 4.4 through 4.5.7, the correction values for the default 250 s/s sampling rate (which is likely used by the majority of customers) is 8 ms"<br />
<br />
Is that correct? This is relatively important to me - as we are in the process of submission corrections to published manuscript and re-processing our data. <br />
Thank you. <br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/2/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
The statement in the Advisory is correct, so let me describe this in another way. With the NA 300, for Net Station 4.4 through 4.5.x, the delay values for 125, 500 and 1000 s/s are correct. For 250 s/s, if you click on this sample rate to select it, then the value in the table is also correct. The exception occurs if your 250 s/s sample rate was the result of using the default sample rate associated with the NA 300 Control Panel. In this particular instance, you should use the 8ms delay value.<br />
<br />
Do let me know if helps clarify the situation or if you have further questions.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to Gaynor, supportteam, Wei, me <br />
Gaynor - How do I know - post-hoc - if the 250 s/s was "selected" or left as such "by default". For all practical purposes these are the same. If the default is on then wouldn't the control panel still show the 250 s/s "selected"?<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/2/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
Unfortunately there is no way for us to determine whether the 250 s/s was clicked to select it or used by default. There is the possibility that we can confirm the delay associated with your recordings by reviewing the latency of the sensory ERP components within your processed data. Would you like us to review your data in this way? If so, do you have a study that used visual stimuli?<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
12/2/14<br />
<br />
to Gaynor, supportteam, Wei, me <br />
Goodness - ok. So this is a real problem that has no immediate solution and we have to accept that in all/some subjects the onsets are just wrong. For instance let's say an RA opened up the control window, changed temporarily to 1000Hz, then changed it back. Would the result be 8 or 36 ms (b/c of the temporary change in the control panel setting) delay?<br />
Agatha<br />
P.S. I do not require external review of ERPs.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/4/14<br />
<br />
to Agatha, supportteam, Wei, me <br />
Dear Agatha,<br />
<br />
In the scenario that you describe, a temporary change to the control panel setting, the result would be the 250 s/s expected delay value of 36 ms. It is only when there is no change to the default use of the 250 s/s sample rate that we see the 8 ms delay. <br />
<br />
I extend my sincere apologies to you for the additional work and frustration this error has caused you. Your second sentence does accurately describe the situation for you, and while I cannot change that I am here to help as much as I can. Please let me know if there is anything I can do.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@g.ucla.edu><br />
12/4/14<br />
<br />
to Gaynor, Agatha, supportteam, Wei, me <br />
Thank you Gaynor for your continued support. This is definitely not great but we'll survive. It should be fixable.<br />
To a smooth 2015 :)<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
12/5/14<br />
<br />
to Agatha, Agatha, supportteam, Wei, me <br />
Hear, hear … to a smooth 2015 :-)<br />
<br />
Thank you for your understanding, Agatha, it is much appreciated.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2868EGI2015-01-28T22:54:23Z<p>Soconnell: </p>
<hr />
<div>NetStation 5 Communications:<br />
*[[editing software issues]]<br />
*[[acquisition timing issues]]<br />
*[[amp timing issues]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2867Timing issues2015-01-28T22:53:27Z<p>Soconnell: </p>
<hr />
<div><br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/27/14<br />
<br />
to supportteam, Austin <br />
Hi EGI support, <br />
<br />
We're in the process of transitioning Net Station 5 into our EEG testing and have been running into some issues:<br />
<br />
1) We deliver our stimuli and manage our events from MATLAB. With that said, when we send simultaneous events from MATLAB to Net Station, it says in the event log that "events that exist at the same time as existing events will not be added". Is there a way to fix this issue? There are some experiments in our lab that depend in sending simultaneous events and this would present a big problem. This was not an issue that we had with earlier versions of Net Station.<br />
<br />
2) The events that we send to Net Station from MATLAB are recorded properly as they occur in time in the event log; however, when opening the recorded file in Net Station Review, all of the events have the same onset time and occur at the end of the recording, though durations of all events are preserved. We haven't had timing issues in the past and are wondering if there is a set up feature involving timing that we overlooked.<br />
<br />
If you could help us solve these issues, this would be great.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Are you using psychtoolbox? We are investigating a timing issue with the synch method used by Psychtoolbox. Do you have a script known to work with an older version of NS I could test with<br />
<br />
I'll need to investigate a bit more on how you were doing simultaneous events before. That was during acquisition I assume?<br />
<br />
Can you remind me which lab you are at?<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Thanks for your reply!<br />
<br />
Yes - we are using Psychtoolbox. I'll see if Austin (the one having trouble with the simultaneous events) can send you some code. And yes - we were delivering simultaneous events during acquisition.<br />
<br />
We're in Mark Cohen's lab at UCLA.<br />
<br />
Send you some code in a bit.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
I'll need to investigate the issues separately, so if you have an experiment known to run in 4.5 that does not have simultaneous events, that would be perfect.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark <br />
Oh ok - great. Sounds good.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
Attachments10/28/14<br />
<br />
to me <br />
Here's the script. Hold off on sending it; I want to confirm that it<br />
works in 4.5 first.<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Use this version. It works in NS 4.5 just fine.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Austin <br />
Perfect! Thanks Austin!<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Here's a code that works fine in NS 4.5 that's been having timing issues in NS 5. Let us know how it goes. <br />
<br />
Thanks, <br />
Samantha<br />
testNS5.m<br />
<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
I'd like to point out another issue. Whenever the recording stops, NS forces you to enter a new patient ID before you can interact with the program again. This is very disruptive, particularly when a user does not intend to save new data. If I have finished my session, I shouldn't have to enter a new dummy patient ID (e.g. "asdf") just to look scroll down.<br />
<br />
This behavior may be a design choice to prevent users from accidentally running a session without entering the patient ID, but there is a bigger problem. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). The program should never capture focus in that manner. I discovered this bug because I was trying to open Finder to determine the next unused subject number, but the window was not visible. I was forced to enter a placeholder ID so that I could use Finder before re-entering the correct ID.<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Do you want me to email him directly?<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <br />
Yeah, that would be best. Mind sending your email to him?<br />
10/28/14<br />
<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Sure. I'll email him.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Thank you, That's just what I needed.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/29/14<br />
<br />
to me, supportteam, Austin <br />
Dear Sam,<br />
<br />
I have verified your code works in 4.5 but not in 5.0, I've turned the issue over to the programmers and will let you know what a fix is available.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Sam O'Connell <samroconnell@gmail.com><br />
10/30/14<br />
<br />
to Agatha <br />
I guess I can try your code and see if we're running into similar issues, but I'm guessing so because of PTB<br />
<br />
Sam O'Connell<br />
samroconnell@gmail.com<br />
(847) 915-5355<br />
<br />
Staff Research Associate<br />
Staglin Center for Cognitive Neuroscience, UCLA<br />
www.brainmapping.org<br />
Think Now, Inc.<br />
www.think-now.com<br />
<br />
Begin forwarded message:<br />
<br />
From: Mark Moran <mmoran@egi.com><br />
Date: October 29, 2014 at 3:49:46 PM PDT<br />
To: Samantha O'Connell <samroconnell@gmail.com><br />
Cc: "supportteam@egi.com" <supportteam@egi.com>, Austin Head <alheadbme@gmail.com><br />
Subject: Re: NS 5 events<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
10/30/14<br />
<br />
to me <br />
Yes pls do. You ought to get Andrew on this as well.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
11/3/14<br />
<br />
to Mark, me, supportteam <br />
Dear Mark,<br />
<br />
I'm a doctoral student working with Mark Cohen. Thank you for looking into our event problem. I'd like to share a few general comments on the new software as well as an interface issue that I've encountered.<br />
<br />
The interface feels much more cohesive and organized now that the various controls have moved from separate windows to a single sidebar. I'm glad that I no longer need to drag things around to search for a lost dialog box. This is a great improvement.<br />
<br />
I'm a big fan of the separate icons for Acquisition/Review/Tools. I also like the "Not Recording" text that shows up over the EEG waveforms; that indicator makes it so much easier to quickly check that things are working. I've noticed small touches like these that give the program a greater sense of polish.<br />
<br />
I do have one issue with the new interface. When the program first starts and whenever the recording stops, Net Station forces you to enter a new patient ID before you can further interact with the software. I assume that this behavior is intended to prevent users from accidentally recording a session without a patient ID. However, this can be rather disruptive, particularly when a user does not intend to save new data. For example, if I want to check the TCP/IP event settings that were in place for a recording that just ended, I first have to enter a patient ID before I can scroll through the control interface, even if I will not record another session. Personally, I would prefer a warning like the "Not Recording" text instead of a required dialog box.<br />
<br />
I recognize that the mandatory patient ID dialog box may be a design choice, but it also causes a bigger problem impacting the operating system as a whole. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). I discovered this bug because I needed to check a file to determine the correct patient ID. However, Finder opened in a window hidden behind Net Station. The top panel showed that Finder was the open application, but there was no way to bring the Finder window into view. My only option was to enter a placeholder patient ID so that I could use Finder before re-entering the correct ID. Perhaps you are aware of this issue, but I wanted to point it out just in case.<br />
<br />
Let me know if you would like any more feedback on these or any other issues.<br />
<br />
Best,<br />
Austin Head<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
11/4/14<br />
<br />
to Austin, me, supportteam <br />
Dear Austin,<br />
<br />
Thank you for the feedback.<br />
<br />
Yes what to do about the patient ID is an open issue, you're not the only person who does not like the current implimentation. I will log your comment into our feature request tracking system<br />
<br />
I'll also log the detail about NS blocking the finder.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/5/14<br />
<br />
to Andrew <br />
This is to keep you in the loop. We'll need your help<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/12/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Thank you for your help with the sync timing we've been experiencing with NS5.<br />
<br />
I wanted to check in on the progress of testing out our code with NS5. We're keen to keep working with NS5, but won't be able to make any progress without figuring out this road block.<br />
<br />
Please let us know at your earliest convenience.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/17/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Before we get hit with the holiday season, wanted to check in again and see if there's any updates on the sync issues we were having with NS5 and Psychtoolbox. Please let us know - we're eager to continue testing out the new program<br />
<br />
Thanks,<br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
11/17/14<br />
<br />
to me, Mark, Austin, supportteam, Agatha, Andrew <br />
Dear Sam,<br />
<br />
I am sorry but we do not have an update for you at the moment. We understand the need for this fix, and will provide you with an update as soon as it is made available to us.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2866Timing issues2015-01-28T22:52:45Z<p>Soconnell: </p>
<hr />
<div><br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/27/14<br />
<br />
to supportteam, Austin <br />
Hi EGI support, <br />
<br />
We're in the process of transitioning Net Station 5 into our EEG testing and have been running into some issues:<br />
<br />
1) We deliver our stimuli and manage our events from MATLAB. With that said, when we send simultaneous events from MATLAB to Net Station, it says in the event log that "events that exist at the same time as existing events will not be added". Is there a way to fix this issue? There are some experiments in our lab that depend in sending simultaneous events and this would present a big problem. This was not an issue that we had with earlier versions of Net Station.<br />
<br />
2) The events that we send to Net Station from MATLAB are recorded properly as they occur in time in the event log; however, when opening the recorded file in Net Station Review, all of the events have the same onset time and occur at the end of the recording, though durations of all events are preserved. We haven't had timing issues in the past and are wondering if there is a set up feature involving timing that we overlooked.<br />
<br />
If you could help us solve these issues, this would be great.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Are you using psychtoolbox? We are investigating a timing issue with the synch method used by Psychtoolbox. Do you have a script known to work with an older version of NS I could test with<br />
<br />
I'll need to investigate a bit more on how you were doing simultaneous events before. That was during acquisition I assume?<br />
<br />
Can you remind me which lab you are at?<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Thanks for your reply!<br />
<br />
Yes - we are using Psychtoolbox. I'll see if Austin (the one having trouble with the simultaneous events) can send you some code. And yes - we were delivering simultaneous events during acquisition.<br />
<br />
We're in Mark Cohen's lab at UCLA.<br />
<br />
Send you some code in a bit.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
I'll need to investigate the issues separately, so if you have an experiment known to run in 4.5 that does not have simultaneous events, that would be perfect.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark <br />
Oh ok - great. Sounds good.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
Attachments10/28/14<br />
<br />
to me <br />
Here's the script. Hold off on sending it; I want to confirm that it<br />
works in 4.5 first.<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Use this version. It works in NS 4.5 just fine.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Austin <br />
Perfect! Thanks Austin!<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
10/28/14<br />
<br />
to Mark, supportteam, Austin <br />
Hi Mark, <br />
<br />
Here's a code that works fine in NS 4.5 that's been having timing issues in NS 5. Let us know how it goes. <br />
<br />
Thanks, <br />
Samantha<br />
testNS5.m<br />
<br />
<br />
Attachments area<br />
Preview attachment testNS5.m<br />
<br />
Binary File<br />
testNS5.m<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
I'd like to point out another issue. Whenever the recording stops, NS forces you to enter a new patient ID before you can interact with the program again. This is very disruptive, particularly when a user does not intend to save new data. If I have finished my session, I shouldn't have to enter a new dummy patient ID (e.g. "asdf") just to look scroll down.<br />
<br />
This behavior may be a design choice to prevent users from accidentally running a session without entering the patient ID, but there is a bigger problem. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). The program should never capture focus in that manner. I discovered this bug because I was trying to open Finder to determine the next unused subject number, but the window was not visible. I was forced to enter a placeholder ID so that I could use Finder before re-entering the correct ID.<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Do you want me to email him directly?<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <br />
Yeah, that would be best. Mind sending your email to him?<br />
10/28/14<br />
<br />
Austin Head <alheadbme@gmail.com><br />
10/28/14<br />
<br />
to me <br />
Sure. I'll email him.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/28/14<br />
<br />
to me, supportteam, Austin <br />
Dear Samantha,<br />
<br />
Thank you, That's just what I needed.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
10/29/14<br />
<br />
to me, supportteam, Austin <br />
Dear Sam,<br />
<br />
I have verified your code works in 4.5 but not in 5.0, I've turned the issue over to the programmers and will let you know what a fix is available.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Sam O'Connell <samroconnell@gmail.com><br />
10/30/14<br />
<br />
to Agatha <br />
I guess I can try your code and see if we're running into similar issues, but I'm guessing so because of PTB<br />
<br />
Sam O'Connell<br />
samroconnell@gmail.com<br />
(847) 915-5355<br />
<br />
Staff Research Associate<br />
Staglin Center for Cognitive Neuroscience, UCLA<br />
www.brainmapping.org<br />
Think Now, Inc.<br />
www.think-now.com<br />
<br />
Begin forwarded message:<br />
<br />
From: Mark Moran <mmoran@egi.com><br />
Date: October 29, 2014 at 3:49:46 PM PDT<br />
To: Samantha O'Connell <samroconnell@gmail.com><br />
Cc: "supportteam@egi.com" <supportteam@egi.com>, Austin Head <alheadbme@gmail.com><br />
Subject: Re: NS 5 events<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
10/30/14<br />
<br />
to me <br />
Yes pls do. You ought to get Andrew on this as well.<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Austin Head <alheadbme@gmail.com><br />
11/3/14<br />
<br />
to Mark, me, supportteam <br />
Dear Mark,<br />
<br />
I'm a doctoral student working with Mark Cohen. Thank you for looking into our event problem. I'd like to share a few general comments on the new software as well as an interface issue that I've encountered.<br />
<br />
The interface feels much more cohesive and organized now that the various controls have moved from separate windows to a single sidebar. I'm glad that I no longer need to drag things around to search for a lost dialog box. This is a great improvement.<br />
<br />
I'm a big fan of the separate icons for Acquisition/Review/Tools. I also like the "Not Recording" text that shows up over the EEG waveforms; that indicator makes it so much easier to quickly check that things are working. I've noticed small touches like these that give the program a greater sense of polish.<br />
<br />
I do have one issue with the new interface. When the program first starts and whenever the recording stops, Net Station forces you to enter a new patient ID before you can further interact with the software. I assume that this behavior is intended to prevent users from accidentally recording a session without a patient ID. However, this can be rather disruptive, particularly when a user does not intend to save new data. For example, if I want to check the TCP/IP event settings that were in place for a recording that just ended, I first have to enter a patient ID before I can scroll through the control interface, even if I will not record another session. Personally, I would prefer a warning like the "Not Recording" text instead of a required dialog box.<br />
<br />
I recognize that the mandatory patient ID dialog box may be a design choice, but it also causes a bigger problem impacting the operating system as a whole. The prompt for the patient ID causes Net Station to remain as the topmost window even if users click to other programs (including Finder, Safari, System Preferences, etc.). I discovered this bug because I needed to check a file to determine the correct patient ID. However, Finder opened in a window hidden behind Net Station. The top panel showed that Finder was the open application, but there was no way to bring the Finder window into view. My only option was to enter a placeholder patient ID so that I could use Finder before re-entering the correct ID. Perhaps you are aware of this issue, but I wanted to point it out just in case.<br />
<br />
Let me know if you would like any more feedback on these or any other issues.<br />
<br />
Best,<br />
Austin Head<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Mark Moran <mmoran@egi.com><br />
11/4/14<br />
<br />
to Austin, me, supportteam <br />
Dear Austin,<br />
<br />
Thank you for the feedback.<br />
<br />
Yes what to do about the patient ID is an open issue, you're not the only person who does not like the current implimentation. I will log your comment into our feature request tracking system<br />
<br />
I'll also log the detail about NS blocking the finder.<br />
<br />
Thanks,<br />
<br />
Mark<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/5/14<br />
<br />
to Andrew <br />
This is to keep you in the loop. We'll need your help<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/12/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Thank you for your help with the sync timing we've been experiencing with NS5.<br />
<br />
I wanted to check in on the progress of testing out our code with NS5. We're keen to keep working with NS5, but won't be able to make any progress without figuring out this road block.<br />
<br />
Please let us know at your earliest convenience.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/17/14<br />
<br />
to Mark, Austin, supportteam, Agatha, Andrew <br />
Hi Mark, <br />
<br />
Before we get hit with the holiday season, wanted to check in again and see if there's any updates on the sync issues we were having with NS5 and Psychtoolbox. Please let us know - we're eager to continue testing out the new program<br />
<br />
Thanks,<br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Gaynor Foster <gfoster@egi.com><br />
11/17/14<br />
<br />
to me, Mark, Austin, supportteam, Agatha, Andrew <br />
Dear Sam,<br />
<br />
I am sorry but we do not have an update for you at the moment. We understand the need for this fix, and will provide you with an update as soon as it is made available to us.<br />
<br />
Best Wishes,<br />
Gaynor<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Editing_software_issues&diff=2865Editing software issues2015-01-28T22:47:46Z<p>Soconnell: </p>
<hr />
<div>Sanders, Andrew J. <AJSanders@mednet.ucla.edu><br />
11/24/14<br />
<br />
Hi Samantha,<br />
<br />
I am emailing because I remember you mentioning your lab is beginning to use Netstation 5.<br />
<br />
Our collaborators in Boston have run into some issues with processing in Netstation 5 and are looking to see if others are experiencing similar issues.<br />
<br />
Would you mind answering some of their questions, or putting them in contact with someone in your lab who may be more familiar with processing in NS5?<br />
<br />
Thanks!!<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 2:02 PM, Jeste, Shafali M.D. wrote:<br />
<br />
NO and this is intentional :) However my collaborator Mark Cohen is, and I’m sure would be happy to talk with you. <br />
I’m cc’ing Andrew who can connect you to the right person in his lab.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 1:11 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Shefali, <br />
Hope you are hanging in there with the U19 stuff. Thanks so much for all your help last week while you were out of the country!<br />
<br />
Quick question: Has your lab been using Netstation 5 at all yet? <br />
<br />
We're trying to set up a new system in my lab in Boston and have run into some issues with processing and just wanted to see if other users are experiencing similar things. <br />
<br />
Thanks, <br />
Susan <br />
<br />
-- <br />
Susan Faja, Ph.D. <br />
Labs of Cognitive Neuroscience | BCH3178<br />
Boston Children’s Hospital | 1 Autumn Street | AU459 | Boston, MA 02215 <br />
617-919-4486 | susan.faja@childrens.harvard.edu<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/25/14<br />
<br />
to Andrew, Susan, Tessa, Shafali <br />
Hi Andrew, <br />
<br />
We have not gotten to the stage of processing data as of yet - we've been having data collection timing issues with Psychtoolbox and NS5. Because we haven't collected data accurately yet, we haven't looked into processing.<br />
<br />
If I can hear what kind of processing issues your collaborators have been having, I can address those to Mark Moran, our connect at EGI. It'll be good for us to know of these issues as well, for we're looking to do some processing using NetStation5 once we have it up and running.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Jeste, Shafali M.D. <SJeste@mednet.ucla.edu><br />
11/26/14<br />
<br />
to Susan, me, Andrew, Tessa <br />
UGH this sounds painful. However it is also a reality that we all will have to switch at some point, so working through the growing pains together will be helpful. I was just able to convince them to sell me another net amps 300, but they will only sell it with NS5 due to the computer/mac issues. However we are trying to scheme ways to work around that issue as I prefer to stick with 4.5 for now.<br />
<br />
At some point a work group on this will probably be in order.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 25, 2014, at 11:18 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Sam et al.,<br />
We've been in touch with Mark Moran and EGI support a lot as we've had a whole slew of processing problems. <br />
I won't go into detail about our 'important but not critical list', but would be happy to send more if it's helpful. Some of the most critical issues are:<br />
<br />
1) Temporal relations have been removed from the Segmentation Tool - this means that you can only segment to 1 thing and it just becomes 0 in your segment. In NS 4, we typically segmented to stim, but also pulled in criteria related to the accuracy and type of the previous trial. This is no longer a possibility. We also used a photocel during our acquisition to confirm timing and segmented to stim + DIN. Also no longer an option. Mark worked with us for about a week on a workaround. I ended up reprogramming. Mark tells us that EGI decided that NS users don't need temporal relations, but that he continues to lobby for it. If you would like to see this feature, please let him know we're not the only lab that used it. <br />
<br />
2) The bad trials from artifact detection get reincorporated in later processing steps. (i.e. they don't stay bad). EGI is aware of this bug and telling us it'll be corrected in a later version. <br />
<br />
3) NS averaging tool doesn't work - all the channels get marked as bad and zeroed out. Again, EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
4) NS 5 doesn't have stat extraction. EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
Re. 3 & 4, EGI recently told us that it's not been a problem for their other users because they are simply not processing in NS 5. This seemed bizarre to us. We are trying to unpack this by reaching out to labs that have EGI systems to see whether they are using 5 yet and what alternatives they've come up with. (We've also been on the EGI user group to learn about exporting to Matlab for ERPlab. The EEG signal exports, but it's unclear whether the NS tags can be exported--We're following up on some very cumbersome workarounds from John Richards who posted today). <br />
<br />
Tessa, feel free to chime in if I have missed anything critical in this summary. <br />
<br />
Thanks so much for letting us know where you are at with things and let us know if we can be helpful. <br />
<br />
-Susan <br />
<br />
p.s. Shefali, thanks! When I arrived in Boston, NA400 and NS5 were the only products shipping from Eugene. We get so sad when we see NS4 on Chuck's computers now. Oh the good old days...<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Faja, Susan <Susan.Faja@childrens.harvard.edu><br />
11/26/14<br />
<br />
to Shafali, me, Andrew, Tessa <br />
Thanks Shefali, <br />
I'm really happy to share my experiences if it can benefit others. (Sara W and Adam Naples have heard a fair amount and, of course, Chuck is in the loop). <br />
I think researchers using EGI will definitely need to stick together as we suspect they may be moving more toward clinical customers. <br />
<br />
Have a wonderful Thanksgiving, <br />
Susan <br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Susan, Shafali, Andrew, Tessa <br />
Hi Susan, <br />
<br />
Thanks for the input - I'll forward this over to my colleagues so they have a sense of what's going on, too. It's really too bad that there's been so many issues with NS5 on both the acquisition and processing ends, and I hope that they'll figure this all out soon. I really appreciate that you took the time to share. I'll be sure to let you know if anything comes up.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Agatha, Andrew, Austin, Edward <br />
A colleague collaborating with Shafali in Boston has been working with NS5's processing software and it looks a little grim - see her outline below of the problems they've been encountering as well.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
11/26/14<br />
<br />
to me, Andrew, Austin, Edward <br />
Thanks very much Sam - this is all reason to not process in NS5 for us. Though of course any issues pertaining to collecting and extracting data are relevant.<br />
<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2864Timing issues2015-01-28T22:47:25Z<p>Soconnell: Replaced content with " <div style="text-align: center; border: 1px dotted gray;">Return to EGI main page</div>"</p>
<hr />
<div><br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2863Timing issues2015-01-28T22:47:04Z<p>Soconnell: </p>
<hr />
<div>Sanders, Andrew J. <AJSanders@mednet.ucla.edu><br />
11/24/14<br />
<br />
Hi Samantha,<br />
<br />
I am emailing because I remember you mentioning your lab is beginning to use Netstation 5.<br />
<br />
Our collaborators in Boston have run into some issues with processing in Netstation 5 and are looking to see if others are experiencing similar issues.<br />
<br />
Would you mind answering some of their questions, or putting them in contact with someone in your lab who may be more familiar with processing in NS5?<br />
<br />
Thanks!!<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 2:02 PM, Jeste, Shafali M.D. wrote:<br />
<br />
NO and this is intentional :) However my collaborator Mark Cohen is, and I’m sure would be happy to talk with you. <br />
I’m cc’ing Andrew who can connect you to the right person in his lab.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 1:11 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Shefali, <br />
Hope you are hanging in there with the U19 stuff. Thanks so much for all your help last week while you were out of the country!<br />
<br />
Quick question: Has your lab been using Netstation 5 at all yet? <br />
<br />
We're trying to set up a new system in my lab in Boston and have run into some issues with processing and just wanted to see if other users are experiencing similar things. <br />
<br />
Thanks, <br />
Susan <br />
<br />
-- <br />
Susan Faja, Ph.D. <br />
Labs of Cognitive Neuroscience | BCH3178<br />
Boston Children’s Hospital | 1 Autumn Street | AU459 | Boston, MA 02215 <br />
617-919-4486 | susan.faja@childrens.harvard.edu<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/25/14<br />
<br />
to Andrew, Susan, Tessa, Shafali <br />
Hi Andrew, <br />
<br />
We have not gotten to the stage of processing data as of yet - we've been having data collection timing issues with Psychtoolbox and NS5. Because we haven't collected data accurately yet, we haven't looked into processing.<br />
<br />
If I can hear what kind of processing issues your collaborators have been having, I can address those to Mark Moran, our connect at EGI. It'll be good for us to know of these issues as well, for we're looking to do some processing using NetStation5 once we have it up and running.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Jeste, Shafali M.D. <SJeste@mednet.ucla.edu><br />
11/26/14<br />
<br />
to Susan, me, Andrew, Tessa <br />
UGH this sounds painful. However it is also a reality that we all will have to switch at some point, so working through the growing pains together will be helpful. I was just able to convince them to sell me another net amps 300, but they will only sell it with NS5 due to the computer/mac issues. However we are trying to scheme ways to work around that issue as I prefer to stick with 4.5 for now.<br />
<br />
At some point a work group on this will probably be in order.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 25, 2014, at 11:18 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Sam et al.,<br />
We've been in touch with Mark Moran and EGI support a lot as we've had a whole slew of processing problems. <br />
I won't go into detail about our 'important but not critical list', but would be happy to send more if it's helpful. Some of the most critical issues are:<br />
<br />
1) Temporal relations have been removed from the Segmentation Tool - this means that you can only segment to 1 thing and it just becomes 0 in your segment. In NS 4, we typically segmented to stim, but also pulled in criteria related to the accuracy and type of the previous trial. This is no longer a possibility. We also used a photocel during our acquisition to confirm timing and segmented to stim + DIN. Also no longer an option. Mark worked with us for about a week on a workaround. I ended up reprogramming. Mark tells us that EGI decided that NS users don't need temporal relations, but that he continues to lobby for it. If you would like to see this feature, please let him know we're not the only lab that used it. <br />
<br />
2) The bad trials from artifact detection get reincorporated in later processing steps. (i.e. they don't stay bad). EGI is aware of this bug and telling us it'll be corrected in a later version. <br />
<br />
3) NS averaging tool doesn't work - all the channels get marked as bad and zeroed out. Again, EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
4) NS 5 doesn't have stat extraction. EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
Re. 3 & 4, EGI recently told us that it's not been a problem for their other users because they are simply not processing in NS 5. This seemed bizarre to us. We are trying to unpack this by reaching out to labs that have EGI systems to see whether they are using 5 yet and what alternatives they've come up with. (We've also been on the EGI user group to learn about exporting to Matlab for ERPlab. The EEG signal exports, but it's unclear whether the NS tags can be exported--We're following up on some very cumbersome workarounds from John Richards who posted today). <br />
<br />
Tessa, feel free to chime in if I have missed anything critical in this summary. <br />
<br />
Thanks so much for letting us know where you are at with things and let us know if we can be helpful. <br />
<br />
-Susan <br />
<br />
p.s. Shefali, thanks! When I arrived in Boston, NA400 and NS5 were the only products shipping from Eugene. We get so sad when we see NS4 on Chuck's computers now. Oh the good old days...<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Faja, Susan <Susan.Faja@childrens.harvard.edu><br />
11/26/14<br />
<br />
to Shafali, me, Andrew, Tessa <br />
Thanks Shefali, <br />
I'm really happy to share my experiences if it can benefit others. (Sara W and Adam Naples have heard a fair amount and, of course, Chuck is in the loop). <br />
I think researchers using EGI will definitely need to stick together as we suspect they may be moving more toward clinical customers. <br />
<br />
Have a wonderful Thanksgiving, <br />
Susan <br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Susan, Shafali, Andrew, Tessa <br />
Hi Susan, <br />
<br />
Thanks for the input - I'll forward this over to my colleagues so they have a sense of what's going on, too. It's really too bad that there's been so many issues with NS5 on both the acquisition and processing ends, and I hope that they'll figure this all out soon. I really appreciate that you took the time to share. I'll be sure to let you know if anything comes up.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Agatha, Andrew, Austin, Edward <br />
A colleague collaborating with Shafali in Boston has been working with NS5's processing software and it looks a little grim - see her outline below of the problems they've been encountering as well.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
11/26/14<br />
<br />
to me, Andrew, Austin, Edward <br />
Thanks very much Sam - this is all reason to not process in NS5 for us. Though of course any issues pertaining to collecting and extracting data are relevant.<br />
<br />
<div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Editing_software_issues&diff=2862Editing software issues2015-01-28T22:46:30Z<p>Soconnell: Created page with "<div style="text-align: center; border: 1px dotted gray;">Return to EGI main page</div>"</p>
<hr />
<div><div style="text-align: center; border: 1px dotted gray;">Return to [[EGI]] main page</div></div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2861EGI2015-01-28T22:42:50Z<p>Soconnell: </p>
<hr />
<div>NetStation 5 Communications:<br />
*[[editing software issues]]<br />
*[[timing issues]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2860Timing issues2015-01-28T22:40:57Z<p>Soconnell: </p>
<hr />
<div>Sanders, Andrew J. <AJSanders@mednet.ucla.edu><br />
11/24/14<br />
<br />
Hi Samantha,<br />
<br />
I am emailing because I remember you mentioning your lab is beginning to use Netstation 5.<br />
<br />
Our collaborators in Boston have run into some issues with processing in Netstation 5 and are looking to see if others are experiencing similar issues.<br />
<br />
Would you mind answering some of their questions, or putting them in contact with someone in your lab who may be more familiar with processing in NS5?<br />
<br />
Thanks!!<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 2:02 PM, Jeste, Shafali M.D. wrote:<br />
<br />
NO and this is intentional :) However my collaborator Mark Cohen is, and I’m sure would be happy to talk with you. <br />
I’m cc’ing Andrew who can connect you to the right person in his lab.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 24, 2014, at 1:11 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Shefali, <br />
Hope you are hanging in there with the U19 stuff. Thanks so much for all your help last week while you were out of the country!<br />
<br />
Quick question: Has your lab been using Netstation 5 at all yet? <br />
<br />
We're trying to set up a new system in my lab in Boston and have run into some issues with processing and just wanted to see if other users are experiencing similar things. <br />
<br />
Thanks, <br />
Susan <br />
<br />
-- <br />
Susan Faja, Ph.D. <br />
Labs of Cognitive Neuroscience | BCH3178<br />
Boston Children’s Hospital | 1 Autumn Street | AU459 | Boston, MA 02215 <br />
617-919-4486 | susan.faja@childrens.harvard.edu<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/25/14<br />
<br />
to Andrew, Susan, Tessa, Shafali <br />
Hi Andrew, <br />
<br />
We have not gotten to the stage of processing data as of yet - we've been having data collection timing issues with Psychtoolbox and NS5. Because we haven't collected data accurately yet, we haven't looked into processing.<br />
<br />
If I can hear what kind of processing issues your collaborators have been having, I can address those to Mark Moran, our connect at EGI. It'll be good for us to know of these issues as well, for we're looking to do some processing using NetStation5 once we have it up and running.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Jeste, Shafali M.D. <SJeste@mednet.ucla.edu><br />
11/26/14<br />
<br />
to Susan, me, Andrew, Tessa <br />
UGH this sounds painful. However it is also a reality that we all will have to switch at some point, so working through the growing pains together will be helpful. I was just able to convince them to sell me another net amps 300, but they will only sell it with NS5 due to the computer/mac issues. However we are trying to scheme ways to work around that issue as I prefer to stick with 4.5 for now.<br />
<br />
At some point a work group on this will probably be in order.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
On Nov 25, 2014, at 11:18 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Sam et al.,<br />
We've been in touch with Mark Moran and EGI support a lot as we've had a whole slew of processing problems. <br />
I won't go into detail about our 'important but not critical list', but would be happy to send more if it's helpful. Some of the most critical issues are:<br />
<br />
1) Temporal relations have been removed from the Segmentation Tool - this means that you can only segment to 1 thing and it just becomes 0 in your segment. In NS 4, we typically segmented to stim, but also pulled in criteria related to the accuracy and type of the previous trial. This is no longer a possibility. We also used a photocel during our acquisition to confirm timing and segmented to stim + DIN. Also no longer an option. Mark worked with us for about a week on a workaround. I ended up reprogramming. Mark tells us that EGI decided that NS users don't need temporal relations, but that he continues to lobby for it. If you would like to see this feature, please let him know we're not the only lab that used it. <br />
<br />
2) The bad trials from artifact detection get reincorporated in later processing steps. (i.e. they don't stay bad). EGI is aware of this bug and telling us it'll be corrected in a later version. <br />
<br />
3) NS averaging tool doesn't work - all the channels get marked as bad and zeroed out. Again, EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
4) NS 5 doesn't have stat extraction. EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
Re. 3 & 4, EGI recently told us that it's not been a problem for their other users because they are simply not processing in NS 5. This seemed bizarre to us. We are trying to unpack this by reaching out to labs that have EGI systems to see whether they are using 5 yet and what alternatives they've come up with. (We've also been on the EGI user group to learn about exporting to Matlab for ERPlab. The EEG signal exports, but it's unclear whether the NS tags can be exported--We're following up on some very cumbersome workarounds from John Richards who posted today). <br />
<br />
Tessa, feel free to chime in if I have missed anything critical in this summary. <br />
<br />
Thanks so much for letting us know where you are at with things and let us know if we can be helpful. <br />
<br />
-Susan <br />
<br />
p.s. Shefali, thanks! When I arrived in Boston, NA400 and NS5 were the only products shipping from Eugene. We get so sad when we see NS4 on Chuck's computers now. Oh the good old days...<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Faja, Susan <Susan.Faja@childrens.harvard.edu><br />
11/26/14<br />
<br />
to Shafali, me, Andrew, Tessa <br />
Thanks Shefali, <br />
I'm really happy to share my experiences if it can benefit others. (Sara W and Adam Naples have heard a fair amount and, of course, Chuck is in the loop). <br />
I think researchers using EGI will definitely need to stick together as we suspect they may be moving more toward clinical customers. <br />
<br />
Have a wonderful Thanksgiving, <br />
Susan <br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Susan, Shafali, Andrew, Tessa <br />
Hi Susan, <br />
<br />
Thanks for the input - I'll forward this over to my colleagues so they have a sense of what's going on, too. It's really too bad that there's been so many issues with NS5 on both the acquisition and processing ends, and I hope that they'll figure this all out soon. I really appreciate that you took the time to share. I'll be sure to let you know if anything comes up.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Agatha, Andrew, Austin, Edward <br />
A colleague collaborating with Shafali in Boston has been working with NS5's processing software and it looks a little grim - see her outline below of the problems they've been encountering as well.<br />
<br />
Thanks, <br />
Sam<br />
<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
11/26/14<br />
<br />
to me, Andrew, Austin, Edward <br />
Thanks very much Sam - this is all reason to not process in NS5 for us. Though of course any issues pertaining to collecting and extracting data are relevant.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Timing_issues&diff=2859Timing issues2015-01-28T22:38:27Z<p>Soconnell: Created page with "Sanders, Andrew J. <AJSanders@mednet.ucla.edu> 11/24/14 Hi Samantha, I am emailing because I remember you mentioning your lab is beginning to use Netstation 5. Our collabor..."</p>
<hr />
<div>Sanders, Andrew J. <AJSanders@mednet.ucla.edu><br />
11/24/14<br />
<br />
Hi Samantha,<br />
<br />
I am emailing because I remember you mentioning your lab is beginning to use Netstation 5.<br />
<br />
Our collaborators in Boston have run into some issues with processing in Netstation 5 and are looking to see if others are experiencing similar issues.<br />
<br />
Would you mind answering some of their questions, or putting them in contact with someone in your lab who may be more familiar with processing in NS5?<br />
<br />
Thanks!!<br />
On Nov 24, 2014, at 2:02 PM, Jeste, Shafali M.D. wrote:<br />
<br />
NO and this is intentional :) However my collaborator Mark Cohen is, and I’m sure would be happy to talk with you. <br />
I’m cc’ing Andrew who can connect you to the right person in his lab.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
<br />
On Nov 24, 2014, at 1:11 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Shefali, <br />
Hope you are hanging in there with the U19 stuff. Thanks so much for all your help last week while you were out of the country!<br />
<br />
Quick question: Has your lab been using Netstation 5 at all yet? <br />
<br />
We're trying to set up a new system in my lab in Boston and have run into some issues with processing and just wanted to see if other users are experiencing similar things. <br />
<br />
Thanks, <br />
Susan <br />
<br />
-- <br />
Susan Faja, Ph.D. <br />
Labs of Cognitive Neuroscience | BCH3178<br />
Boston Children’s Hospital | 1 Autumn Street | AU459 | Boston, MA 02215 <br />
617-919-4486 | susan.faja@childrens.harvard.edu<br />
<br />
<br />
<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/25/14<br />
<br />
to Andrew, Susan, Tessa, Shafali <br />
Hi Andrew, <br />
<br />
We have not gotten to the stage of processing data as of yet - we've been having data collection timing issues with Psychtoolbox and NS5. Because we haven't collected data accurately yet, we haven't looked into processing.<br />
<br />
If I can hear what kind of processing issues your collaborators have been having, I can address those to Mark Moran, our connect at EGI. It'll be good for us to know of these issues as well, for we're looking to do some processing using NetStation5 once we have it up and running.<br />
<br />
Thanks, <br />
Sam<br />
<br />
<br />
Jeste, Shafali M.D. <SJeste@mednet.ucla.edu><br />
11/26/14<br />
<br />
to Susan, me, Andrew, Tessa <br />
UGH this sounds painful. However it is also a reality that we all will have to switch at some point, so working through the growing pains together will be helpful. I was just able to convince them to sell me another net amps 300, but they will only sell it with NS5 due to the computer/mac issues. However we are trying to scheme ways to work around that issue as I prefer to stick with 4.5 for now.<br />
<br />
At some point a work group on this will probably be in order.<br />
<br />
SSJ<br />
<br />
Shafali Spurling Jeste, MD<br />
Assistant Professor in Psychiatry and Biobehavioral Sciences<br />
UCLA David Geffen School of Medicine<br />
Director, Electrophysiology Core<br />
UCLA Center for Autism Research and Treatment<br />
760 Westwood Plaza<br />
Semel Institute, Room 68-237B<br />
lab: 310-825-2761<br />
clinic: 310-794-4008<br />
<br />
On Nov 25, 2014, at 11:18 PM, Faja, Susan <Susan.Faja@childrens.harvard.edu> wrote:<br />
<br />
Hi Sam et al.,<br />
We've been in touch with Mark Moran and EGI support a lot as we've had a whole slew of processing problems. <br />
I won't go into detail about our 'important but not critical list', but would be happy to send more if it's helpful. Some of the most critical issues are:<br />
<br />
1) Temporal relations have been removed from the Segmentation Tool - this means that you can only segment to 1 thing and it just becomes 0 in your segment. In NS 4, we typically segmented to stim, but also pulled in criteria related to the accuracy and type of the previous trial. This is no longer a possibility. We also used a photocel during our acquisition to confirm timing and segmented to stim + DIN. Also no longer an option. Mark worked with us for about a week on a workaround. I ended up reprogramming. Mark tells us that EGI decided that NS users don't need temporal relations, but that he continues to lobby for it. If you would like to see this feature, please let him know we're not the only lab that used it. <br />
<br />
2) The bad trials from artifact detection get reincorporated in later processing steps. (i.e. they don't stay bad). EGI is aware of this bug and telling us it'll be corrected in a later version. <br />
<br />
3) NS averaging tool doesn't work - all the channels get marked as bad and zeroed out. Again, EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
4) NS 5 doesn't have stat extraction. EGI is aware of this and telling us it'll be corrected in a later version. <br />
<br />
Re. 3 & 4, EGI recently told us that it's not been a problem for their other users because they are simply not processing in NS 5. This seemed bizarre to us. We are trying to unpack this by reaching out to labs that have EGI systems to see whether they are using 5 yet and what alternatives they've come up with. (We've also been on the EGI user group to learn about exporting to Matlab for ERPlab. The EEG signal exports, but it's unclear whether the NS tags can be exported--We're following up on some very cumbersome workarounds from John Richards who posted today). <br />
<br />
Tessa, feel free to chime in if I have missed anything critical in this summary. <br />
<br />
Thanks so much for letting us know where you are at with things and let us know if we can be helpful. <br />
<br />
-Susan <br />
<br />
p.s. Shefali, thanks! When I arrived in Boston, NA400 and NS5 were the only products shipping from Eugene. We get so sad when we see NS4 on Chuck's computers now. Oh the good old days...<br />
<br />
<br />
From: Samantha O'Connell [samroconnell@gmail.com]<br />
Sent: Tuesday, November 25, 2014 2:02 PM<br />
To: Sanders, Andrew J.<br />
Cc: Faja, Susan; Clarkson, Tessa; Jeste, Shafali M.D.<br />
Subject: Re: EGI question<br />
<br />
<br />
Faja, Susan <Susan.Faja@childrens.harvard.edu><br />
11/26/14<br />
<br />
to Shafali, me, Andrew, Tessa <br />
Thanks Shefali, <br />
I'm really happy to share my experiences if it can benefit others. (Sara W and Adam Naples have heard a fair amount and, of course, Chuck is in the loop). <br />
I think researchers using EGI will definitely need to stick together as we suspect they may be moving more toward clinical customers. <br />
<br />
Have a wonderful Thanksgiving, <br />
Susan <br />
<br />
From: <Jeste>, "Shafali M.D." <SJeste@mednet.ucla.edu><br />
Date: Wednesday, November 26, 2014 3:19 AM<br />
To: Susan Faja <susan.faja@childrens.harvard.edu><br />
Cc: Samantha O'Connell <samroconnell@gmail.com>, "Sanders, Andrew J." <AJSanders@mednet.ucla.edu>, "Clarkson, Tessa" <Tessa.Clarkson@childrens.harvard.edu><br />
Subject: Re: EGI question<br />
<br />
<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Susan, Shafali, Andrew, Tessa <br />
Hi Susan, <br />
<br />
Thanks for the input - I'll forward this over to my colleagues so they have a sense of what's going on, too. It's really too bad that there's been so many issues with NS5 on both the acquisition and processing ends, and I hope that they'll figure this all out soon. I really appreciate that you took the time to share. I'll be sure to let you know if anything comes up.<br />
<br />
Thanks, <br />
Sam<br />
<br />
<br />
Samantha O'Connell <samroconnell@gmail.com><br />
11/26/14<br />
<br />
to Agatha, Andrew, Austin, Edward <br />
A colleague collaborating with Shafali in Boston has been working with NS5's processing software and it looks a little grim - see her outline below of the problems they've been encountering as well.<br />
<br />
Thanks, <br />
Sam<br />
<br />
<br />
Agatha Lenartowicz <alenarto@ucla.edu><br />
11/26/14<br />
<br />
to me, Andrew, Austin, Edward <br />
Thanks very much Sam - this is all reason to not process in NS5 for us. Though of course any issues pertaining to collecting and extracting data are relevant.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2858EGI2015-01-28T22:35:31Z<p>Soconnell: </p>
<hr />
<div>NetStation 5 Communications:<br />
*[[timing issues]]<br />
*[[editing software issues]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2857EGI2015-01-28T22:14:30Z<p>Soconnell: /* NetStation 5 Communications */</p>
<hr />
<div>NetStation 5 Communications:</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EGI&diff=2856EGI2015-01-28T22:14:11Z<p>Soconnell: Created page with "=NetStation 5 Communications="</p>
<hr />
<div>=NetStation 5 Communications=</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EEG&diff=2855EEG2015-01-28T22:13:40Z<p>Soconnell: </p>
<hr />
<div>A collection of information about EEG data from collection to processing/analysis.<br />
<br />
<br />
<br />
==Collection==<br />
How do you even get EEG data?<br />
<br />
===Staglin===<br />
The [http://www.semel.ucla.edu/staglin Staglin IMHRO Center for Cognitive Neuroscience] is our main EEG data collection facility. Go here to learn how data collection works at the Staglin Center.<br />
*[[StaglinCenter:EEG]]<br />
<br />
===EEG/FMRI===<br />
Concurrent data collection of EEG and FMRI is possible at the Staglin Center.<br />
*[[StaglinCenter:EEG-FMRI]]<br />
<br />
===Transfer===<br />
For now you have to move data by sneaker-net from the acquisition computers to your computer. We may automate this process in the future.<br />
<br />
<br />
==Directory Structure==<br />
Standards are important. And we're hoping to have standards about how our EEG data is kept?<br />
*[[EEG:DirectoryStructure]]<br />
<br />
<br />
<br />
==Processing==<br />
How to process EEG data.<br />
*[[General Pre-Processing Steps]]<br />
<br />
===Programs for EEG data processing===<br />
*[[Netstation]]<br />
*[[BrainVision Analyzer]]<br />
*[[EEGLAB]]<br />
<br />
===ICA===<br />
Independent Component Analysis<br />
*[[EEG:Processing:ICA]]<br />
<br />
===Source===<br />
Source localization.<br />
*[[EEG:Processing:Source]]<br />
<br />
*[[Under Construction]]<br />
<br />
== Support ==<br />
*[[EGI]]<br />
<br />
== History ==<br />
<br />
*[[EEG fMRI noise 2011]]<br />
*[[EEG Net Names]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2742FNIRS2014-08-12T00:19:18Z<p>Soconnell: /* Manuals */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
*[[Media:NIRx User Resources Overview.pdf|User Resources]]<br />
*[[Media:NIRx User References - Rev. 20140313.pdf|User References]]<br />
*[[Media:NIRx - NIRS Publication Sample - Rev. 20140205.pdf|Publication Samples]]<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: [[Media:NIRStar13-1_Manual_R1.0_2014-05-06_Release.pdf|NIRStar]]<br />
* NIRs Analysis Software: <br />
:*[[Media:nirsLAB_UserManual_AllChapters_2014.pdf|nirsLAB]]<br />
:*[[Media:NIRx NAVI User Manual_12.4.pdf|NAVI]]<br />
* NIRs Mobile Device (currently do not own this device): [[Media:NIRSport Baseplate UserManual-2013-04-R11.pdf|NIRSport]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2741FNIRS2014-08-12T00:19:03Z<p>Soconnell: /* Manuals */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
*[[Media:NIRx User Resources Overview.pdf|User Resources]]<br />
*[[Media:NIRx User References - Rev. 20140313.pdf|User References]]<br />
*[[Media:NIRx - NIRS Publication Sample - Rev. 20140205.pdf|Publication Samples]]<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: [[Media:NIRStar13-1_Manual_R1.0_2014-05-06_Release.pdf|NIRStar]]<br />
* NIRs Analysis Software: :*[[Media:nirsLAB_UserManual_AllChapters_2014.pdf|nirsLAB]]<br />
:*[[Media:NIRx NAVI User Manual_12.4.pdf|NAVI]]<br />
* NIRs Mobile Device (currently do not own this device): [[Media:NIRSport Baseplate UserManual-2013-04-R11.pdf|NIRSport]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2740FNIRS2014-08-12T00:16:52Z<p>Soconnell: /* Information for Use */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
*[[Media:NIRx User Resources Overview.pdf|User Resources]]<br />
*[[Media:NIRx User References - Rev. 20140313.pdf|User References]]<br />
*[[Media:NIRx - NIRS Publication Sample - Rev. 20140205.pdf|Publication Samples]]<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: [[Media:NIRStar13-1_Manual_R1.0_2014-05-06_Release.pdf|NIRStar]]<br />
* NIRs Data Processing Software: [[Media:nirsLAB_UserManual_AllChapters_2014.pdf|nirsLAB]]<br />
* NIRs Mobile Device (currently do not own this device): [[Media:NIRSport Baseplate UserManual-2013-04-R11.pdf|NIRSport]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2736FNIRS2014-08-12T00:13:44Z<p>Soconnell: /* Information for Use */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
*User Resources:<br />
*User References:<br />
*Publication Samples:<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: [[Media:NIRStar13-1_Manual_R1.0_2014-05-06_Release.pdf|NIRStar]]<br />
* NIRs Data Processing Software: [[Media:nirsLAB_UserManual_AllChapters_2014.pdf|nirsLAB]]<br />
* NIRs Mobile Device (currently do not own this device): [[Media:NIRSport Baseplate UserManual-2013-04-R11.pdf|NIRSport]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2735FNIRS2014-08-12T00:12:17Z<p>Soconnell: /* Manuals */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: [[Media:NIRStar13-1_Manual_R1.0_2014-05-06_Release.pdf|NIRStar]]<br />
* NIRs Data Processing Software: [[Media:nirsLAB_UserManual_AllChapters_2014.pdf|nirsLAB]]<br />
* NIRs Mobile Device (currently do not own this device): [[Media:NIRSport Baseplate UserManual-2013-04-R11.pdf|NIRSport]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2731FNIRS2014-08-12T00:05:28Z<p>Soconnell: /* Manuals */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
* NIRs Equipment: [[Media:NIRScout1624 UserManual-2013-07-R33.pdf|NIRScout]]<br />
* NIRs Acquisition Software: <br />
* NIRs Data Processing Software: <br />
* NIRs Mobile Device (currently do not own this device):<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2729FNIRS2014-08-11T23:49:40Z<p>Soconnell: /* Manuals */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
* NIRs Probe Setup and Cap Application: [[Media:NIRx Headgear 2013-11-14_R10.pdf|nirsCAP]]<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=NIRx_Testing&diff=2727NIRx Testing2014-08-11T23:37:09Z<p>Soconnell: /* Caps */</p>
<hr />
<div>==Cleaning==<br />
===Caps===<br />
The caps are made of a fabric netting. Though they won't get that dirty from the ultrasound gel, they may get dirty due to grease from hair, so the best way to clean the caps, if not too dirty, are to wipe the gromits with alcohol swabs to remove any remaining gel. If dirtier, using Johnson's baby shampoo or Ivory soap with water, gently "swish" the cap to remove any dirt. Be very careful not to lose gromits in the process.<br />
<br />
===Fiber Optic Probes===<br />
The fiber optic probe ends that come in contact with the skin may be cleaned and disinfected by wiping with diluted isopropyl alcohol 70%. Use a soft cloth or paper tissue.<br />
<br />
Some fiber optic sets are suited for cold-gas sterilization. Please contact NIRx to confirm suitability and to obtain detailed information.<br />
<br />
'''DO NOT USE ETHANOL OR METHANOL FOR CLEANING OF THE FIBER-OPTIC SURFACES. THE FIBERS ARE NOT SUITED FOR AUTOCLAVING.'''<br />
<br />
==Handling and Routine Maintenance==<br />
===Fiber Optic Probes===<br />
The fiber optic probes are delicate optical devices. Any strain, kinking, pinching, and tight bending(bending radius < 2 cm) should be avoided because this may damage the fibers. <br />
<br />
Before each measurement, the fibers should be visually inspected for signs of physical damage. In the case of suspected fiber damage, please contact NIRx.<br />
<br />
'''NOTE:''' Fiber optics are considered consumables and as such are '''not''' protected by manufacturer warranty.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=NIRx_Testing&diff=2726NIRx Testing2014-08-11T23:36:38Z<p>Soconnell: /* Caps */</p>
<hr />
<div>==Cleaning==<br />
===Caps===<br />
The caps are made of a fabric netting. Though they won't get that dirty from the ultrasound gel, they may get dirty due to grease from hair, so the best way to clean the caps, if not too dirty, are to wipe the gromits with alcohol swabs to remove any remaining gel. If dirtier, using Johnson's baby shampoo or Ivory soap with water, gently "swish" the cap to remove any dirt. Be very careful not to loose gromits in the process.<br />
<br />
===Fiber Optic Probes===<br />
The fiber optic probe ends that come in contact with the skin may be cleaned and disinfected by wiping with diluted isopropyl alcohol 70%. Use a soft cloth or paper tissue.<br />
<br />
Some fiber optic sets are suited for cold-gas sterilization. Please contact NIRx to confirm suitability and to obtain detailed information.<br />
<br />
'''DO NOT USE ETHANOL OR METHANOL FOR CLEANING OF THE FIBER-OPTIC SURFACES. THE FIBERS ARE NOT SUITED FOR AUTOCLAVING.'''<br />
<br />
==Handling and Routine Maintenance==<br />
===Fiber Optic Probes===<br />
The fiber optic probes are delicate optical devices. Any strain, kinking, pinching, and tight bending(bending radius < 2 cm) should be avoided because this may damage the fibers. <br />
<br />
Before each measurement, the fibers should be visually inspected for signs of physical damage. In the case of suspected fiber damage, please contact NIRx.<br />
<br />
'''NOTE:''' Fiber optics are considered consumables and as such are '''not''' protected by manufacturer warranty.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=NIRx_Testing&diff=2725NIRx Testing2014-08-11T23:35:52Z<p>Soconnell: /* =Fiber Optic Probes */</p>
<hr />
<div>==Cleaning==<br />
===Caps===<br />
The caps are made of a fabric netting. Though they won't get that dirty from the ultrasound gel, they may get dirty due to grease from hair, so the best way to clean the caps, if not too dirty, are to wipe the gromits with alcohol swabs. If dirtier, using Johnson's baby shampoo or Ivory soap with water, gently "swish" the cap to remove any dirt. Be very careful not to loose gromits in the process.<br />
<br />
===Fiber Optic Probes===<br />
The fiber optic probe ends that come in contact with the skin may be cleaned and disinfected by wiping with diluted isopropyl alcohol 70%. Use a soft cloth or paper tissue.<br />
<br />
Some fiber optic sets are suited for cold-gas sterilization. Please contact NIRx to confirm suitability and to obtain detailed information.<br />
<br />
'''DO NOT USE ETHANOL OR METHANOL FOR CLEANING OF THE FIBER-OPTIC SURFACES. THE FIBERS ARE NOT SUITED FOR AUTOCLAVING.'''<br />
<br />
==Handling and Routine Maintenance==<br />
===Fiber Optic Probes===<br />
The fiber optic probes are delicate optical devices. Any strain, kinking, pinching, and tight bending(bending radius < 2 cm) should be avoided because this may damage the fibers. <br />
<br />
Before each measurement, the fibers should be visually inspected for signs of physical damage. In the case of suspected fiber damage, please contact NIRx.<br />
<br />
'''NOTE:''' Fiber optics are considered consumables and as such are '''not''' protected by manufacturer warranty.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=NIRx_Testing&diff=2724NIRx Testing2014-08-11T23:35:37Z<p>Soconnell: Created page with "==Cleaning== ===Caps=== The caps are made of a fabric netting. Though they won't get that dirty from the ultrasound gel, they may get dirty due to grease from hair, so the be..."</p>
<hr />
<div>==Cleaning==<br />
===Caps===<br />
The caps are made of a fabric netting. Though they won't get that dirty from the ultrasound gel, they may get dirty due to grease from hair, so the best way to clean the caps, if not too dirty, are to wipe the gromits with alcohol swabs. If dirtier, using Johnson's baby shampoo or Ivory soap with water, gently "swish" the cap to remove any dirt. Be very careful not to loose gromits in the process.<br />
<br />
===Fiber Optic Probes==<br />
The fiber optic probe ends that come in contact with the skin may be cleaned and disinfected by wiping with diluted isopropyl alcohol 70%. Use a soft cloth or paper tissue.<br />
<br />
Some fiber optic sets are suited for cold-gas sterilization. Please contact NIRx to confirm suitability and to obtain detailed information.<br />
<br />
'''DO NOT USE ETHANOL OR METHANOL FOR CLEANING OF THE FIBER-OPTIC SURFACES. THE FIBERS ARE NOT SUITED FOR AUTOCLAVING.'''<br />
<br />
==Handling and Routine Maintenance==<br />
===Fiber Optic Probes===<br />
The fiber optic probes are delicate optical devices. Any strain, kinking, pinching, and tight bending(bending radius < 2 cm) should be avoided because this may damage the fibers. <br />
<br />
Before each measurement, the fibers should be visually inspected for signs of physical damage. In the case of suspected fiber damage, please contact NIRx.<br />
<br />
'''NOTE:''' Fiber optics are considered consumables and as such are '''not''' protected by manufacturer warranty.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2723FNIRS2014-08-11T23:29:07Z<p>Soconnell: </p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===<br />
<br />
==Testing==<br />
Follow these steps to use the NIRx system: [[NIRx Testing]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2722FNIRS2014-08-11T23:28:16Z<p>Soconnell: /* How to Use */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==Information for Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2721FNIRS2014-08-11T23:22:53Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation.pptx|nirsLAB Overview]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2720FNIRS2014-08-11T23:21:56Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
:3. [[Media:Part 03 - fNIRS_Applications.pptx|Applications]]<br />
:4. [[Media:Part 04 - First fNIRS Experiment.pptx|First fNIRs Experiment]]<br />
:5. [[Media:Part 05 - Mobile NIRS with NIRSport Presentation and Experiment.pptx|NIRSport]]<br />
:6. [[Media:Part 06 - fNIRS-EEG Presentation and Experiment.pptx|Concurrent fNIRS-EEG]]<br />
:7. [[Media:Part 07 - nirsLAB Overview Presentation|nirsLAB Overview]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2714FNIRS2014-08-11T22:37:17Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2713FNIRS2014-08-11T22:37:07Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction<br />
:2. [[Media:Part 02 - fNIRS Hardware and Software Presentation.pptx|Hardware and Software]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2712FNIRS2014-08-11T22:36:02Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [[Media:Part 01 - fNIRS_Introduction.pptx|Introduction]]<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2711FNIRS2014-08-11T22:33:46Z<p>Soconnell: /* Powerpoint Presentations */</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
:1. [<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2708FNIRS2014-08-11T22:29:34Z<p>Soconnell: </p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
==NIRx system location==<br />
<br />
The NIRx system is currently located in the EEG Net Room to the left of the EEG Testing Room.<br />
<br />
==How to Use==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2707FNIRS2014-08-11T22:27:47Z<p>Soconnell: </p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net<br />
<br />
<br />
==User Information==<br />
<br />
Here is information outlining how to use the NIRx system<br />
<br />
===Powerpoint Presentations===<br />
<br />
===Manuals===</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2706FNIRS2014-08-11T22:24:46Z<p>Soconnell: </p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website] or contact Thomas Johannsen at thomas.johannsen@nirx.net</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=FNIRS&diff=2705FNIRS2014-08-11T22:24:33Z<p>Soconnell: Created page with "In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system a..."</p>
<hr />
<div>In July 2014, the CCN received the NIRx fNIRs system that uses infrared light to measure blood flow. This page can direct you to how to locate, use, and maintain the system along with how to process data.<br />
<br />
In case of questions not answered here, please view the [http://www.nirx.net/ NIRx website]] or contact Thomas Johannsen at thomas.johannsen@nirx.net</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=StaglinCenter:EEG&diff=2704StaglinCenter:EEG2014-08-11T22:19:18Z<p>Soconnell: </p>
<hr />
<div>This page will give you general information about the EEG Suite including how to use the testing rooms, EGI net information, current EEG projects, and where to locate and order supplies.<br />
<br />
<br />
The Staglin EEG Suite is part of the [http://www.semel.ucla.edu/staglin Staglin IMHRO Center for Cognitive Neuroscience] and contains resources including:<br />
*[http://www.egi.com/research-division-research-products/eeg-systems/251-conventional-eeg EGI Net Amps 300]<br />
*[http://www.egi.com/research-division-research-products/eeg-systems/191-ges300mr MR-safe EGI Net Amps 300]<br />
*[http://www.egi.com/research-division-research-products/sensor-registration EGI Photogrammetry System]<br />
*[http://www.egi.com/research-division-research-products/sensor-nets EGI HydroCel EEG Nets] - S/M/L of MR and non-MR compatible versions<br />
<br />
<br />
==Using the EEG Suite==<br />
This page describes step-by-step how to schedule, set-up, and test in the Staglin EEG Suite: [[StaglinCenter:EEG:Testing]]<br />
<br />
'''We recommend giving these directions a complete once-over before you ever take data here.'''<br />
<br />
==Troubleshooting and Denoising==<br />
*[[Checking Ground]]<br />
*[[Checking for wire loops]]<br />
*[[Checking Scanner Settings]]<br />
*[[Checking Cap Electrodes for Noise]]<br />
<br />
==EGI Net Maintenance==<br />
*[ftp://ftp.egi.com/pub/support/Documents/Moodle/LMC101/Routine%20Net%20Test%20Protocol.pdf Procedure for Routine Net Tests]<br />
*[https://docs.google.com/forms/d/1qYeNEjPSWKaGmElK9eYHlLOpIOF6R5L1tYh1l861R4E/viewform EGI Net Check-Up Form]<br />
*[https://docs.google.com/spreadsheets/d/1Gx4vqWxGfCX9JPs5AoBQcIU4OveudAx9vv4XIcNJ8YQ/edit#gid=332429759 EGI Net Check-Up Log]<br />
<br />
==EEG Suite supplies==<br />
*[[Where to find EEG supplies]]<br />
*[[Where to order EEG supplies]]<br />
*[[Current supply stock]]<br />
<br />
==Current Projects==<br />
===EEG-only===<br />
*[[SSVEP EEG]]<br />
<br />
===Concurrent EEG/fMRI===<br />
*[[SSVEP Concurrent]]<br />
*[[AV Task]]<br />
<br />
==Related Info==<br />
===EKG===<br />
If you want to take EKG data concurrently...<br />
*[[StaglinCenter:EEG:EKG]]<br />
<br />
<br />
==External Links==<br />
*[http://www.egi.com EGI]<br />
*[http://www.egi.com/research-division-research-products/eeg-systems/251-conventional-eeg EGI Amp]<br />
*[http://www.egi.com/research-division-research-products/eeg-systems/191-ges300mr EGI MR Safe Amp]<br />
*[http://www.egi.com/research-division-research-products/sensor-registration EGI Photogrammetry System]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Access_information_(VPN)&diff=2703Access information (VPN)2014-08-11T22:16:08Z<p>Soconnell: </p>
<hr />
<div>'''IMPORTANT:''' BrainVision Analyzer can only be installed on Windows or devices that can parallel Windows. <br />
<br />
1. Install the BrainVision Analyzer VPN access point using the instructions here: [[Media:Bva2-instructions.pdf|BVA2 Installation Instructions]]<br />
:: NOTE: '''DO NOT''' use the IP address in the PDF instructions. The current IP address is '''128.97.66.151''' (updated 2014-08-06)<br />
2. Contact Edward Lau (eplau@ucla.edu) for an ID and password to use to connect to the VPN.</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EEG&diff=2702EEG2014-08-11T22:15:27Z<p>Soconnell: </p>
<hr />
<div>A collection of information about EEG data from collection to processing/analysis.<br />
<br />
<br />
<br />
==Collection==<br />
How do you even get EEG data?<br />
<br />
===Staglin===<br />
The [http://www.semel.ucla.edu/staglin Staglin IMHRO Center for Cognitive Neuroscience] is our main EEG data collection facility. Go here to learn how data collection works at the Staglin Center.<br />
*[[StaglinCenter:EEG]]<br />
<br />
===EEG/FMRI===<br />
Concurrent data collection of EEG and FMRI is possible at the Staglin Center.<br />
*[[StaglinCenter:EEG-FMRI]]<br />
<br />
===Transfer===<br />
For now you have to move data by sneaker-net from the acquisition computers to your computer. We may automate this process in the future.<br />
<br />
<br />
==Directory Structure==<br />
Standards are important. And we're hoping to have standards about how our EEG data is kept?<br />
*[[EEG:DirectoryStructure]]<br />
<br />
<br />
<br />
==Processing==<br />
How to process EEG data.<br />
*[[General Pre-Processing Steps]]<br />
<br />
===Programs for EEG data processing===<br />
*[[Netstation]]<br />
*[[BrainVision Analyzer]]<br />
*[[EEGLAB]]<br />
<br />
===ICA===<br />
Independent Component Analysis<br />
*[[EEG:Processing:ICA]]<br />
<br />
===Source===<br />
Source localization.<br />
*[[EEG:Processing:Source]]<br />
<br />
*[[Under Construction]]<br />
<br />
== History ==<br />
<br />
*[[EEG fMRI noise 2011]]<br />
*[[EEG Net Names]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=Under_Construction&diff=2701Under Construction2014-08-11T22:13:49Z<p>Soconnell: Created page with "*Basic Preprocessing in NetStation *Basic Preprocessing and ICA in EEGLAB *Time-Frequency Analyses - Matlab/EEGLAB *Source Analysis *Machine Learning"</p>
<hr />
<div>*[[Basic Preprocessing in NetStation]]<br />
*[[Basic Preprocessing and ICA in EEGLAB]]<br />
*[[Time-Frequency Analyses - Matlab/EEGLAB]]<br />
*[[Source Analysis]]<br />
*[[Machine Learning]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EEG&diff=2700EEG2014-08-11T22:13:40Z<p>Soconnell: /* Processing */</p>
<hr />
<div>A collection of information about EEG data from collection to processing/analysis.<br />
<br />
<br />
<br />
==Collection==<br />
How do you even get EEG data?<br />
<br />
===Staglin===<br />
The [http://www.semel.ucla.edu/staglin Staglin IMHRO Center for Cognitive Neuroscience] is our main EEG data collection facility. Go here to learn how data collection works at the Staglin Center.<br />
*[[StaglinCenter:EEG]]<br />
<br />
===EEG/FMRI===<br />
Concurrent data collection of EEG and FMRI is possible at the Staglin Center.<br />
*[[StaglinCenter:EEG-FMRI]]<br />
<br />
===Transfer===<br />
For now you have to move data by sneaker-net from the acquisition computers to your computer. We may automate this process in the future.<br />
<br />
<br />
==Directory Structure==<br />
Standards are important. And we're hoping to have standards about how our EEG data is kept?<br />
*[[EEG:DirectoryStructure]]<br />
<br />
<br />
<br />
==Processing==<br />
How to process EEG data.<br />
*[[General Pre-Processing Steps]]<br />
<br />
===Programs for EEG data processing===<br />
*[[Netstation]]<br />
*[[BrainVision Analyzer]]<br />
*[[EEGLAB]]<br />
<br />
*[[Under Construction]]<br />
<br />
<br />
===Preprocessing===<br />
<br />
===ICA===<br />
Independent Component Analysis<br />
*[[EEG:Processing:ICA]]<br />
<br />
===Source===<br />
Source localization.<br />
*[[EEG:Processing:Source]]<br />
<br />
== History ==<br />
<br />
*[[EEG fMRI noise 2011]]<br />
*[[EEG Net Names]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=BrainVision_Analyzer&diff=2699BrainVision Analyzer2014-08-11T22:11:56Z<p>Soconnell: Created page with "==BrainVision Analyzer Manual== The BrainVision Analyzer 2.0 [http://erpinfo.org/boot-camp-2007-materials/2013-boot-camp-materials/boot-camp-tutorials/documentation/Analyzer.p..."</p>
<hr />
<div>==BrainVision Analyzer Manual==<br />
The BrainVision Analyzer 2.0 [http://erpinfo.org/boot-camp-2007-materials/2013-boot-camp-materials/boot-camp-tutorials/documentation/Analyzer.pdf Manual]<br />
<br />
==Installing the BVA license==<br />
*[[Access information (VPN)]]<br />
<br />
==Other information NOT included in the BVA Manual==<br />
*[[Importing EEG data]]<br />
*[[Topographic Interpolation]]<br />
*[[Editing Channel Locations]]<br />
*[[Using ICA in BVA]]<br />
*[[Viewing Data Info]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=EEG&diff=2698EEG2014-08-11T22:11:15Z<p>Soconnell: /* Processing */</p>
<hr />
<div>A collection of information about EEG data from collection to processing/analysis.<br />
<br />
<br />
<br />
==Collection==<br />
How do you even get EEG data?<br />
<br />
===Staglin===<br />
The [http://www.semel.ucla.edu/staglin Staglin IMHRO Center for Cognitive Neuroscience] is our main EEG data collection facility. Go here to learn how data collection works at the Staglin Center.<br />
*[[StaglinCenter:EEG]]<br />
<br />
===EEG/FMRI===<br />
Concurrent data collection of EEG and FMRI is possible at the Staglin Center.<br />
*[[StaglinCenter:EEG-FMRI]]<br />
<br />
===Transfer===<br />
For now you have to move data by sneaker-net from the acquisition computers to your computer. We may automate this process in the future.<br />
<br />
<br />
==Directory Structure==<br />
Standards are important. And we're hoping to have standards about how our EEG data is kept?<br />
*[[EEG:DirectoryStructure]]<br />
<br />
<br />
<br />
==Processing==<br />
How to process EEG data.<br />
<br />
*[[General Pre-Processing Steps]]<br />
*[[BrainVision Analyzer]]<br />
*[[EEGLAB]]<br />
<br />
*[[Under Construction]]<br />
<br />
<br />
===Preprocessing===<br />
<br />
===ICA===<br />
Independent Component Analysis<br />
*[[EEG:Processing:ICA]]<br />
<br />
===Source===<br />
Source localization.<br />
*[[EEG:Processing:Source]]<br />
<br />
Under construction<br />
*[[Basic Preprocessing in NetStation]]<br />
*[[Basic Preprocessing and ICA in EEGLAB]]<br />
*[[Time-Frequency Analyses - Matlab/EEGLAB]]<br />
*[[Source Analysis]]<br />
*[[Machine Learning]]<br />
<br />
== History ==<br />
<br />
*[[EEG fMRI noise 2011]]<br />
*[[EEG Net Names]]</div>Soconnellhttps://www.ccn.ucla.edu/wiki/index.php?title=StaglinCenter:EEG:Export&diff=2697StaglinCenter:EEG:Export2014-08-11T21:29:45Z<p>Soconnell: Created page with "<div style="text-align: center; border: 1px dotted gray;"> Return to StaglinCenter:EEG:Testing</div>"</p>
<hr />
<div><div style="text-align: center; border: 1px dotted gray;"> Return to [[StaglinCenter:EEG:Testing]]</div></div>Soconnell