When using the Portal website to record Flow data, it is strongly recommended that you use a Chrome internet browser. Other browsers are not guaranteed to work. To begin recording: Make sure you are in the Flow tab for the correct Organization and the Study under which you want to record data. Follow the instructions in the Preparing Flow2 for Use or Preparing DevKit for Use sections to start up the headset, fit the headset properly on the participant, and tune the lasers. From the Data Acquisition Control Menu, click the Participant  drop-down menu and select the ID that corresponds with the participant who is wearing the headset. Optionally select a Task name from the Task drop-down menu. To learn more about Task names, see Adding Task names . Optionally enter a visit N umber , Name , and Description . Optionally enter a maximum duration in seconds (i.e. 10

Tasks are predefined stimuli or instructions that you can present to a participant during a recording. By using precise, repeatable tasks, you can ensure data are appropriately comparable across multiple datasets (under different circumstances, for example) and across multiple participants. In order for the timing of Task stimuli to be synchronized and recorded alongside your Flow2 data during a data recording, Tasks must be created using a specific framework (and run on the same computer being used to acquire data). You can create your own Tasks using the Kernel Tasks SDK or you can use one of the Kernel-built Unity Tasks. The Tasks in the menu are described below. NOTE: The provided tasks may be presented by configuring your data acquisition computer to have a participant-facing monitor in addition to the main monitor. This can be helpful if you would like to be able to view the

PLEASE READ THE FOLLOWING SAFETY NOTICES LASER SAFETY The Kernel Flow2 complies with Federal Laser Product Performance Standards (FLPPS) 21CFR1040.10 (Code of Federal Regulations, Title 21, Section 1040.10) and is classified as a Class 1 laser device and does not present a hazard with regard to maximum permissible exposure and accessible exposure limits for both ocular and skin considerations. The Kern el Flow2 utilizes 120 NIR and 120 visible Class 1 diode lasers. During Normal operation the Kernel Flow2 emits visible (690nm) and invisible (905nm) Class 1 laser radiation. Class 1 laser is considered safe from all potential hazards and is considered to be incapable of producing damaging radiation levels during operation and is exempt from any control measures.  Natural eye protection is provided by the physiological eye aversion response. This response induces closure of the eyelid, eye movement and pupillary constriction, in addition to movement of the

The list and visualization below illustrate how a Kernel Cloud Organization and its research are organized in the Kernel Cloud database. DATASET:  an individual collection of data, such as a Kernel Flow2 recording (e.g. what is captured between Record start and Record stop of the Flow2 system). Datasets can also refer to data collected through a survey or other data stream.  A dataset has a variety of metadata saved with it. SESSION:  a collection of individual datasets, such as all the datasets recorded while a participant is wearing the headset on a specific day. STUDY: a research project. May include multiple tasks, and research may be conducted over many sessions with many participants.  TASK:  an individual experiment within a study. An Organization can have an unlimited number of Studies, each Study can have an unlimited number of sessions, and each session can have an unlimited number of datasets

If your Organization ordered a Sync Accessory Box, it will be included with the Flow2 system. The Sync Accessory Box is a USB peripheral used for collecting data from external devices during the recording of a Flow2 recording. This might include devices like a button/trigger, eye trackers, VR/AR headsets, or physiological measurement devices (e.g. pulse oximeter, capnometer, respiration belt, etc.). You might also use the Sync Accessory Box to record Task data generated from certain external devices.   You do not need to use the Sync Accessory Box to record or synchronize data from Kernel Unity Tasks , or Tasks created using Kernel's Task SDK (as long as your task-generating system is on the same local network and clock as the data acquisition computer). In those cases, Kernel's software automatically synchronizes and record those data along with your Flow2 data. Sync data collected through the Sync

EEA, UK, or Switzerland, you may request that we: provide access to and/or a copy of certain Personal Data we hold about you delete certain Personal Data that we are holding about you prevent the processing of your Personal Data for direct-marketing purposes (including any direct marketing processing based on profiling); update or rectify Personal Data that is out of date or incorrect; oppose, cancel, or restrict the way that we process and disclose certain of your Personal Data; transfer your Personal Data to a third-party provider of services; or revoke your consent for the processing of your Personal Data. To make such a request, please contact us at privacy@kernel.com .  If applicable, you may make a complaint to the data protection supervisory authority in the country where you reside. Alternatively, you may seek a remedy through local courts if you believe your rights have been

A Study is the basic framework in which data from Kernel systems are organized and stored. Organizations can create an unlimited number of studies, and individual researchers and Flow2 or DevKit systems can be associated with specific studies. Roles Each Organization contains Studies, which the Organization Owner or Organization Admin can create. Within a Study, researchers can be designated as an A dministrator (Study Admin)  or a R esearcher (Study Member) . Organization Admins are automatically designated as Study Admin for each Study in the Organization. Each role has different privileges:  To create a Study (Organization Owner/admin only): On the Home page in the Kernel Cloud Portal (can be accessed at any time by clicking the "Kernel" logo in the top left corner), type the name of the Study into the Add Study field and click the Add Study icon. The Study is added to the Studies List. To

You may want to hide some datasets from view. For example, a dataset that was interrupted or otherwise rendered unusable during recording might best be removed from the list of datasets when reviewing the Study results. Hiding a dataset in Kernel Cloud is done by invalidating it. Invalidating a dataset removes it from the default view in Dataset Lists. The dataset remains available for researchers (with sufficient privileges) to view, download, and analyze, as well as to re-validate if you change your mind.   To invalidate a recorded dataset: In the Portal, navigate to the Datasets tab containing the dataset you want to invalidate. Find the dataset in the list and click it. The Dataset detail page opens. Click the Info tab. Scroll down to the Invalidate Dataset section. Type the reason for invalidation in the (mandatory) Reason Invalid field. Click the Invalidate Dataset  button. The dataset is invalidated

Before using your Kernel system for the first time, a team member must set up your organization and register your Flow2 headset using the Kernel Cloud Portal at portal.kernel.com . See Configuring Kernel Cloud . On the Portal, you can perform the following tasks: Configure your Kernel Cloud organization and account Add researchers to your team Creating and managing studies Create Participant IDs Create Task names View  and  download  datasets Logging into the Portal: You can login to the Portal by entering a one-time passcode. To login to the Portal: From the Portal home page , click Log In . Enter the email address associated with your account (or log in with Google) and click Log In . An email is sent containing a unique one-time code. In your browser window, the Confirm Authentication dialog appears.   To login using the emailed one-time code: Switch to your email program.  Locate

The DevKit comes with a set of six active dry EEG electrodes and corresponding EEG tips. For the reference design cap  that arrives with your shipment, t he electrodes are pre-installed into the cap. They are placed approximately at F3, F4, T7, T8, P3, and P4 on the 10-10 grid. The system also includes two external Reference/Bias leads with ear clips on the ends. The EEG system is integrated into the headset and the electrical signals are digitized and synchronized with the optical data on the headset to be transmitted together to Kernel Cloud.   The reference design cap will have electrodes pre-installed, but not the rubber tips, which make contact with the scalp and lower the EEG impedance. Kernel sends two types of EEG tips to snap into the electrodes: four flat and four pronged electrodes. For the reference design cap , the flat electrodes should

These Terms of Service (these “ Terms of Service ”) form a binding contract between you (“ AUTHORIZED CUSTOMER USER , “ you ” or “ your ”) and HI, LLC, d/b/a Kernel (together with its subsidiaries, agents, employees, successors and assigns, “ KERNEL ,” “ we ,” “ us ”). PLEASE CAREFULLY READ THESE TERMS OF SERVICE.  THEY CONTAIN IMPORTANT INFORMATION ABOUT YOUR RIGHTS AND OBLIGATIONS.  BY ACCESSING OR USING THE KERNEL TECHNOLOGY OR ANY DATA COLLECTED FROM THE KERNEL TECHNOLOGY, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTAND THESE TERMS OF SERVICE AND YOU AGREE TO BE BOUND HEREBY.   1. Definitions “ Customer ” means the institution or other entity through which you are accessing or using the Kernel Technology.  Kernel Technology ” means, collectively all Kernel-issued products and KERNEL’s: website interface(s); proprietary platform referred to as the Kernel Cloud; user operating manual for the Kernel Cloud, the Kernel-issued products and/or software and any modifications to such

Storing the Headset Your Kernel DevKit system was shipped to you in a carefully designed and thoroughly cushioned hard case (the Kernel Storage Case). The reference design cap sits on a precision-molded Headset Stand sized to precisely fit the cap snugly but without strain. This stand is also used for the startup process . Always store your DevKit cap on the supplied Headset Stand. When stored for extended periods, always store the cap on the Headset Stand inside the Kernel Storage Case. Do not store the DevKit with cables attached. Never close the case before checking that the cap is properly stowed on the Headset Stand in its designated cavity.

When using the Portal website to record data with the Flow2 or DevKit headset, it is strongly recommended that you use a Chrome internet browser. Other browsers are not guaranteed to work. A recording ends when the maximum duration elapses or the researcher clicks the Stop Recording button. All captured data is automatically uploaded to Kernel Cloud for processing and analysis. If you are done recording datasets, there are important steps to follow.  To end a recording and remove the headset: If necessary, click the  Stop Recording button on the Portal Flow UI.   Click Turn  Lasers OFF . Ensure the lasers are OFF before removing the headset from a participant.   Remove the headset according to Removing the DevKit from a participant or Removing the Flow2 Headset from the participant . NOTE: Note that if you try to stop the recording before a task event is received that indicates the end of

When using the Portal website to interact with the Flow headset, it is strongly recommended that you use a Chrome internet browser. Other browsers are not guaranteed to work. On the Flow tab of a study in Portal, and with the headset on the head, press the Turn Lasers ON button on the Portal Flow UI to enable the lasers.  You will see a map that shows the signal strength of the data for each module. This metric measures how much light reaches the detectors from the light sources within a module. It can be seen as a proxy for how well-coupled the light sources and detectors are to the participant's scalp and therefore how much analyzable data will be received for each module. The signal strength of each module is depicted with a color scale, where white/light blue shades indicate a low/negligible amount of

Flow2 and the DevKit reference design (which is included with a DevKit purchase) are designed to be used with minimal training. Our software guides you through the setup, placement, and positioning of the headset for measurements. If you have experience using other neuroimaging devices like CW-fNIRS or EEG, then using a Kernel headset should be easy. If you need additional tips or pointers, we have tutorials and videos for using our system in the Preparing and Using Flow2/DevKit sections of our documentation site. If you do run into technical issues, you can always reach out to us at support@kernel.com for help. If you'd like a focused training session for your organization, please contact us to discuss training package options.

Flow2 The Flow2 headset is designed for an average adult head. Our system should fit people with with head measurements of: 52cm - 62cm Circumference 32cm - 37cm Bitragion Coronal Arc Heads are complex and unique. There may be some combinations in between that don’t fit well. We’ve made our best effort to design flexibility into the system so that it fits more than 90% of the adult population. DevKit The DevKit is intended, in part, to enable the use of Kernel Flow technology on subjects outside the size range of a Flow2 headset. The DevKit modules can be assembled into a soft cap of your choosing (see Assembling a new DevKit cap ), so you can easily make smaller or larger caps with module layouts appropriate to your specific goals. To provide an example and starting point, a reference design cap is included with the DevKit. This cap has

Kernel Flow provides four quality control (QC) reports to help you evaluate the results of your Flow data: NIRS Basic QC NIRS Expert QC EEG QC Sync Accessory Box QC To view or download QC files: In the Portal, navigate to the dataset you want to analyze: Click Pipelines to open the Pipelines tab.  Click the QC header to expand that section. Click one of the buttons to download the QC file(s). Descriptions of the QC reports are listed below. NIRS Basic quality control report This report contains a Session Summary and 7 sections, each of which assigns a status to a certain aspect of data quality. The statuses are determined by color and are listed below.  Red: indicates an issue Orange: indicates a warning or potential issues Green: indicates no issues Sections that are assigned orange or red statuses should serve as flags to improve data recording conditions

Data export pipelines are one type of download available through the Kernel Portal at this time. These are accessed in the Pipelines tab for each dataset (see Downloading datasets ). Data export pipelines allow you to export the TD-NIRS data into two different formats: The SNIRF format, for channel-space data The NIfTi format, for voxel-space data NOTE: Kernel is dedicated to continually enhancing our signal processing pipelines to maximize neural signal extraction while effectively filtering out various noise sources from the rich data streamed by the Flow device. The preprocessing of fNIRS data, particularly TD-fNIRS data, is an evolving area of research both within the academic community and at Kernel. This document provides a description of the current processing methods. Any updates to the pipelines will be documented in the Release Notes . SNIRF and NIfTI exports are tagged with the version of the Portal pipeline that produced

Kernel Acceptable Use Policy In connection with the use of any Kernel Service or Product, including the Kernel Cloud, you must not: Promote, encourage, or facilitate hate speech, violence, or discrimination against individuals or groups. Attempt to manipulate people into believing misinformation; Harm others or cause individuals to harm themselves or others; Impersonate another person, misrepresent your affiliation with another person or entity, engage in fraud, or hide or attempt to hide your identity; Collect or harvest any personally identifiable information, including account names, from any other user’s account; Access any unauthorized Kernel technology or unauthorized part of the Kernel Cloud, Access any part of the Kernel Cloud, or any content or data therein, through any technology or means other than those provided or authorized by Kernel (including without limitation through technologies such as automated or non-automated “scraping,” “robots,” “spiders,” “offline readers,”); Interfere with the normal functioning

The Kernel API allows you to automate repeated tasks programmatically. To get started, have your Organization Owner generate an API key on the Organization Settings page. External/Customer facing API Routes for: All dataset IDs + metadata in a study Run a pipeline, given a dataset ID and pipeline name Status for most recent pipeline run and signed urls if present, given dataset ID and pipeline name NOTE: All routes use the same hostname: api.kernel.com Each route requires an API key in the header, such as: headers={"Authorization": f"{api_key}"} An Organization Owner can generate an API key on the Organization Settings page. Common ways to use Kernel API To find your study_id : Navigate to the study in portal and notice the URL looks like: https://portal.kernel.com/organizations/2d1fee1c-c2bc-4833-b560-afc673140f42/studies/ b249e4b9-9108-4ce4-a7ce-41cc3bbd2bf2 /datasets The bold part b249e4b9-9108