Neurethic - Contributions [fr]

AAGRIP

2023-10-13T07:55:12Z

10.227.0.48 : /* Software */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
* comment on assure synchro entre image et son d'une vidéo ?
* qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
* Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

Psychopy have 4 different back-ends to handle video files : ffpyplayer, moviepy, opencv, vlc

*ffpyplayer : bug if there is no sound file or if it's corrupted

*moviepy : lot of errors

*opencv : works even without audio file but if we use the static component to preload the video, the audio part launchs briefly at the preload time.

*vlc : error during the initialisation, it may need additionnal package

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

AAGRIP

2023-10-12T14:29:38Z

10.227.0.48 : /* AAGRIP */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
* comment on assure synchro entre image et son d'une vidéo ?
* qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
* Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

Psychopy have 4 different back-ends to handle video files : ffpyplayer, moviepy, opencv, vlc

*ffpyplayer : bug if there is no sound file or if it's corrupted

*moviepy : lot of errors

*opencv : works even without audio file but if we use the static component to preload the video, the audio part launchs briefly at the preload time.

vlc : error during the initialisation, it may need additionnal package

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

AAGRIP

2023-10-12T14:29:30Z

10.227.0.48 : /* The project */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
*comment on assure synchro entre image et son d'une vidéo ?
*qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
*Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

Psychopy have 4 different back-ends to handle video files : ffpyplayer, moviepy, opencv, vlc

*ffpyplayer : bug if there is no sound file or if it's corrupted

*moviepy : lot of errors

*opencv : works even without audio file but if we use the static component to preload the video, the audio part launchs briefly at the preload time.

vlc : error during the initialisation, it may need additionnal package

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

AAGRIP

2023-10-12T14:29:10Z

10.227.0.48 : /* The project */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
::- comment on assure synchro entre image et son d'une vidéo ?
::- qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
::- Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

Psychopy have 4 different back-ends to handle video files : ffpyplayer, moviepy, opencv, vlc

*ffpyplayer : bug if there is no sound file or if it's corrupted

*moviepy : lot of errors

*opencv : works even without audio file but if we use the static component to preload the video, the audio part launchs briefly at the preload time.

vlc : error during the initialisation, it may need additionnal package

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

AAGRIP

2023-10-12T14:23:52Z

10.227.0.48 : /* Software */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
- comment on assure synchro entre image et son d'une vidéo ?
- qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
- Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

Psychopy have 4 different back-ends to handle video files : ffpyplayer, moviepy, opencv, vlc

*ffpyplayer : bug if there is no sound file or if it's corrupted

*moviepy : lot of errors

*opencv : works even without audio file but if we use the static component to preload the video, the audio part launchs briefly at the preload time.

vlc : error during the initialisation, it may need additionnal package

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

AAGRIP

2023-10-12T12:39:03Z

10.227.0.48 : /* Materials */

== AAGRIP ==
[[File:Yoda Grip Force.png|thumb|May the gripforce be with you]]
=== The project ===
on décrit le projet ici ?

grandes questions :
- comment on assure synchro entre image et son d'une vidéo ?
- qu'est ce qui affecte le signal de nos capteurs de force dans notre setup ? Comment on le corrige au mieux ?
- Est ce que les latences observées pour l'affichage des stimuli n'affectent pas nos données ?

== Materials or Hardware ==

=== Acquisition Cards ===
NI acquisition cards -> drivers only available on Windows and not on Linux

=== Screen ===
Check the refresh rate of the screen used. The refresh rate may be less than advertised if you don't use a display port cable.

Operating systems usually have a software permanently running to handle the display of the screen. This software can disturb experiment framework to ensure the vertical synchronisation of the screen. On Windows, this software, the Desktop Windows Manager (DWM), prevent the Psychtoolbox to guarantee the constant vertical frame rate of the screen.

=== F/T Sensors ===

Power supply of the computer affects the quality of the signal collected with f/t sensors

=== Arduino ===

=== Troubleshootings ===

== Software ==

=== Experiment frameworks ===
Framework available to build experiment : Psychopy, Psychtoolbox, OpenSesame

Psychopy and OpenSesame rely on Python unlike Psychtoolbox which relies on Matlab.

We chose Psychopy for our project because the package already offers some interesting functionalities such as stimuli pre-loading, interval between frames recording, time blocked until the screen is fully displayed, ... Besides, as it relies on Python, it's easier to custom our script to add hardware and/or LSL trigger.

Stimuli pre-loading is handled with the static component in the builder interface of psychopy and it allows us to avoid the delay between the start of the trial and the launch of the stimulus which will depends on the kind and the size of the stimuls.

Psychopy experiment can be launched by command line if you execute the python file in the psychopy installation folder. Create a python virtual environment with the psychoy package doesn't seems to work to launch experiment in it.

(Psychopy seems to keep a lot of things in RAM when you run an experiment multiple times so it may be better to restart it regularly)

=== LSL ===

-> à intégrer à l'expérience

=== Troubleshootings ===

<ref>Une référence [https://fr.wikipedia.org/w/index.php?title=Pierre-Eudoxe_Dubalen&veaction=edit] </ref>
<references />

Main Page

2023-10-12T12:38:25Z

10.227.0.48 :

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

== AAGRIP ==

blabla sur le projet [[AAGRIP]]