GLM-Express
This is a package for modeling functional neuroimaging tasks. As the name implies, it's optimized to be simple and straightforward! The task_information.json file stores all of the regressors and modeling specifications for each task; modifying this file allows you to test a range of analytical outcomes.
Included
This package comes equipped with the following modeling objects:
Subjectis a first-level modeler for subject-specific functional neuroimaging dataGroupLevelis a second-level modeler that is optimized to aggregate contrast maps derived by theSubjectobjectAggregatorapplies first-level models to all subjects in your BIDS project (not efficient for larger datasets)RestingStatefor analyses of subject-level resting state functional connectivity
Assumptions
We assume the following about your data:
- Your data is in valid
BIDSformat - Your data has been preprocessed via
fmriprep - Your preprocessed data are stored in a
derivativesfolder nested in yourBIDSproject - You have adequate events TSV files for all of your functional tasks
- Any parametric modulators are stored within each event file
- Otherwise, you can build custom design matrices and feed them into the modeling function
About task_information.json
Glossary of keys in the task_information file; manipulating these allow you to quickly and effectively customize your modeling parameters without editing any source code
tr: Repetition time (defined here, but can be overriden for any one subject)excludes: Subjects in your project you need to exclude for a given taskcondition_identifier: Column in your events file that denotes trial type; NOTE this will be changed totrial_typein the scriptconfound_regressors: Regressors to include fromfmriprepoutputmodulators: Parametric modulators to weight trial type (these should be in your events file)block_identifier: Column in your events file that denotes block type; defaults tonulldesign_contrasts: Your defined contrasts! Include as few or as many as you see fit
Metadata
Release files for glm-express 2.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| glm_express-2.0.3.tar.gz | 27.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| glm_express-2.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.4 kB
Release files / glm_express-2.0.3.tar.gz
| Download URL | glm_express-2.0.3.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a87b2d81d93754e7b745bb5ea233ee8e5df5da14bd17613e480846ab2405a15
|
|
BLAKE2b-256 checksum How to use checksums |
84567280a140a39edf83474cd783813761c7855550b7b105b8c4e172df8428e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.7.0
|
Release files / glm_express-2.0.3-py3-none-any.whl
| Download URL | glm_express-2.0.3-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
546ad1416856129a05ef9b73b06e51f45369016fb2acad17671bd654a194fa25
|
|
BLAKE2b-256 checksum How to use checksums |
2e6894046cb9df8d03b9f8c3bb0f855f3a3ca8ffadfe32c0f4fd85f7eec0d894
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.7.0
|
Security for glm-express 2.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.