System Status Dialog



The system status dialog will allow you to see the status of __prod_name while acquiring or recording.  The system status dialog can be launched from the View menu of __prod_name:




Single Line Information

1. Acquisition Toggle and Status When this indicator is gray, __prod_name is not acquiring any data.  Clicking on the acquisition toggle when the indicator is gray will start acquiring data.  When __prod_name is acquiring, the indicator will turn green.  Clicking on the acquisition toggle when the indicator is green will turn off acquisition.
2. Recording Toggle and Status When this indicator is gray, __prod_name is not recording data to a file.  Clicking on the recording toggle when the indicator is gray will start recording data to a file.  When __prod_name is recording, the indicator will turn purple.  Clicking on the recording toggle when the indicator is purple will turn off recording.   No data will be saved if __prod_name is not in recording mode.
3. Timestamp Clock This is the current __prod_name timestamp displayed in YYYY/MM/DD HH:MM:SS 24-hour clock format. microseconds. This is obtained from the clock of the computer on which __prod_name is running. Use the current session status section of this window to determine how long __prod_name has been acquiring or recording.
4. Logged Errors




Displays the number of errors that have been logged to the logfile since the last time the counter was reset.  The logfile provides details on the errors that have occurred.  To view the logfile, click on the logged errors button and select "View Logfile".  To reset the error count back to zero, click the logged errors button and select "Reset Logged Error Count". 
5.  Data Processing Errors




This indicator will turn red every time a Data Processing Error occurs and the total number of errors will be incremented.  A Data Processing Error is logged when an AD, CSC, Spike, Event, Video or Display Error occurs.  To reset the error count back to zero, click the logged errors button and select "Reset Data Processing Counters". For more details on the different types of Data Processing Errors, see the Error Counts section of this window. Clicking on Reset Data Processing Counters will reset all of the processing statistics for the system to 0. The current statistics will be written to the logfile before they are reset.
6. Show/Hide Details Button Clicking on this button when it says "Show Details" will expand the acquisition system status window to show a more detailed view of the current system status.  Clicking on the button when it says "Hide Details" will change the window to single line mode.


Detailed View

Current Session Status
1. Start Date and Time of Acquisition This is the exact time and date of the last time __prod_name began acquiring.
2. Start Date and Time of Recording This is the exact time and date of the last time __prod_name began recording.
3. Hard Disk Usage The disk usage is shown as a percentage of used space on the hard drive where the data directory is located.  In the above image, it shows that 182.6 gigabytes(GB) out of a total of 465.7GB are used.  The higher this number, the less space you have left on your system.  If this percentage is ever over 90%, you should change the data directory to a different hard drive, delete old data and unused programs, or get more storage space for your computer.
4. Connected NetCom Client This is the name of the NetCom client program that is connected to __prod_name.  If no program is connected, this will show "Not Connected" (as seen above).
5.  System Identification This identifies the system on which __prod_name is running.  The default system identifier is the PC name on which __prod_name is running.  This field can be modified as needed.
6.5. Elapsed Time of Acquisition This is the elapsed time in hours, minutes and seconds since the last time __prod_name began acquiring.  If __prod_name is not acquiring,  this will show the duration of the last recording session.
7.6. Elapsed Time of Recording This is the elapsed time in hours, minutes and seconds since the last time __prod_name began recording.  If __prod_name is not recording, this will show the duration of the last recording session.



System Message History
1. Message Filters Only messages whose type has a check mark (filter is On) by it in the message filters list will be shown in the history list.   All messages are passed through the message filters before being sent to the message history.  If the message makes it through the filters, it will be displayed in the message history.  Changes in the filter settings will have no effect on messages that have already been through the filtering process.

__prod_name allows you to filter the following messages:
  1. Fatal: All messages tagged as FATAL will be affected. A major error has occurred that has caused the system to no longer process data in some way.  The system should be restarted and Neuralynx Support should be notified.
  2. Error:   All messages tagged as ERROR will be affected. An error of some type has occurred, but the system has the capacity to continue processing data.  This is usually a minor data processing error such as an error in commands, incorrect keywords or values, intermittent problems with a portion of the system or a user interface error.
  3. Warning:   All messages tagged as WARNING will be affected.  Warning messages indicate that something happened out of the ordinary, but was handled by __prod_name.
  4. Notice:   All messages tagged as NOTICE will be affected.  Notices provide status information about __prod_name, such as what the system has been doing in case an error occurs or to review system data processing. These messages are purely informational.  
  5. Data:   All messages tagged as DATA will be affected.  Data message types can be used to log information to the log file. These are rarely used and their main purpose is for debugging.  However, if you will use these messages for analysis, you would be better off posting an event with the message as the event string.
2.Clear Button Clicking this button will clear all messages in the message history list.  All of these messages are present in the log file, so you will not be clearing all records of these messages.
3.View Logfile Button Each time a message is generated by __prod_name, it is logged in the log file.  The message history will only show the most recent messages that were allowed by the filter selections, not all the messages that have occurred since __prod_name was started.  Clicking on the View Logfile button will allow you to see a complete list of messages generated by __prod_name at the time the button is pressed, regardless of the message filter settings.  Keep in mind that a new logfile is started when you change data directories.
4. Timestamp Every message displayed in the message history list will have the __prod_name timestamp for when the message was generated displayed in this column.
5. Message Type This will be one of the types listed in the message filters section.
6. Message The complete message text that was generated by __prod_name.


