NIfTI Support | This release further integrates import and export of NIfTI files. There is now an "Open NIfTI" icon in the main toolbar to open NIfTI files quickly. More data types are now also supported including unsigned short and double values. There is now also direct support to process NIfTI volume maps (see below) usually containing float or double values and an intent code specifying a statistical distribution. In case that a volume map file is opened via the "Open NIfTI" icon (or the respective item in the “File” menu), a BrainVoyager volume map is created and attached to a pseudo-VMR document that is created from the same data. This is necessary since a volume map in BrainVoyager can only be linked to a VMR file. It is now also possible to save NIfTI files either compressed (.nii.gz, default) or uncompressed (.nii) by selecting the respective option in the "Saving NIfTI files from BV documents" field in the "NIfTI" tab of the "Settings" / "Preferences" dialog. |
NIfTI Volume Map Files | It is now possible to directly save and load (statistical) NIfTI volume maps from the "Volume Maps" dialog. When exporting VMP data containing multiple maps, each sub-map is exported as a separate NIfTI file. Saving volume maps in normalised (MNI, ACPC, TAL) space as NIfTI file(s) does not resample the VMP float values, i.e. the map is stored in the current volume space except that the BV orientation is converted into neurological RAS orientation. BrainVoyager saves an identity matrix as the orientation (sform) matrix multiplied by scaling values reflecting the relative resolution of the map with respect to the spatial resolution of the hosting anatomy. For details, see topic "NIfTI Volume Map Files" in chapter "Coordinates and Transformations" of the updated User’s Guide. |
Huge GLM Files | It is now possible to create, load and visualize GLM files larger than 4 GB as long as enough working memory is available. Huge GLMs may be obtained when analyzing functional data volumes with large dimensions, as used in high-resolution fMRI, combined with a large number of predictors e.g. when calculating separate subject GLMs with many subjects and study predictors. |
Installing Missing Plugins and Scripts | When installing BrainVoyager, plugins and scripts are stored in the "BVExtensions" folder inside the current user’s "Documents" folder. In case that another user logs in, the plugins and scripts will not be available in this user’s "Documents/BVExtensios" folder. This release now detects and informs the user about this situation providing a dialog with instructions to install a copy of the "BVExtensions" folder from our web site in the user’s local "Documents" folder. |
Sphere ROI | When defining a sphere ROI from the context menu of a VMR View, a dialog will be shown that allows setting the radius of the created sphere. This avoids adjusting the radius in the "Spherical ROI Definition" section in the "Settings" tab of the "Volume Tools Options" dialog (which also allows to switch between drawing directly into the VMR or (default) drawing a VOI). The adjusted radius will be stored permanently as the new default for subsequent sphere ROI definitions. Since ROIs are generated as VOIs , the name and color of the created ROI can be changed in the "Volume-Of-Interest Analysis" dialog. |
Auto-Balancing GLM Contrasts | When defining contrasts in the "Overlay GLM Contrasts" dialog, contrasts are balanced on the fly, i.e. it is no longer necessary to click the "Balance +/-" button to balance the selected positive and negative predictor sets. |
Auto-Save MDMs | Multi-study design matrix (MDM) files are now stored automatically when using the "General Linear Model: Multi Study, Multi Subject" dialog in a similar way as is available for single-study (SDM) files when using the "Single Study General Linear Model" dialog. The auto-saved MDM name will keep the same information (e.g. GLM type, time course normalisation setting, AR setting) as the auto-saved GLM name. The auto-saved file name is also suggested as initial file name when using the "Save MDM" in the multi-study GLM dialog. |
Generated VTC File Names | When creating VTC files, the automatically suggested resulting file names now include not only the target space (e.g. NATIVE, ACPC, TAL, MNI) but also the target cube dimension, spatial resolution and used interpolation method (nearest neighbour, trilinear, since); the file name "[core-file-name]_512_sinc3_2x0.4_TAL.vtc", for example, indicates that a high-resolution VTC is generated with a target cube dimension of 512, that the data is interpolated using sinc interpolation and a spatial resolution of 0.8. The spatial resolution is expressed with the value of the VTC resolution relative to the hosting VMR resolution (e.g. "2") times the resolution of the VMR itself ("0.4"), hence "2x0.4", i.e. the resulting VTC voxel will have a resolution of 0.8 x 0.8 x 0.8. For standard resolution (1 mm) VMRs, the suggested file name will look similar to "[core-file-name]_256_sinc3_2x1.0_MNI.vtc". |