Just Another Tool for Online Studies
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
stdout
jatos.
now, but old-style names are still supported.X-Forwarded-*
HTTP headers (X-Forwarded-Proto
, X-Forwarded-For
, X-Forwarded-Ssl
) (easier to run JATOS in complex system layouts)Previous releases: github.com/JATOS/JATOS/releases
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
stdout
jatos.
now, but old-style names are still supported.X-Forwarded-*
HTTP headers (X-Forwarded-Proto
, X-Forwarded-For
, X-Forwarded-Ssl
) (easier to run JATOS in complex system layouts)Previous releases: github.com/JATOS/JATOS/releases
This is a alpha release. Do not use.
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
stdout
jatos.
now, but old-style names are still supported.X-Forwarded-*
HTTP headers (X-Forwarded-Proto
, X-Forwarded-For
, X-Forwarded-Ssl
) (easier to run JATOS in complex system layouts)Previous releases: github.com/JATOS/JATOS/releases
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
stdout
jatos.
now, but old-style names are still supported.X-Forwarded-*
HTTP headers (X-Forwarded-Proto
, X-Forwarded-For
, X-Forwarded-Ssl
) (easier to run JATOS in complex system layouts)Previous releases: github.com/JATOS/JATOS/releases
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
stdout
jatos.
now, but old-style names are still supported.X-Forwarded-*
HTTP headers (X-Forwarded-Proto
, X-Forwarded-For
, X-Forwarded-Ssl
) (easier to run JATOS in complex system layouts)Previous releases: github.com/JATOS/JATOS/releases
If you want to update a JATOS server from version < 3.7.1 read the release information from v3.7.x first.
Try out the new version on cortex.jatos.org.
Previous releases: github.com/JATOS/JATOS/releases
Warning 1: Do not update your JATOS while studies are running. Wait for them until they are finished and then update. Updating while studies are running will break those study runs and result data will probably be lost.
Warning 2: If you are using study links with preview (the ones with ?pre
in the URL) - they won't trigger a preview anymore (although they will still work and start the study run). The preview setting moved to the Study Properties.
Info 1: If you are using Nginx with JATOS you might have to change the location
directive for Websockets to "/(jatos/testWebSocket|publix/[a-z0-9-]+/(group/join|batch/open))"
.
Info 2: The update procedure might take longer than usual depending on the number of workers you currently have stored in your JATOS. The time that the update will take is difficult to estimate but to give an example in one instance 65.000 workers took around 90 minutes to update. You can follow the progress in JATOS' log in logs/application.log
.
Try out the new version on cortex.jatos.org.
Info: Depending on your database size the JATOS update procedure can take a couple minutes since some database rows have to be updated. You can check the progress in JATOS log logs/application.log
.
<scripts>
jatos.startComponentByTitle
(starts the component by specifying its title)?pre
don't work anymore)Previous releases: github.com/JATOS/JATOS/releases
For testing purpose only
This version includes the JATOS API.
Warning 1: Do not update your JATOS while studies are running. Wait for them until they are finished and then update. Updating while studies are running will break those study runs and result data will probably be lost.
Warning 2: If you are using study links with preview (the ones with ?pre
in the URL) - they won't trigger a preview anymore (although they will still work and start the study run). The preview setting moved to the Study Properties.
Info 1: If you are using Nginx with JATOS you might have to change the location
directive for Websockets to "/(jatos/testWebSocket|publix/[a-z0-9-]+/(group/join|batch/open))"
.
Info 2: The update procedure might take longer than usual depending on the number of workers you currently have stored in your JATOS. The time that the update will take is difficult to estimate but to give an example in one instance 65.000 workers took around 90 minutes to update. You can follow the progress in JATOS' log in logs/application.log
.
Try out the new version on cortex.jatos.org.
Info: Depending on your database size the JATOS update procedure can take a couple minutes since some database rows have to be updated. You can check the progress in JATOS log logs/application.log
.
<scripts>
jatos.startComponentByTitle
(starts the component by specifying its title)?pre
don't work anymore)Previous releases: github.com/JATOS/JATOS/releases