Error Counts
1.  AD Processing Errors Button


File AD Records Lost:  The total number of AD Records that were lost during the recording of a raw data file (.nrd).  For example, 1 lost AD Record means that 1 AD sample was lost for each channel recorded in the raw data file.

File AD Records Processed:  The total number of AD Records that were properly recorded per channel to a raw data file (.nrd).
2.  CSC Processing Errors Button


Acquisition Samples Lost:  The number of CSC samples lost while Acquisition is ON.

Acquisition Samples Processed:  The number of CSC samples processed correctly while Acquisition is ON.

Recording Samples Lost:  The number of CSC samples lost while Recording is ON.

Recording Samples Processed:  The number of CSC samples processed correctly while Recording is ON.

File Samples Lost:  The number of CSC samples not properly written to file.

File Samples Processed:  The number of CSC samples correctly written to file.

NetCom Samples Lost:  The number of CSC samples lost when sending data to a NetCom client application.

NetCom Samples Processed:  The number of CSC samples successfully sent to a NetCom client application.
3.  Spike Processing Errors Button


Acquisition Samples Lost:  The number of Spike samples lost while Acquisition is ON.

Acquisition Samples Processed:  The number of Spike samples processed correctly while Acquisition is ON.

Recording Samples Lost:  The number of Spike samples lost while Recording is ON.

Recording Samples Processed:  The number of Spike samples processed correctly while Recording is ON.

File Samples Lost:  The number of Spike samples not properly written to file.

File Samples Processed:  The number of Spike samples correctly written to file.

NetCom Samples Lost:  The number of samples lost when sending data to a NetCom client application.

NetCom Samples Processed:  The number of Spike samples successfully sent to a NetCom client application.

4.  Event Processing Errors Button




Acquisition Samples Lost:  The number of Event records lost while Acquisition is ON.

Acquisition Samples Processed:  The number of Event records processed correctly while Acquisition is ON.

Recording Samples Lost:  The number of Event records lost while Recording is ON.

Recording Samples Processed:  The number of Event records processed correctly while Recording is ON.

File Samples Lost:  The number of Event records not properly written to file.

File Samples Processed:  The number of Event records correctly written to file.

NetCom Samples Lost:  The number of Event records lost when sending Event data to a NetCom client application.

NetCom Samples Processed:  The number of Event records successfully sent to a NetCom client application.
5.  Video Processing Errors Button




Acquisition Samples Lost:  The number of Video records lost while Acquisition is ON.

Acquisition Samples Processed:  The number of Video records processed correctly while Acquisition is ON.

Recording Samples Lost:  The number of Video records lost while Recording is ON.

Recording Samples Processed:  The number of Video records processed correctly while Recording is ON.

File Samples Lost:  The number of Video records not properly written to file.

File Samples Processed:  The number of Video records correctly written to file.
6.  Display Errors Button





STX:  STX is a value used to identify the start of an AD Record.  STX values are used when transmitting data in order to help detect and recover from corrupt data.  If this error occurs, then at least 1 AD Record has been lost.

ID:  The ID is a value used to identify the AD Record type when processing data.  It also helps detect when data has been corrupted.  If this error occurs, then at least 1 AD Record has been lost.

Size:  The size represents the AD data portion of an AD Record.  The size is validated by comparing it to the expected size that is calculated in __prod_name.  This error is generally caused by the number of input boards being set incorrectly.  An invalid size value may also indicate that the AD Record has become corrupt.  If this error occurs, then at least 1 AD Record has been lost.

CRC:  The CRC is a value used to validate the contents of a data packet.  If this error occurs, then at least 1 AD Record has been lost.

Order Adjustments:  The number of times __prod_name had to re-order the AD records received from the __lynxsx_hardware_name Neurophysiology System.

Timestamp:  The timestamp value used to identify and validate the contents of an AD Record.  The timestamp is also used to determine if any AD Records have been lost.  If this error occurs, then at least 1 AD Record has been lost.

AD Records Lost:  The total number of AD Records that were lost during Acquisition or Recording.

AD Records Processed:  The total number of AD Records that were properly processed during Acquisition or Recording.

DMA Sequence:  This is not applicable to __prod_name.

DMA Ring Buffer Overrun:  This is not applicable to __prod_name.

Filter Ring Buffer Overrun:  A ring buffer containing raw unfiltered data has overflowed.  If this occurs, all data within the ring buffer has been lost.  This error is due to a lack of resources being available to process the buffer in real time.

Display Ring Buffer Overrun:  A ring buffer containing data records has overflowed.  The data records can be any of the data types used by __prod_name.  If this occurs, all data within the ring buffer has been lost and will not be displayed in any of the plots associated with the ring buffer that has overflowed.  This error is due to a lack of resources being available to process the buffer in real time.

Display Vertex:  A vertex buffer has reached its maximum capacity for drawing data for the current screen refresh.  All data that is received after the buffer has become full will be discarded.  This error will also occur if data has been calculated to draw incorrectly to the screen.