FRIEND Engine icon
FRIEND Engine icon

FRIEND Engine

FRIEND engine is a new implementation of the FRIEND software, a fMRI neurofeedback processing package that has been on the NITRC website since Oct 2013.

Cost / License

  • Free
  • Open Source

Application type

Platforms

  • Mac
  • Windows
  • Linux
  • Python
  • Unity
  • MATLAB
-
No reviews
0likes
0comments
0news articles

Features

Suggest and vote on features
No features, maybe you want to suggest one?

 Tags

  • mental-health
  • medical
  • neurofeedback
  • mri
  • neuroscience

FRIEND Engine News & Activities

Highlights All activities

Recent activities

No activities found.

FRIEND Engine information

  • Developed by

    Unknown
  • Licensing

    Open Source and Free product.
  • Written in

  • Alternatives

    10 alternatives listed
  • Supported Languages

    • English

AlternativeTo Categories

Sport & HealthEducation & Reference

GitHub repository

  •  15 Stars
  •  7 Forks
  •  0 Open Issues
  •   Updated  
View on GitHub
FRIEND Engine was added to AlternativeTo by stephenfranks on and this page was last updated .
No comments or reviews, maybe you want to be first?
Post comment/review

What is FRIEND Engine?

FRIEND engine is a new implementation of the FRIEND software, a fMRI neurofeedback processing package that has been on the NITRC website since Oct 2013. Its aim is to create a cross-platform framework for a real time neurofeedback processing pipeline that permits interoperability with other applications (e.g.: games engines for the creation of virtual scenarios) and the inclusion of new processing methods through the use of plug-ins provided with the distribution or developed and shared by FRIEND engine users.

The FRIEND engine framework consists of three main parts. The first one is the front end that is responsible for presenting the neurofeedback information to the subject. The second one is the core engine, a multithread application server that listens to a TCP/IP port for request commands issued by the front end and performs the associated command processing. The third one is the plug-in file, a dynamic library file (a .so file Linux file or a Mac OSX dylib file) that implements specific functions that are called internally by the engine at specific times during the pipeline. The engine is written in C++, whereas the front end can be written in any language by the user/researcher. They can execute on different machines as they communicate through a TCP/IP protocol.