Contents
Interactive analysis of the MEG/EEG data and source estimates is facilitated by the mne_analyze tool. Its features include:
See mne_analyze for command line options.
Note
Before starting mne_analyze the SUBJECTS_DIR
environment variable has to be set.
The main window of mne_analyze shown in The main window of mne_analyze. has the following components:
When you select Open... from the File menu the data loading dialog shown in The open dialog. appears. It has four sections:
inv
.mri/T1-neuromag/sets
under the subject’s
FreeSurfer directory. The Default button
uses the default transformation file which must be called $SUBJECTS_DIR/$SUBJECT/bem/$SUBJECT-trans.fif
.
This can be one of the MRI description files in mri/T1-neuromag/sets
or
a transformation file stored from mne_analyze ,
see Coordinate frame alignment.After the data set(s) has been selected, the following actions will take place:
If multiple data sets are loaded each data set has the following individual settings:
If a data set has not been previously displayed, the currently active settings are copied to the data set.
Note
If you double click on an inverse operator file name displayed in the Inverse operator list, the command used to produced this file will be displayed in a message dialog.
Instead of an evoked-response data file it is possible to load epochs of data (single trials) from a raw data file. This option is invoked from File/Open raw... . The file selection box is identical to the one used for evoked responses (The open dialog.) except that data set selector is replaced by the epoch selector show in The raw data epoch selector..
The epoch selector contains the following controls:
Once the settings have been accepted by clicking OK , the first matching epoch will be displayed. You can switch between epochs using the data set list accessible through Switch to data set... in the File menu.
The MEG and EEG signals can be viewed in two ways:
In both the sample channel display and the topographical display, current time point can be selected with a left mouse click. In addition, time point of interest can be entered numerically in the text box at the bottom left corner of the main display.
A selection of channels is always shown in the right most part of the main display. The topographical layout to use is selected from Adjust/Select trace layout... , which brings up a window with a list of available layouts. The system-wide layouts reside in $MNE_ROOT/share/mne_analyze/lout. In addition any layout files residing in $HOME/.mne/lout are listed. The format of the layout files and selection of the default layout is discussed in Full view layout.
Several actions can be performed with the mouse in the topographical data display:
Left button click
Selects a time point of interest.
Left button click with control key
Selects a time point of interest and selects the channel under the pointer to the sample channel display.
Left button drag with shift key
Enlarges the view to contain only channels in the selected area.
Middle button click or drag
Marks this channel as bad and clears all previously marked bad channel. This action is only available if an inverse operator is not loaded. An inverse operator dictates the selection of bad channels. The current bad channel selection can be applied to the data from File/Save bad channel selection .
Middle button click or drag with control key
Extends the bad channel selection without clearing the previously active bad channels.
Right button
Adjusts the channel selection used for dipole fitting in the same way as the middle button selects bad channels. For more information on channel selections, see Channel selections.
The sample channel display shows one of the measurement channels at the upper left corner of the mne_analyze user interface. A time point can be selected with a left mouse click. In addition, the following keyboard functions are associated with the sample channel display:
Down
Change the sample channel to the next channel in the scanning order.
Up
Change the sample channel to the previous channel in the scanning order.
Right
Move forward in time by 1 ms.
Control Right
Move forward in time by 5 ms.
Left
Move backward in time by 1 ms.
Control Left
Move backward in time by 5 ms.
The scales of the topographical and sample channel display can be adjusted from the Scales dialog which is invoked by selecting Adjust/Scales... from the menus. The Scales dialog shown in The Scales dialog. has the following entries:
Analyze range min [ms]
Specifies the lower limit of the time range of data to be shown.
Analyze range max [ms]
Specifies the upper limit of the time range of data to be shown.
Use full time range
If this box is checked, all data available in the data file will be shown.
Baseline min [ms]
Specifies the lower time limit of the baseline.
Baseline max [ms]
Specifies the upper time limit of the baseline.
Baseline in use
Baseline subtraction can be switched on and off from this button.
MEG amp min [fT/cm]
Lower limit of the vertical scale of planar gradiometer MEG channels.
MEG amp max [fT/cm]
Upper limit of the vertical scale of planar gradiometer MEG channels.
MEG axmult [cm]
The vertical scale of MEG magnetometers and axial gradiometers will be obtained by multiplying the planar gradiometer vertical scale limits by this value, given in centimeters.
EEG amp min [muV]
Lower limit of the vertical scale of EEG channels.
EEG amp max [muV]
Upper limit of the vertical scale of EEG channels.
Show stimulus channel
Show the digital trigger channel data in the sample view together with the sample channel.
In mne_analyze , the current estimates are visualized on inflated or folded cortical surfaces. There are two visualization displays: the surface display, which is always visible, and the 3D viewer which is invoked from the Windows/Show viewer... menu selection, see The viewer.
A total of eight surfaces or patches can be assigned to the surface display:
When File/Load surface... or File/Load morphing surface... is invoked, the surface selection dialog shown in The surface selection dialog. appears.
The dialog has the following components:
List of subjects
This list contains the subjects available in the directory set with theSUBJECTS_DIR
environment variable.
List of available surfaces for the selected subject
Lists the surfaces available for the current subject. When you click on an item in this list, it appears in the Selected surface text field.
x-rotation (deg)
Specifies the initial rotation of the surface around the x (left to right) axis. Positive angle means a counterclockwise rotation when the surface is looked at from the direction of the positive x axis. Sometimes a more pleasing visualization is obtained when this rotations are specified when the surface is loaded.
y-rotation (deg)
Specifies the initial rotation of the surface around the y (back to front) axis.
z-rotation (deg)
Specifies the initial rotation of the surface around the z (bottom to up) axis.
The surface patches are loaded with help of the patch selection dialog, which appears when File/Load surface patch... or File/Load morphing surface patch... is selected. This dialog, shown in The patch selection dialog., contains a list of available patches and the possibility to rotate the a flat patch counterclockwise by the specified number of degrees from its original orientation. The patch is automatically associated with the correct hemisphere on the basis of the two first letters in the patch name (lh = left hemisphere, rh = right hemisphere).
The main surface display has a section called Adjust view , which has the controls shown in Surface controls.:
L and R
Select the left or right hemisphere surface loaded through File/Load surface... .
B
Display the surfaces for both hemispheres.
M
Display the surfaces loaded File/Load morphing surface... according to the L, R, and B hemisphere selectors
P
Select the patch associated with the currently selected surface. For this to work, either L or R must be selected.
Option menu
Select one of the predefined view orientations, see Defining viewing orientations, below.
Arrow buttons
Rotate the surface by increments specified in degrees in the text box next to the arrows.
The display can be also adjusted using keyboard shortcuts, which are available once you click in the main surface display with the left mouse button to make it active:
Arrow keys
Rotate the surface by increments specified in degrees in the Adjust View section.
+
Enlarge the image.
-
Reduce the image.
=
Return to the default size.
r
Rotate the image one full revolution around z axis using the currently specified rotation step. This is useful for producing a sequence of images when automatic image saving is on, see Producing output files.
s
Produces a raster image file which contains a snapshot of the currently displayed image. For information on snapshot mode, see Producing output files.
.
Stops the rotation invoked with the ‘r’ key, see above.
In addition, the mouse wheel or trackball can be used to rotate the image. If a trackball is available, e.g., with the Apple MightyMouse, the image can be rotated up and down or left and right with the trackball. With a mouse wheel the image will rotated up and down when the wheel is rotated. Image rotation in the left-right direction is achieved by holding down the shift key when rotating the wheel. The shift key has the same effect on trackball operation.
Note
The trackball and mouse wheel functionality is dependent on your X server settings. On Mac OSX these settings are normally correct by default but on a LINUX system some adjustments to the X server settings maybe necessary. Consult your system administrator or Google for details.
When you click on the surface with the left mouse button, the corresponding vertex number and the associated value will be displayed on the message line at the bottom of the display. In addition, the time course at this vertex will be shown, see Timecourses at vertices. You can also select a vertex by entering the vertex number to the text field at the bottom of the display. If the MRI viewer is displayed and Track surface location in MRI is selected in the MRI viewer control dialog, the cursor in the MRI slices will also follow the vertex selection, see Working with the MRI viewer.
The View menu choice Show coordinates... brings up a window which shows the coordinates of the selected vertex on the white matter surface, i.e., lh.white and rh.white FreeSurfer surfaces. If morphing surfaces have been loaded, the coordinates of both the subject being analyzed and those of the morphing subject will be shown. The Coordinates window includes the following lines:
MEG head
Indicates the vertex location in the MEG head coordinates. This entry will be present only if MEG/EEG data have been loaded.
Surface RAS (MRI)
Indicates the vertex location in the Surface RAS coordinates. This is the native coordinate system of the surfaces and this entry will always be present.
MNI Talairach
Shows the location in MNI Talairach coordinates. To be present, the MRI data of the subject must be in the mgz format (usually true with any recent FreeSurfer version) and the Talairach transformation must be appropriately defined during the FreeSurfer reconstruction workflow.
Talairach
Shows the location in the FreeSurfer Talairach coordinates which give a better match to the Talairach atlas.
The above coordinate systems are discussed in detail in MEG/EEG and MRI coordinate systems.
Note
By default, the tksurfer program, part of the FreeSurfer package, shows the vertex locations on the orig rather than white surfaces. Therefore, the coordinates shown in mne_analyze and tksurfer are by default slightly different (usually by < 1 mm). To make the two programs consistent, you can start tksurfer with the -orig white
option.
The list of viewing orientations available in the Adjust View section of the main surface display is controlled
by a text file. The system-wide defaults reside in $MNE_ROOT/share/mne/mne_analyze/eyes
.
If the file $HOME/.mne/eyes
exists, it is used instead.
All lines in the eyes file starting with # are comments. The view orientation definition lines have the format:
<name>:<Left>:<Right>:<Left up>:<Right up> ,
where
<*name*>
is the name of this viewing orientation,
<*Left*>
specifies the coordinates of the viewing ‘eye’ location for the left hemisphere, separated by spaces,
<*Right*>
specifies the coordinates of the viewing location for the right hemisphere,
<*Left up*>
specifies the direction which is pointing up in the image for left hemisphere, and
<*Right up*>
is the corresponding up vector for the right hemisphere.
All values are given in a coordinate system where positive x points to the right, positive y to the front, and positive z up. The lengths of the vectors specified for each of the four items do not matter, since parallel projection is used and the up vectors will be automatically normalized. The up vectors are usually 0 0 1, i.e., pointing to the positive z direction unless the view is directly from above or below or if some special effect is desired.
The names of viewing orientations should be less than 9 characters long. Otherwise, the middle pane of the main display will not be able to accommodate all the controls. The widths of the main window panes can be adjusted from the squares at the vertical sashes separating the panes.
The scenes shown in the main surface display and the viewer, described in The viewer, are lit by fixed diffuse ambient lighting and a maximum of eight light sources. The states, locations, and colors of these light sources can be adjusted from the lighting adjustment dialog shown in The lighting adjustment dialog., which can be accessed through the Adjust/Lights... menu choice. The colors of the lights can be adjusted numerically or using a color adjustment dialog accessible through the Color... buttons.
Three types of output files can be produced from the main surface display using the graphics output buttons shown in Graphics output controls.:
w files (w button)
These files are simple binary files, which contain a list of vertex numbers on the cortical surface and their current data values. The w files will be automatically tagged with-lh.w
and-rh.w
. They will only contain vertices which currently have a nonzero value.
Graphics snapshots (img button)
These files will contain an exact copy of the image in tif or rgb formats. The output format and the output mode is selected from the image saving dialog shown in File type selection in the image saving dialog.. For more details, see Image output modes. If snapshot or automatic image saving mode is in effect, thee img button terminates this mode.
QuickTime (TM) movies (mov button)
These files will contain a sequence of images as a QuickTime (TM) movie file. The movie saving dialog shown in The controls in the movie saving dialog. specifies the time range and the interval between the frames as well as the quality of the movies, which is restricted to the range 25...100. The size of the QuickTime file produced is approximately proportional to the quality.
The image saving dialog shown in File type selection in the image saving dialog. selects the format of the image files produced and the image output mode. The buttons associated with different image format change the file name filter in the dialog to display files of desired type. However, the final output format is defined by the ending of the file name in the Selection text field as follows:
jpg
JPEG (Joint Photographic Experts Group) format. Best quality jpeg is always produced.
tif or tiff
Uncompressed TIFF (Tagged Image File Format).
rgb
RGB format.
Portable Document File format.
png
Portable Network Graphics format.
Note
Only TIFF and RGB output routines are compiled into mne_analyze . For other output formats to work, the following programs must be present in your system: tifftopdf, tifftopnm, pnmtojpeg, and pnmtopng.
There are three image saving modes which can be selected from the option menu labelled Output mode :
Single
When OK is clicked one file containing the present image is output.
Snapshot
A new image file is produced every times
is pressed in the image window, see Controlling the surface display and Overview. The image file name is used as the stem of the output files. For example, if the name is,sample.jpg
, the output files will besample_shot_001.jpg
,sample_shot_002.jpg
, etc.
Automatic
A new image file is produced every time the image window changes. The image file name is used as the stem of the output files. For example, if the name is,sample.jpg
, the output files will besample_001.jpg
,sample_002.jpg
, etc.
The displayed surface distributions can be morphed to another subject’s brain using the spherical morphing procedure, see Morphing and averaging. In addition to the morphing surfaces loaded through File/Load morphing surface... surface patches for the same subject can be loaded through File/Load morphing surface patch... . Switching between main and morphing surfaces is discussed in Controlling the surface display.
Any labels displayed are visible on any of the surfaces displayed in the main surface display. Time points can be picked in any of the surfaces. As a result, the corresponding timecourses will be shown in the MNE amplitude window, see Inquiring timecourses.
When Windows/Show viewer... is selected, the following additional surfaces will be loaded:
The scalp surface is loaded from the file bem/
<subject>``-head.fif`` under
the subject’s FreeSurfer directory. This surface is automatically
prepared if you use the watershed algorithm as described in Using the watershed algorithm.
If you have another source for the head triangulation you can use
the utility mne_surf2bem to create
the fif format scalp surface file, see Creating the BEM meshes.
If a file called bem/
<subject>``-bem.fif`` under
the subject’s FreeSurfer directory is present, mne_analyze tries
to load the BEM surface triangulations from there. This file can
be a symbolic link to one of the -bem.files
created
by mne_prepare_bem_model , see Computing the BEM geometry data.
If the BEM file contains a head surface triangulation, it will be
used instead of the one present in the bem/
<subject>``-head.fif`` file.
Once all required surfaces have been loaded, the viewer window shown in The viewer window with a visualization of MEG and EEG contour maps. pops up. In addition to the display canvas, the viewer has Adjust view controls similar to the main surface display and options for graphics output. The Adjust view controls do not have the option menu for standard viewpoints and has two additional buttons:
The output options only include graphics output as snapshots (img ) or as movies (mov ).
Options...
This button pops up the viewer options window which controls the appearance of the viewer window.
Rescale
This button adjusts the contour level spacing in the magnetic field and electric potential contour maps so that the number of contour lines is reasonable.
Reload
Checks the modification dates of the surface files loaded to viewer and reloads the data if the files have been changed. This is useful, e.g., for display of different BEM tessellations.
The display can be also adjusted using keyboard shortcuts, which are available once you click in the viewer display with the left mouse button:
Arrow keys
Rotate the surface by increments specified in degrees in the Adjust View section.
+
Enlarge the image.
-
Reduce the image.
=
Return to the default size.
r
Rotate the image one full revolution around z axis using the currently specified rotation step. This is useful for producing a sequence of images when automatic image saving is on, see Producing output files.
s
Produces a image file which contains a snapshot of the currently displayed image. For information on snapshot mode, see Producing output files.
.
Stops the rotation invoked with the ‘r’ key, see above.
The left mouse button can be also used to inquire estimated magnetic field potential values on the helmet and head surfaces if the corresponding maps have been calculated and displayed.
In addition, the mouse wheel or trackball can be used to rotate the image. If a trackball is available, e.g., with the Apple MightyMouse, the image can be rotated up and down or left and right with the trackball. With a mouse wheel the image will rotated up and down when the wheel is rotated. Image rotation in the left-right direction is achieved by holding down the shift key when rotating the wheel. The shift key has the same effect on trackball operation.
Note
The trackball and mouse wheel functionality is dependent on your X server settings. On Mac OSX these settings are normally correct by default but on a LINUX system some adjustments to the X server settings maybe necessary. Consult your system administrator or Google for details.
The viewer options window shown above contains three main sections to control the appearance of the viewer:
The available items are:
Left hemi
The pial surface of the left hemisphere. This surface can be made transparent. Naturally, this surface will only be visible if the scalp is made transparent.
Right hemi
The pial surface of the right hemisphere.
Inner skull
The inner skull surface. This surface can be made transparent. If parts of the pial surface are outside of the inner skull surface, they will be visible, indicating that the inner skull surface is obviously inside the inner skull. Note that this criterion is more conservative than the one imposed during the computation of the forward solution since the source space points are located on the white matter surface rather than on the pial surface. This surface can be displayed only if the BEM file is present, see Overview.
Outer skull
The outer skull surface. This surface can be made transparent. This surface can be displayed only if the BEM file is present and contains the outer skull surface, see Overview.
Scalp
The scalp surface. This surface can be made transparent. The display of this surface requires that the scalp triangulation file is present, see Overview.
Digitizer data
The 3D digitizer data collected before the MEG/EEG acquisition. These data are loaded from File/Load digitizer data... . The display can be restricted to HPI coil locations and cardinal landmarks with the option. The digitizer points are shown as disks whose radius is equal to the distance of the corresponding point from the scalp surface. Points outside the scalp are shown in red and those inside in blue. Distinct shades of cold and warm colors are used for the fiducial landmarks. The HPI coils are shown in green. Further information on these data and their use in coordinate system alignment is given in Coordinate frame alignment.
Helmet
The MEG measurement surface, i.e., inner surface of the dewar.
EEG electrodes
The EEG electrode locations. These will be only available if your data set contains EEG channels.
MEG sensors
Outlines of MEG sensors.
MEG field map
Estimated contour map of the magnetic field component normal to the helmet surface or normal to the scalp, see Magnetic field and electric potential maps.
EEG potential map
Interpolated EEG potential map on the scalp surface, see Magnetic field and electric potential maps.
Activity estimates
Current estimates on the pial surface.
In mne_analyze , the magnetic field and potential maps displayed in the viewer window are computed using an MNE-based interpolation technique. This approach involves the following steps:
The magnetic field and potential maps appear automatically whenever they are enabled from the viewer options, see Viewer options.
Let \(x_k\) be an MEG or an EEG signal at channel \(k = 1 \dotso N\). This signal is related to the primary current distribution \(J^p(r)\) through the lead field \(L_k(r)\):
where the integration space \(G\) in our case is a spherical surface. The oblique boldface characters denote three-component locations vectors and vector fields.
The inner product of two leadfields is defined as:
These products constitute the Gram matrix \(\Gamma_{jk} = \langle L_j \mid L_k \rangle\). The minimum -norm estimate can be expressed as a weighted sum of the lead fields:
where \(w\) is a weight vector and \(L\) is a vector composed of the continuous lead-field functions. The weights are determined by the requirement
i.e., the estimate must predict the measured signals. Hence,
However, the Gram matrix is ill conditioned and regularization must be employed to yield a stable solution. With help of the SVD
a regularized minimum-norm can now found by replacing the data matching condition by
where
respectively. In the above, the columns of \(U^{(p)}\) are the first k left singular vectors of \(\Gamma\). The weights of the regularized estimate are
where \(\Lambda^{(p)}\) is diagonal with
\(\lambda_j\) being the \(j\) th singular value of \(\Gamma\). The truncation point \(p\) is selected in mne_analyze by specifying a tolerance \(\varepsilon\), which is used to determine \(p\) such that
The extrapolated and interpolated magnetic field or potential distribution estimates \(\hat{x'}\) in a virtual grid of sensors can be now easily computed from the regularized minimum-norm estimate. With
where \(L_j'\) are the lead fields of the virtual sensors,
The parameters of the field maps can be adjusted from the Field mapping preferences dialog shown in Field mapping preferences dialog. which is accessed through the Adjust/Field mapping... menu item.
The Field mapping preferences dialog has the following controls, arranged in MEG , EEG , and common sections:
SVD truncation at
Adjusts the smoothing of the field and potential patterns. This parameter specifies the eigenvalue truncation point as described in Technical description. Smaller values correspond to noisier field patterns with less smoothing.
Use default origin
The location of the origin of the spherical head model used in these computations defaults to (0 0 40) mm. If this box is unchecked the origin coordinate fields are enabled to enter a custom origin location. Usually the default origin is appropriate.
Downsampling grade
This option only applies to EEG potential maps and MEG field maps extrapolated to the head surface and controls the number of virtual electrodes or point magnetometers used in the interpolation. Allowed values are: 2 (162 locations), 3 (642 locations), and 4 (2562 locations). Usually the default value 3 is appropriate.
Number of smoothsteps
This option controls how much smoothing, see About smoothing, is applied to the interpolated data before computing the contours. Usually the default value is appropriate.
Reconstruction surface radius
Distance of the spherical reconstruction surface from the sphere model origin. Usually default value is appropriate. For children it may be necessary to make this value smaller.
The characteristics of the current estimates displayed are controlled from the MNE preferences dialog which pops up from Adjust/Estimates... .
This dialog, shown in Estimate preferences dialog., has the following controls:
SNR estimate
This controls the regularization of the estimate, i.e., the amount of allowed mismatch between the measured data and those predicted by the estimated current distribution. Smaller SNR means larger allowed mismatch. Typical range of SNR values is 1...7. As discussed in Minimum-norm estimates, the SNR value can be translated to the current variance values expressed in the source-covariance matrix R. This translation is presented as the equivalent current standard-deviation value
Show
This radio button box selects the quantity to display. MNE is the minimum norm estimate (estimated value of the current), dSPM is the noise-normalized MNE, and sLORETA is another version of the noise-normalized solution which is claimed to have a smaller location bias than the dSPM.
Mask with
If MNE is selected in the Show radio button box, it is possible to mask the solution with one of the statistical maps. The masking map is thresholded at the value given in the Threshold text field and the MNE is only shown in areas with statistical values above this threshold.
Value histogram
This part of the dialog shows the distribution of the currently shown estimate values over the surface. The histogram is colored to reflect the current scale settings. The fthresh , fmid , and fmax values are indicated with vertical bars. The histogram is updated when the dialog is popped up and when the estimate type to show changes, not at every new time point selection. The Refresh button makes the histogram current at any time.
Color scale
These text fields control the color scale as described in The color scale parameters..
Options
Various options controlling the estimates.
| Parameter | Meaning |
|---|---|
| fthresh | If the value is below this level, it will not be shown. |
| fmid | Positive values at this level will show as red. Negative values will be dark blue. |
| fmax | Positive values at and above this level will be bright yellow. Negative values will be bright blue. |
| fmult | Apply this multiplier to the above thresholds. Default is \(1\) for statistical maps and \(1^{-10}\) for currents (MNE). The vertical bar locations in the histogram take this multiplier into account but the values indicated are the threshold parameters without the multiplier. |
| tcmult | The upper limit of the timecourse vertical scale will be \(tc_{mult}f_{mult}f_{max}\). |
The optional parameters are:
Retain sign
With this option, the sign of the dot product between the current direction and the cortical surface normal will be used as the sign of the values to be displayed. This option yields meaningful data only if a strict or a loose orientation constraint was used in the computation of the inverse operator decomposition.
Retain normal component only
Consider only the current component normal to the cortical mantle. This option is not meaningful with completely free source orientations.
Show scale bar
Show the color scale bar at the lower right corner of the display.
Show comments
Show the standard comments at the lower left corner of the display.
Time integr. (ms)
Integration time for each frame (\(\Delta t\)). Before computing the estimates time integration will be performed on sensor data. If the time specified for a frame is \(t_0\), the integration range will be \(t_0 - ^{\Delta t}/_2 \leq t \leq t_0 + ^{\Delta t}/_2\).
# of smooth steps
Before display, the data will be smoothed using this number of steps, see About smoothing.
Opacity
The range of this parameter is 0...1. The default value 1 means that the map overlaid on the cortical surface is completely opaque. With lower opacities the color of the cortical surface will be visible to facilitate understanding the underlying folding pattern from the curvature data displayed.
The SNR estimate display shows the SNR estimated from the whitened data in red and the apparent SNR inferred from the mismatch between the measured and predicted data in green.
The SNR estimate is computed from the whitened data \(\tilde{x}(t)\), related to the measured data \(x(t)\) by
where \(C^{-^1/_2}\) is the whitening operator, introduced in Whitening and scaling.
The computation of the apparent SNR will be explained in future revisions of this manual.
Timecourses at individual vertices can be inquired by clicking on a desired point on the surface with the left mouse button. If the control key was down at the time of a click, the timecourse will be added to the timecourse manager but left off. With both control and shift down, the timecourse will be added to the timecourse manager and switched on. For more information on the timecourse manager, see The timecourse manager.
The timecourses are be affected by the Retain sign and Retain normal component only settings in the MNE preferences dialog , see Preferences.
The labels provide means to interrogate timecourse information
from ROIs. The label files can be created in mne_analyze ,
see Creating new label files or in tksurfer ,
which is part of the FreeSurfer software. For mne_analyze left-hemisphere
and right-hemisphere label files should be named <name> -lh.label
and <name> -rh.label
,
respectively.
Individual label files can be loaded from Labels/Load label... . All label files in a directory can be loaded from Labels/Load all labels... . Once labels are loaded, the label list shown in The label list. appears. Each time a new label is added to the list, the names will be reordered to alphabetical order. This list can be also brought up from Labels/Show label list . The list can be cleared from Labels/Discard all labels .
Warning
Because of the format of the label files mne_analyze can not certify that the label files loaded belong to the cortical surfaces of the present subject.
When a label is selected from the label list, the corresponding timecourse appears. The Keep button stores the timecourse to the timecourse manager, The timecourse manager.
The timecourse shown in the MNE amplitude window is a compound measure of all timecourses within a label. Two measures are available:
Average
Compute the average over all label vertices at each time point.
Maximum
Compute the maximum absolute value over all vertices at each time point. If the data are signed, the value is assigned the sign of the value at the maximum vertex. This may make the timecourse jump from positive to negative abruptly if vertices with different signs are included in the label.
L2 norm (sample by sample)
Compute the \(l_2\) norm over the values in the vertices at each time point.
Pick vertex with largest L2 norm over time
Compute the \(l_2\) norm over time in each vertex and show the time course at the vertex with the largest norm.
The timecourse manager shown in The timecourse manager. has the following controls for each timecourse stored:
Numbered checkbox
Switches the display of this timecourse on and off.
Color...
This button shows the color of the timecourse curve. The color can be adjusted from the color editor which appears when the button is pressed.
Save...
Saves the timecourse. If a single vertex is selected, the time course file will contain some comment lines starting with the the percent sign, one row of time point values in seconds and another with the data values. The format of the timecourse data is explained in Label timecourse files, below.
Forget
Delete this timecourse from memory.
When timecourse corresponding to a label is saved, the default is to save the displayed single timecourse in a format identical to the vertex timecourses. If Save all timecourses within the label is selected, the Time-by-time output output changes the output to be listed time by time rather than vertex by vertex, Include coordinates adds the vertex location information to the output file, and Include vertex numbers adds the indices of picked vertices to the output, see Label timecourse saving options.. The vertex-by-vertex output formats is summarized in Vertex-by-vertex output format. is the number of vertices, is the number of time points, is the number of comment lines, indicate the times in milliseconds, is a vertex number, are the coordinates of vertex in millimeters, and are the values at vertex . Items in brackets are only included if Include coordinates is active. In the time-by-time output format the data portion of the file is transposed..
| Line | Contents |
|---|---|
| \(1-n_{com}\) | Comment lines beginning with % |
| \(n_{com}+1\) | \(\{0.0\}[0.0\ 0.0\ 0.0] t_1 \dotso t_{n_t}\) |
| \((n_{com}+1)-(n_p+n_{com}+1)\) | \(\{p\}[x_p y_p z_p]v_p^{(1)} \dotso v_p^{(n_t)}\) |
It is easy to create new label files in mne_analyze. For this purpose, an inflated surface should be visible in the main display. Follow these steps:
-lh.label
or -rh.label
,
depending on the hemisphere on which the label is specified.In addition to source estimates derived from MEG and EEG data, mne_analyze can be used to display other surface-based data. These overlay data can be imported from w and stc files containing single time slice (static) and dynamic data (movies), respectively. These data files can be produced by mne_make_movie , FreeSurfer software, and custom programs or Matlab scripts.
The names of the files to be imported should end with -
<hemi> .<type> , where <hemi> indicates
the hemisphere (lh
or rh
and <type> is w
or stc
.
Overlays are managed from the dialog shown in The overlay management dialog. which is invoked from File/Manage overlays... .
This dialog contains the following controls:
List of overlays loaded
Lists the names of the overlays loaded so far.
Load w...
Load a static overlay from a w file. In the open dialog it is possible to specify whether this file contains data for the cortical surface or for scalp. Scalp overlays can be viewed in the viewer window.
Load stc...
Load a dynamic overlay from an stc file. In the open dialog it is possible to specify whether this file contains data for the cortical surface or for scalp. Scalp overlays can be viewed in the viewer window.
Delete
Delete the selected overlay from memory.
Time scale slider
Will be activated if a dynamic overlay is selected. Changes the current time point.
Overlay type is
Selects the type of the data in the current overlay. Different default color scales are provided each overlay type.
Value histogram
Shows the distribution of the values in the current overlay. For large stc files this may take a while to compute since all time points are included. The histogram is colored to reflect the current scale settings. The fthresh , fmid , and fmax values are indicated with vertical bars.
Color scale
Sets the color scale of the current overlay. To activate the values, press Show . For information on color scale settings, see The color scale parameters..
Options
Display options. This a subset of the options in the MNE preferences dialog. For details, see Preferences.
Show
Show the selected overlay and assign the settings to the current overlay.
Apply to all
Apply the current settings to all loaded overlays.
It is also possible to inquire timecourses of vertices and labels from dynamic (stc) cortical overlays in the same way as from original data and store the results in text files. If a static overlay (w file) or a scalp overlay is selected, the timecourses are picked from the data loaded, if available.
Starting from MNE software version 2.6, mne_analyze includes routines for fitting current dipoles to the data. At present mne_analyze is limited to fitting single equivalent current dipole (ECD) at one time point. The parameters affecting the dipole fitting procedure are described in Dipole fitting parameters. The results are shown in the dipole list (The dipole list). The selection of channels included can be adjusted interactively or by predefined selections as described in Channel selections.
Warning
The current dipole fitting has been added recently and has not been tested comprehensively. Especially fitting dipoles to EEG data may be unreliable.
Prior to fitting current dipoles, the fitting parameters must be set with the Dipole fitting preferences dialog shown in The dipole fitting preferences dialog.. The dialog is brought up from the Setup fitting... choice in the Dipoles menu. This dialog contains three sections: Forward model , Modalities , and Noise estimate .
The Forward model section specifies the forward model to be used:
Sphere model origin x/y/z [mm]
Specifies the origin of the spherically symmetric conductor model in MEG/EEG head coordinates, see The head and device coordinate systems.
EEG scalp radius [mm]
Specifies the radius of the outermost shell in the EEG sphere model. For details, see The EEG sphere model definition file.
EEG sphere model name
Specifies the name of the EEG sphere model to use. For details, see The EEG sphere model definition file.
BEM model
Selects the boundary-element model to use. The button labeled with ... brings up a file-selection dialog to select the BEM file. An existing selection can be cleared with the Unset button. If EEG data are included in fitting, this must be a three-compartment model. Note that the sphere model is used even with a BEM model in effect, see The dipole fitting algorithm.
Accurate field calculation
Switches on the more accurate geometry definition of MEG coils, see Coil geometry information. In dipole fitting, there is very little difference between the accurate and normal coil geometry definitions.
The Modalities section defines which kind of data (MEG/EEG) are used in fitting. If an inverse operator is loaded with the data, this section is fixed and greyed out. You can further restrict the selection of channels used in dipole fitting with help of channel selections discussed in Channel selections.
The Noise estimate section of the dialog contains the following items:
Noise covariance
Selects the file containing the noise-covariance matrix. If an inverse operator is loaded, the default is the inverse operator file. The button labeled with ... brings up a file-selection dialog to select the noise covariance matrix file. An existing selection can be cleared with the Unset button.
Omit off-diagonal terms
If a noise covariance matrix is selected, this choice omits the off-diagonal terms from it. This means that individual noise estimates for each channel are used but correlations among channels are not taken into account.
Regularization
Regularize the noise covariance before using it in whitening by adding a multiple of an identity matrix to the diagonal. This is discussed in more detail in Regularization of the noise-covariance matrix. Especially if EEG is included in fitting it is advisable to enter a non-zero value (around 0.1) here.
Planar fixed [fT/cm]
In the absence of a noise covariance matrix selection, a diagonal noise covariance with fixed values on the diagonal is used. This entry specifies the fixed value of the planar gradiometers.
Axial fixed [fT]
If a noise covariance matrix file is not specified, this entry specifies a fixed diagonal noise covariance matrix value for axial gradiometers and magnetometers.
EEG fixed [muV]
If a noise covariance matrix file is not specified, this entry specifies a fixed diagonal noise covariance matrix value for axial gradiometers and magnetometers..
When the dipole fitting preferences dialog is closed and the values have been modified the following preparatory calculations take place:
When the Fit ECD button in the tool bar is clicked with a time point selected from the the response, the optimal Equivalent Current Dipole parameters (location, orientation, and amplitude) are determined using the following algorithm:
Additional notes:
mne_dipole_fit --help
lists the command-line options which have direct correspondence
to the interactive dipole fitting options discussed here.The dipole list dialog shown in The dipole list. contains the parameters of the dipoles fitted. In addition, it is possible to import current dipole locations from the Neuromag source modelling program xfit to mne_analyze . Dipoles can be imported in two ways:
The buttons at the bottom of the dialog perform the following functions:
Done
Hide the dialog.
Show
Show the currently selected dipoles as specified in Display options , see below.
Save
Save the selected (or all) dipoles. If the file name specified in the file selection dialog that pops up ends with.bdip
, the dipole data will be saved in the binary bdip format compatible with the Neuromag xfit software, otherwise, a text format output will be used. In the text file, comments will be included on lines starting with the percent sign so that the text format can be easily loaded into Matlab.
Clear
Clear the selected dipoles from the list.
When you double click on one of the dipoles or select several dipoles and click Show points on the surface displayed in the vicinity of the dipoles will be painted according to the specifications given in the Options section of the dialog:
Color
By the default, the dipoles are marked in green with transparency (alpha) set to 0.5. I you click on one of the dipoles, you can adjust the color of this dipole by editing the color values or from the color editor appearing when you click Color... . When you click Apply , the new color values are attached to the selected dipole.
Max. distance for dipoles to show (mm)
If this option is on, only dipoles which are closer to the surface than the distance specified in the adjacent text field are displayed.
Paint all point closer than (mm)
Instead of indicating the point closest to the dipole all points closer than the distance given in the text field will be painted if this option is on. This choice is useful for understanding the shape of the neighborhood of a dipole on the cortical surface.
Number of smooth steps
This option spreads out the dipole marking by the given number of smooth steps to make the dipoles more clearly visible. A suitable choice is 3 or 4.
Keep previous dipoles
If this option is on, previously marked dipoles are not cleared from the display before new ones are shown.
Note
The surface must be loaded to display dipole locations. To calculate the distance from the dipoles to the white matter surface, the white matter tessellation is loaded as needed. Depending on the precise location of the fitted dipole, the spot indicating the dipole site may easily appear on a different wall of a fissure than could be expected. The fissural walls can be far apart from each other in the inflated view of the cortex even if they are physically separated by just a few millimeters. The size of the spots indicating the dipole locations do not relate to the dipole strengths or their confidence limits in any way.
As mentioned in The topographical display, the right mouse button in the topographical display of channels can be used to restrict the selection of channels taken into account in dipole fitting. In addition, the channel selections can be manipulated in the channel selection window, which pops up from Dipoles/Manage channel selections... . Initially this dialog contains the selections defined in or $HOME/.mne/mne_analyze.sel or $MNE_ROOT/share/mne/mne_analyze/mne_analyze.sel, the personal file taking precedence over the system wide default. The Save button in this dialog save the current set of channel selections to the personal selection file. The format of this file is identical to the channel selection file in mne_browse_raw .
When a channel selection file is in effect. the variances of the unselected channels are increased by a factor of 900. This means that unselected channels receive virtually no weight in the least-squares error function or, equivalently, that they are considered to be 30 times more noisy than their true noise value. Since this implementation of channel selections requires recomputation of the initial guess candidate data discussed in The dipole fitting algorithm, above, changing the selection may take a finite amount of time, especially if a BEM is used for the forward calculation.
Note
Please note that when making a channel selection in the topographical displays, the channels not present in a particular layout are also affected. For example, if you select channels in a layout showing the Vectorview planar gradiometers, the magnetometer channels and EEG channels will be unselected.
The MRI-MEG coordinate frame alignment tools included in mne_analyze utilized the 3D digitizer (Polhemus) data acquired in the beginning of each MEG/EEG session and the scalp surface triangulation shown in the viewer window. To access the coordinate frame alignment tools:
The coordinate frame alignment dialog contains the following sections:
The saving and loading choices are:
Save default
Saves a file which contains the MEG/MRI coordinate transformation only. The file name is generated from the name of the file from which the digitization data were loaded by replacing the ending.fif
with-trans.fif
. If this file already exists, it will be overwritten without any questions asked.
Save MRI set
This option searches for a file called COR.fif in $SUBJECTS_DIR/$SUBJECT/mri/T1-neuromag/sets. The file is copied to COR-<username>-<date>-<time>.fif and the current MEG/MRI coordinate transformation as well as the fiducial locations in MRI coordinates are inserted.
Save...
Saves a file which contains the MEG/MRI coordinate transformation only. The ending-trans.fif
is recommended. The file name selection dialog as a button to overwrite.
Load...
Loads the MEG/MRI coordinate transformation from the file specified.
The MEG/MRI coordinate transformation files are employed in the forward calculations. The convenience script mne_do_forward solution described in Computing the forward solution uses a search sequence which is compatible with the file naming conventions described above. It is recommended that -trans.fif file saved with the Save default and Save... options in the mne_analyze alignment dialog are used because then the $SUBJECTS_DIR/$SUBJECT directory will be composed of files which are dependent on the subjects’s anatomy only, not on the MEG/EEG data to be analyzed.
Each iteration step of the Iterative Closest Point (ICP) algorithm consists of two matching procedures:
These two steps are iterated the designated number of times. If the Try to keep nasion in place option is on, the present location of the nasion receives a strong weight in the second part of each iteration step so that nasion movements are discouraged.
Note
One possible practical approach to coordinate frame alignment is discussed in MEG-MRI coordinate system alignment.
The newest version of FreeSurfer contains a script called mkheadsurf which
can be used for coordinate alignment purposes. For more information,
try mkheadsurf --help
. This script produces a file
called surf/lh.smseghead
, which can be converted into
a fif file using mne_surf2bem.
Suggested usage:
mkheadsurf -subjid
<subject> .$SUBJECTS_DIR/
<subject> /bem
.mne_surf2bem --surf ../surf/lh.smseghead --id 4 --check --fif
<subject> -head-dense.fif
-head-sparse.fif
-head-dense.fif
to <subject> -head.fif
After this you can switch between the dense and smooth head
surface tessellations by copying either <subject> -head-dense.fif
or <subject> -head-sparse.fif
to <subject> -head.fif
.
If you have Matlab software available on your system, you
can also benefit from the script mne_make_scalp_surfaces .
This script invokes mkheadsurf and
subsequently decimates it using the mne_reduce_surface function
in the MNE Matlab toolbox, which in turn invokes the reducepatch
Matlab function. As a result, the $SUBJECTS_DIR/$SUBJECT/bem directory
will contain ‘dense’, ‘medium’,
and ‘sparse’ scalp surface tessellations. The
dense tessellation contains the output of mkheadsurf while
the medium and sparse tessellations comprise 30,000 and 2,500 triangles,
respectively. You can then make a symbolic link of one of these
to <subject> -head.fif
.
The medium grade tessellation is an excellent compromize between
geometric accuracy and speed in the coordinate system alignment.
Note
While the dense head surface tessellation may help in coordinate frame alignment, it will slow down the operation of the viewer window considerably. Furthermore, it cannot be used in forward modelling due to the huge number of triangles. For the BEM, the dense tessellation does not provide much benefit because the potential distributions are quite smooth and widespread on the scalp.
If you have identified the three fiducial points in software outside mne_analyze , it is possible to display this information on the head surface visualization. To do this, you need to copy the file containing the fiducial location information in MRI (surface RAS) coordinates to $SUBJECTS_DIR/$SUBJECT/bem/$SUBJECT-fiducials.fif. There a three supported ways to create this file:
The newest versions of Neuromag software allow continuous acquisition of signals from the HPI coils. On the basis of these data the relative position of the dewar and the head can be computed a few times per second. The resulting location data, expressed in the form of unit quaternions (see http://en.wikipedia.org/wiki/Quaternion) and a translation.
The continuous HPI data can be through the File/View continuous HPI data... menu item, which pops up
a standard file selection dialog. If the file specified ends with .fif
a
fif file containing the continuous coordinate transformation information
is expected. Otherwise, a text log file is read. Both files are
produced by the Neuromag maxfilter software.
Once the data have been successfully loaded, the dialog shown in Continuous HPI data overview. appears. It contains the following information:
The overview items are:
GOF
Geometric mean of the goodness of fit values of the HPI coils at this time point.
Origin movement
The distance between the head coordinate origins at the first and current time points.
Angular velocity
Estimated current angular velocity of the head.
Coil movements
Comparison of the sensor locations between the first and current time points. The minimum, maximum, average, and median sensor movements are listed.
The graphical display contains the following data:
The slider below the display can be used to select the time point. If you click on the slider, the current time can be adjusted with the arrow keys. The current head position with respect to the sensor array is show in the viewer window if it is visible, see The viewer. Note that a complete set of items listed above is only available if a data file has been previously loaded, see Loading data.
Selecting Show MRI viewer... from the View menu starts the FreeSurfer MRI viewer program tkmedit to work in conjunction with mne_analyze . After a few moments, both tkmedit with the current subject’s T1 MRI data shown and the MRI viewer control window shown in The MRI viewer control window. appear. Note that the tkmedit user interface is initially hidden. The surfaces of a subject must be loaded before starting the MRI viewer.
The MRI viewer control window contains the following items:
Show MRI viewer user interface
If this item is checked, the tkmedit user interface window will be show.
Track surface location in MRI
With this item checked, the cursor in the MRI data window follows the current (clicked) location in surface display or viewer. Note that for the viewer window the surface location will inquired from the surface closest to the viewer. The MEG helmet surface will not be considered. For example, if you click at an EEG electrode location with the scalp surface displayed, the location of that electrode on the scalp will be shown. The cortical surface locations are inquired from the white matter surface.
Show dipole locations in MRI
If this option is selected, whenever a dipole is displayed in the surface view using the dipole list dialog discussed in The dipole list the cursor will also move to the same location in the MRI data window.
Show digitizer data in MRI
If digitizer data are loaded, this option shows the locations with green diamonds in the MRI data.
Interpolate voxels
Toggles trilinear interpolation in the MRI data on and off.
Max. intensity projection
Shows a maximum-intensity projection of the MRI data. This is useful in conjunction with the Show digitizer data in MRI option to evaluate the MEG/MRI coordinate alignment
Recenter MRI display
Brings the cursor to the center of the MRI data.
Show surface data in MRI
This button creates an MRI data set containing the surface data displayed and overlays in with the MRI slices shown in the MRI viewer.
Show segmentation data in MRI
If available, the standard automatically generated segmentation volume (mri/aparc+aseg) is overlaid on the MRI using the standard FreeSurfer color lookup table ($FREESURFER_HOME/FreeSurferColorLUT.txt). As a result, the name of the brain structure or region of corex at the current location of the cursor will be reported if the tkmedit user interface is visible. After the segmentation is loaded this button toggles the display of the segmentation on and off.
Show command input and output
Allows sending tcl commands to tkmedit and shows the responses received. The tkmedit tcl scripting commands are discussed at https://surfer.nmr.mgh.harvard.edu/fswiki/TkMeditGuide/TkMeditReference/TkMeditScripting.
The FreeSurfer software includes an average subject (fsaverage) with a cortical surface reconstruction. In some cases, the average subject can be used as a surrogate if the MRIs of a subject are not available.
The MNE software comes with additional files which facilitate the use of the average subject in conjunction with mne_analyze . These files are located in the directory $MNE_ROOT/mne/setup/mne_analyze/fsaverage:
fsaverage_head.fif
The approximate head surface triangulation for fsaverage.
fsaverage_inner_skull-bem.fif
The approximate inner skull surface for fsaverage.
fsaverage-fiducials.fif
The locations of the fiducial points (LPA, RPA, and nasion) in MRI coordinates, see Using fiducial points identified by other software.
fsaverage-trans.fif
Contains a default MEG-MRI coordinate transformation suitable for fsaverage. For details of using the default transformation, see Loading data.
The following graphics displays are compatible with the Elekta-Neuromag report composer cliplab :
The graphics can be dragged and dropped from these windows to one of the cliplab view areas using the middle mouse button. Because the topographical display area has another function (bed channel selection) tied to the middle mouse button, the graphics is transferred by doing a middle mouse button drag and drop from the label showing the current time underneath the display area itself.
Note
The cliplab drag-and-drop functionality requires that you have the proprietary Elekta-Neuromag analysis software installed. mne_analyze is compatible with cliplab versions 1.2.13 and later.
When mne_analyze is invoked
with the --visualizehpi
option, a simplified user interface shown
in Snapshot of mne_analyze in the head position visualization mode. is displayed. This interface consists only
of the viewer window. This head position visualization mode
can be used with existing data files but is most useful for showing
immediate feedback of the head position during experiments with
an Elekta-Neuromag MEG system.
As described in mne_analyze, the head position visualization mode can be customized with the –dig, –hpi, –scalehead, and –rthelmet options. For this mode to be useful, the –dig and –hpi options are mandatory. If existing saved data are viewed, both of these can point to a average or raw data file. For on-line operation with the Elekta-Neuromag systems, the following files in should be used:
--dig /neuro/dacq/meas_info/isotrak --hpi /neuro/dacq/meas_info/hpi_result
Note
Since MNE software runs only on LINUX and Mac OS X platforms, one usually needs to NFS mount the volume containing /neuro directory to another system and access these files remotely. However, Neuromag has indicated that future versions of their acquisition software will run on the LINUX platform as well and the complication of remote operation can then be avoided.
When mne_analyze starts in the head position visualization mode and the –dig and –hpi options have been specified, the following sequence operations takes place:
--scalehead
option is invoked, the average head surface
is scaled to the approximate size of the subject’s head
by fitting a sphere to the digitizer and to the head surface points
lying above the plane of the fiducial landmarks, respectively. The
standard head surface is then scaled by the ration of the radiuses
of these two best-fitting spheres. Without –scalehead, the standard
head surface is used as is without scaling.If the --rthelmet
option was present, the room-temperature
helmet surface is shown instead of the MEG sensor surface. The digitizer
and HPI data files are reloaded and the above steps 1. - 4. are
repeated when the Reload HPI button
is pressed. The comment lines in the viewer window show information
about the digitizer and HPI data files as well as the location of the
MEG device coordinate origin in the MEG head coordinate system.
Note
The appearance of the viewer visualization can be customized using the Options... button, see Viewer options. Since only the scalp and MEG device surfaces are loaded, only a limited number of options is active. The display can also be saved as an image from the img button, see Producing output files.


Group and isolate cluster resources
Estimated reading time: 4 minutesThese are the docs for UCP version 3.1.12
To select a different version, use the selector below.
Docker EE enables access control to cluster resources by grouping resources into resource sets. Combine resource sets with grants to give users permission to access specific cluster resources.
A resource set can be:
- A Kubernetes namespace for Kubernetes workloads.
- A UCP collection for Swarm workloads.
Kubernetes namespaces
A namespace allows you to group resources like Pods, Deployments, Services, or any other Kubernetes-specific resources. You can then enforce RBAC policies and resource quotas for the namespace.
Each Kubernetes resources can only be in one namespace, and namespaces cannot be nested inside one another.
Learn more about Kubernetes namespaces.
Swarm collections
A Swarm collection is a directory of cluster resources like nodes, services, volumes, or other Swarm-specific resources.
Each Swarm resource can only be in one collection at a time, but collections can be nested inside one another, to create hierarchies.
Nested collections
You can nest collections inside one another. If a user is granted permissions
for one collection, they’ll have permissions for its child collections,
pretty much like a directory structure. As of UCP 3.1
, the ability to create a nested
collection of more than 2 layers deep within the root /Swarm/
collection has been deprecated.
The following image provides two examples of nested collections with the recommended maximum of two nesting layers. The first example illustrates an environment-oriented collection, and the second example illustrates an application-oriented collection.
For a child collection, or for a user who belongs to more than one team, the system concatenates permissions from multiple roles into an “effective role” for the user, which specifies the operations that are allowed against the target.
Built-in collections
Docker EE provides a number of built-in collections.
| Default collection | Description |
|---|---|
/ |
Path to all resources in the Swarm cluster. Resources not in a collection are put here. |
/System |
Path to UCP managers, DTR nodes, and UCP/DTR system services. By default, only admins have access, but this is configurable. |
/Shared |
Default path to all worker nodes for scheduling. In Docker EE Standard, all worker nodes are located here. In Docker EE Advanced, worker nodes can be moved and isolated. |
/Shared/Private/ |
Path to a user’s private collection. Note that private collections are not created until the user logs in for the first time. |
/Shared/Legacy |
Path to the access control labels of legacy versions (UCP 2.1 and lower). |
Default collections
Each user has a default collection which can be changed in UCP preferences.
Users can’t deploy a resource without a collection. When a user deploys a resource without an access label, Docker EE automatically places the resource in the user’s default collection. Learn how to add labels to nodes.
With Docker Compose, the system applies default collection labels across all
resources in the stack unless com.docker.ucp.access.label
has been explicitly
set.
Default collections and collection labels
Default collections are good for users who work only on a well-defined slice of the system, as well as users who deploy stacks and don’t want to edit the contents of their compose files. A user with more versatile roles in the system, such as an administrator, might find it better to set custom labels for each resource.
Collections and labels
Resources are marked as being in a collection by using labels. Some resource types don’t have editable labels, so you can’t move them across collections.
Can edit labels: services, nodes, secrets, and configs Cannot edit labels: containers, networks, and volumes
For editable resources, you can change the com.docker.ucp.access.label
to move
resources to different collections. For example, you may need deploy resources
to a collection other than your default collection.
The system uses the additional labels, com.docker.ucp.collection.*
, to enable
efficient resource lookups. By default, nodes have the
com.docker.ucp.collection.root
, com.docker.ucp.collection.shared
, and
com.docker.ucp.collection.swarm
labels set to true
. UCP
automatically controls these labels, and you don’t need to manage them.
Collections get generic default names, but you can give them meaningful names, like “Dev”, “Test”, and “Prod”.
A stack is a group of resources identified by a label. You can place the
stack’s resources in multiple collections. Resources are placed in the user’s
default collection unless you specify an explicit com.docker.ucp.access.label
within the stack/compose file.
Where to go next
- Create and configure users and teams
- Define roles with authorized API operations
- Grant role-access to cluster resources


Munnar, the famed hill station of south India, is a romantic locale where natural beauty is everywhere to visit,
explore and to enjoy. Munnar is situated at the confluence of three mountain streams – Muthirapuzha,
Nallathanni and Kundala and the word ‘Munnar’ means three rivers in Malayalam.
Situated about 1600m above sea level, the hill station had been the summer resort of the British
Government during the colonial era. Virgin forests, savannah, rolling hills, scenic valleys, numerous streams, huge splashy waterfalls,
sprawling tea plantations and winding walkways are all part of the great holiday experience on offer for a traveler to Munnar.
Winter(December to February)
The winter months are by a wide margin the best time to visit Munnar since the climate is charming.
The base temperature amid this time drops to ten degrees Celsius and is ideal for an excursion or a cozy stay. This is additionally
an incredible time for experience aficionados who can appreciate experience exercises, for example, mountain climbing,
trekking and rappelling. Do convey woollens along as the nights can get very cold
As spring begins(March to May)
March marks the start of summer in Munnar. The climate stays charming and temperatures go between 19 degrees Celsius
and 35 degrees Celsius. Summer in Munnar is an ideal time to appreciate touring and visiting tea homes and the Tata
Tea Museum. Convey light cottons, however additionally convey an umbrella as rain is normal amid this time.
The rainy season(June to September)
This is the monsoon season in Munnar and despite the fact that numerous visitors maintain a strategic distance from Munnar
amid the rainstorm, this is an incredible time to visit Munnar of peace is what you crave for. Secured with rich green
foliage, monsoon in Munnar have their very own appeal. This is additionally an extraordinary time to appreciate limits on
inn duties and appreciate Munnar all to yourself, without swarms of visitors. Likewise do make sure to convey an umbrella
to keep away from rain.
1. Top Station
Located at a distance of approximately 40 Kilometers from Munnar, Top Station is one of the well frequented tourist
hotspots in Kerala. The place is located at an average elevation of 1800 meters above sea levels in the Western Ghats.
The tourists can experience breathtaking views of the mountains and walk among the clouds for an out-worldly experience
2. Echo Point
Home to the rare Kurunji flower, the Echo point is named after the enchanting echo phenomenon that occurs at the spot.
The spot is characterized by a picturesque lake situated beside a hillock. The Echo Point is a famous destination for
the young tourists and a great picnic spot for camping and photography.
3. Mattupettu Dam
Constructed to conserve water to generate hydroelectricity, the Mattupetty Dam is one of the famous picnic spots in Munnar.
The dam is built on the Mattupetty Lake which is home to several species of birds and animals due to the perennial supply
of water through the reservoir. One can enjoy a nice stroll by the lake or can try boating.
4.  And the mist of clouds
surrounding the area only adds to its magnificence! Situated as high as 2,400 metres above the sea-level, this spot is
a must-visit for all tourists.
5. Eravikulam (Rajamalai) National Park
The protected forest is located at an average elevation of 2000 meters above sea level and is home to several endemic
and rare species of flora, fauna, reptiles and avifauna totaling at a whopping 750 species. The Eravikulam National
Park is a home to rare and endangered species like Tiger, Leopard, Nilgiri Tahr, Gaur, Indian Muntjac and Sambar Deer,
Golden Jackal, Jungle Cat, Wild dog and Dhole
6. Kundala Lake
At a distance of about 20 km from the city centre, this lake features scintillating backdrops of lush green slopes,
complete with unmatched cherry blossoms. And, if you’re lucky, you can also spot a blanket or two of the much-coveted
Neelakurunji flowers! When here, you can enjoy boating in the conventional rowboats, modern pedal boats, as well as
the Kashmiri Shikaras!
7. Atukkad Waterfalls
Located on the way to Pallivasal amidst dense vegetation, the Atukkad Waterfalls are one of the major tourist
attractions in Munnar. The water is cold and is also known as a great trekking hotspot in Munnar. The romantic
and secluded cascades of Atukkad are visited by several tourists throughout the year.
8. Tata Tea Museum: Temple For All Tea Lovers
Established by Tata Tea many years ago, the museum exclusively showcases the origin and evolution century-old tea
plantations in Munnar. The museum essentially pays homage to the fact that Munnar houses some of the best tea estates
in the world, and is thus among the most significant places to visit in Munnar.


Tableau Editor
Workspace
Undo (Ctrl+z)
Redo (Ctrl+y)
Clear
Tools
[B]
Build Tool
Left click to select a location
Numbers or Space to create a box with a given label or change a label
Backspace to delete a label or remove a box
Arrow keys or Tab/Enter to navigate
Ctrl + left click and drag to create empty boxes
Right click and drag to remove boxes
[M]
Move Tool
Left click and drag to move boxes


[My awesome documentation]
BindingChecker
Contents
Public Functions
Public Slots
Signals
Detailed Description
BindingChecker Class
Header:
#include <BindingChecker>
Inherits:
QObject
List of all members, including inherited members
Public Functions
BindingChecker
(QObject *
parent
= nullptr)
QString
someVar
()
Public Slots
void
setSomeVar
(
QString
)
Signals
void
someVarChanged
()
Detailed Description
Member Function Documentation
BindingChecker::
BindingChecker
(
QObject
*
parent
= nullptr)
[some footer and whatnot information]


Flat White is a bespoke ceramic and porcelain tile studio based in Brooklyn.
We transform off-the-shelf tiles with textures, treatments, symbols, and patterns that can cover walls or be combined with existing configurations. Each project is a unique exploration of color, composition, shape, and experimental techniques.
Our studio is led by Violette Van Parys, a French designer trained in ancient techniques. Her tiles are hand treated with custom pigments of oxides, precious metals, and natural oils fired at over 1400ºF that fuse with existing glazes for durable products that will stand the test of time.
We work with architects, designers, artists, and home owners to develop bespoke prototypes for special projects. Our tiles are used in private and commercial properties, indoors and out.
Email us for more information and to inquire about working together.


{% extends "events/base.html" %} {% block page_title %}Privacy Policy | {{ super() }}{% endblock %} {% block page_id %}privacy{% endblock %} {% block section_type %}events legal{% endblock %} {% block content %}
Note: The Privacy Policy for the Events Platform is currently under review and comment on our governance mailing list. We will update this Privacy Policy once review and comment is completed.
May 16, 2012
Mozilla hosts a platform to promote a wide variety of events related to webmaking. We list our own events and also offer the ability for others to list events that encourage people to come together to teach, meet, learn, and share.
This top section is a summary of Mozilla’s privacy practices for the Mozilla Webmaker Events Platform (the “Events Platform”). Please be sure to read the entire document, because when you use the Events Platform to search for, host, attend events or otherwise, you are indicating you are ok with our whole privacy policy, not just this summary:
This policy describes how Mozilla handles the information we collect about you when you use the Events Platform. We have separate privacy policies for our other products and services.
For us, “personal information” is either:
If we store personal information with other information that is not personal, we treat the combination like personal information.
We consider information that does not fall within the definition of personal information to be “non-personal information”. If we remove all personal information from a set of data we have about you, we treat the remaining as non-personal information.
A cookie is a string of information that a website stores on a visitor's computer, and that the visitor's browser provides to the website each time the visitor returns to allow the website to “recognize” the browser. Clear gifs (also known as web beacons) are used in combination with cookies to help website operators understand how visitors interact with their websites. The term usually used to describe this is "web analytics" and the cookies and clear gifs are the tools by which a website owner collects this web analytics data.
Mozilla uses the information provided by cookies and clear gifs to develop a better understanding of how Mozilla's visitors use Mozilla's websites, and to facilitate those visitors' interactions with Mozilla's websites. Mozilla’s HTML formatted emails may use clear GIFs to help us determine the number of people who open our emails and click on the links within our emails.
You have the ability to accept or decline cookies. Mozilla visitors who do not wish to have cookies placed on their computers by Mozilla, its contractors, or third-party service providers should set their browsers to refuse cookies before linking to the Events Platform. The Events Platform may not function properly without the aid of cookies.
There are four general ways we get information about you:
To attend or host an event, we may ask you to register by providing information such as your first and last name, email, address and zip code. To host an event, you may give us information such as the location where your event will take place, the title and description of your event, the date, time, and length of your event, the event venue name and maximum number of attendees. You may also provide us with feedback about the event.
If you attend Mozilla events, you may be asked to consent to your photo being taken at the event. We may post these photos to promote the event. You can request that we remove a photo by contacting the organizer of that Mozilla event.
We use your information to help us provide the Events Platform to you, including to communicate with you about the event and to help us improve future events. We may also use information, such as comments or photos, to help promote the event, share the event, or inform others about the event.
When you give us personal information, we will only use it for the reasons we told you about when you gave it to us, including as described in this policy.
Mozilla is an open organization. We publicly release de-identified user information to make our products better and help foster an open web, but only in a way that we think respects the privacy of our users.
Whenever we publicly release information about our users in this way, unless we get your consent to release more, we’ll remove information that we believe can identify you and try to disclose it in a way we believe minimizes the risk of you being re-identified. For example, if we share your comments about the event, we will do so without revealing your name, unless we ask your permission to do so first.
We may post photos from Mozilla events on photo sharing and social networking sites. You can request removal of a photo by contacting the event organizer.
We may share your personal information with employees, contractors, partners and service providers, but only if they are contractually obligated to handle the data in ways that are approved by Mozilla. If our organizational structure or status changes (like if we undergo a restructuring, are acquired, or go bankrupt) we’ll pass on your information to a successor or affiliate.
We may also access, use, preserve or disclose information about you when we have a good faith belief that it is reasonably necessary to do so to protect the rights, property or safety of Mozilla, its users or the public.
Mozilla does not rent or sell your personal information to anyone.
Any feedback you provide about an event may be posted publicly.
When a government agency or someone involved in a lawsuit asks for your personal info, we'll only give it to them if we have a good faith belief that:
We follow the law whenever we receive requests like this about you and we'll notify you any time we are asked to hand over your personal info like this, unless we're legally prohibited from doing so or circumstances require otherwise.
We may also access, use, preserve or disclose information about you when we have a good faith belief that it is reasonably necessary to do so to protect the rights, property or safety of Mozilla, its users or the public.
We take steps to make sure that anyone (like an employee or contractor) we show your personal information has a good reason to see it and is only allowed to do Mozilla-approved things with it.
Despite our efforts, we can't guarantee that hackers can't break in and access your data. If we find out about a security breach, we'll try hard to let you know so that you can take appropriate protective steps. We only keep information as long as we need to do the thing we collected it for. Once we don't need it any more, we'll destroy it unless we are forced by law to keep it longer.
When you register to host an event:
When you register as either a host or an attendee, you should expect to receive some communications related to the event, such as event confirmations and reminders.
You can often choose to share an event through email, Facebook, or Twitter sharing functionalities on the event page. These functionalities are designed not to share your information directly with these companies, where possible.
Privacy laws and expectations vary from country to country. We’re a global organization and our computers are in several different places around the world. We also use service providers whose computers may also be in various countries. This means that any information we have about you might end up on one of those computers in another country, and that country may have a different level of data protection regulation than yours.
By registering to host or attend an event, you consent to the transfer of your information as described above.
If you are under 13, you must not provide us with your personal information. If you are a parent and believe that your child who is under 13 has provided us with personally identifiable information, please contact us to have your child’s information removed.
If you are 13-17, with parental permission and supervision, you may register to host or attend some events. We encourage you and your parents to read the safety tips at Event Guidelines.
Sometimes, we change our privacy policies. When we do, we’ll post a notice about the change at privacy-page and try to notify you in other appropriate ways.
If you want to make a correction to your information, or you have any questions about our privacy policies, please get in touch with:
Mozilla CorporationPhone: +1-650-903-0800
Email: joinmozilla at mozilla dot org


DIRECTED BY: Betty Thomas WRITTEN BY: Susannah Grant CAST: Sandra Bullock, Domenic West, Elizabeth Perkins, Steve Buscemi
MPAA: Rated PG-13 for mature thematic elements involving substance abuse, language and some sensuality. RUNTIME: USA:103
RATING: 4/10
"Alcohol and drugs = bad. Not alcohol and drugs = good. Got it?"
Just when you though you've seen enough of brave young women dealing with their personal problems on screen, be that insanity or alcoholism, Hollywood releases yet another one of those 'deep, emotional stories about finding yourself'..
'28 Days' is practically a visualization of the usual 'meaningful' true stories that people are so proudly retelling at AA-meetings. Gwennie (Sandra Bullock) is a young woman who drowned her problems in alcohol. For her life was a big party, with no beginning and no end. This behavior has of course estranged her from her only sister and from life itself. Her existence is filled with endless parties and comic episodes. Such as when she got drunk with boyfriend Jasper (Dominic West), borrowed her sister's (Elizabeth Perkins ) wedding limo and crashed it into someone's house. This time she had to pay with a 28 day stay in court-ordered rehab. Here she must realize that the only thing that can save her is her is redemption, willpower and commitment. Most important she must realize her place and direction in life and understand that her life is not just a big party.
The film itself feels like a rehab program, whining and moaning about things that have been said and written a million times. It is a classic cautionary tale. An echo.  A shadow of last year's 'Girl, Interrupted', which likewise followed in the footsteps of great masterpieces like 'The Cuckoo's Nest' and 'Trainspotting'. Director Betty Thomas has stuffed her film with so many failures and errors, that it is impossible to sum them all up in one review. For some paranoid reason she decided to make her film a drama/comedy. Jokes and funny characters almost deliberately delude you from the really important and complex issues: alienation, despair, terror, confusion, loneliness. And what awesome power and strength of character it actually takes to overcome all that and become clean. Isn't that what the filmmakers wanted to show in the first place? Even the transition process itself seems like a walk in the park. Betty Thomas' idea of hell is a cozy, homey place where happy alcoholics and cheerful drug addicts are not allowed to smoke, drink or watch TV after 11. It is simply too light, simplified and unnecessary sweet to be taken seriously. But the worst thing about it is that it actually thinks that it is saying something of significance. That it actually tries to educate the audience with its extremely predictable and primitive story. "All you need to do is just say no", says Dr.Cornell (Steve Buscemi) as if was the revelation of the century. And that's how simple it is! In fact I would rather watch 'Lost in Space' once again, than return to '28 Days' .
As for acting, it's acceptable, but hardly anything else. For Sandra Bullock it's an opportunity to demonstrate that she is capable of more than 'Speed'. She handles her part with a surprising professionalism and ease that certainly saves the film from being a complete flop. Dominic West shines as the source of Gwenie's devilish temptations, but Elizabeth Perkins' and Steve Buscemi's great talents are wasted on unnoticeable and shallow characters. Although intellectually 'Girl, Interrupted' was a greater achievement, '28 Days' is superior in its visual aspect. There are some nice flash back sequences and occasionally impressive pacing, but the overall technical aspect of this film is on the ground floor. The most important thing is that we've seen it before and it was a lot better. 'Clean and Sober', 'Only When I Laugh', 'When A Man Loves A Woman' , 'Leaving Las Vegas' and many other stronger films were made about the same issues. So what's the point? In other words '28 Days' doesn't contribute to the moviemaking business on any level.  Under all other circumstances stay away, because this film equals $8 and 103 minutes lost.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


ScriptUI Builder
SuiBuilder
API provides its own way of building a user interface based on the Adobe ScriptUI. It features:
- a prepared set of the Adobe ScriptUI components
- extensibility via custom components
- built-in validators
- well readable and maintainable fluent interface API design
Including into application
Brixy framework offers a prepared script that includes SuiBuilder
module and loads a set of base ScriptUI components and helpful debug methods.
Including in Brixy MVC application:
BX.use('brixy', 'includes/suiBuilderPack.jsxinc');
Including in application not based on Brixy MVC application framework:
// required core Brixy library
#include 'path/to/Brixy/includes/Brixy.jsxinc'
// SuiBuilder library
#include 'path/to/Brixy/includes/suiBuilderPack.jsxinc'
First dialog window
Load module:
var SuiBuilder = BX.module.Me('brixy.ui.SuiBuilder');
Create SuiBuilder
instance:
var b = new SuiBuilder();
For each dialog window we need one SuiBuilder
instance. First of all we should create the window itself. The window()
factory method creates new ScriptUI Window
component:
b.window('dialog', 'Hello World');
Now we can add window's components by calling their factory methods. Create SuiBuilder row
component. It is wrapper to the ScriptUI group
component with orientation 'row'
. SuiBuilder always places new components inside the last created container component. So row
is appended inside the window.
b.row();
Now we will add SuiBuilder staticText
component as wrapper to the ScriptUI statictext
component. Because the row
is recently created container component, new staticText
component is appended as its child component.
b.staticText('Hello World!');
Add SuiBuilder button
component as wrapper to the ScriptUI button
. Button is also added as child of the row
component. Note that previous staticText
is not container component.
b.button('OK');
And finally show the window:
b.showWindow();
Complete script:
var b = new SuiBuilder();
b.window('dialog', 'Hello World')
.row()
.staticText('Hello World!')
.button('OK')
.showWindow();
Note the use of the fluent interface API design that allows you to chain method calls. It is clear and well readable code.
Edited: 2017/01/20


--- layout: post title: It’s Schema Free – Why NoSQL Continues to Gain Adoption date: '2012-02-08T14:44:36-08:00' tags: tumblr_url: http://alexhwilliams.tumblr.com/post/17284104434/its-schema-free-why-nosql-continues-to-gain-adoption ---
http://bit.ly/AdnITU


Provenance is defined as a record that describes the people,
institutions, entities, and activities involved in producing,
influencing, or delivering a piece of data or a thing.
In particular, the provenance of information is crucial in deciding
whether information is to be trusted, how it should be integrated with
other diverse information sources, and how to give credit to its
originators when reusing it. In an open and inclusive environment
such as the Web, where users find information that is often contradictory or
questionable, provenance can help those users to make trust judgements.
The PROV Family of Specifications is a set of specifications defined by the W3C PROV Working Group defining various aspects that are necessary to achieve the vision of inter-operable interchange of provenance information in heterogeneous environments such as the Web. The specifications are:
- PROV-OVERVIEW, an overview of the family of PROV specifications;
- PROV-PRIMER, a primer for the PROV data model;
- PROV-DM, the PROV data model for provenance;
- PROV-CONSTRAINTS, a set of constraints applying to the PROV data model;
- PROV-N, a notation for provenance aimed at human consumption;
- PROV-O, the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF;
- PROV-AQ, the mechanisms for accessing and querying provenance;
- PROV-XML, an XML schema for the PROV data model;
- PROV-LINKS, a mechanism for linking entities across bundles;
- PROV-DICTIONARY, tackling the provenance of dictionaries.
ProvValidator, ProvTranslator and ProvExpander services use ProvToolbox a Java toolkit to create, save, and read PROV expressions.
- ProvTranslator reads the PROV representation submitted by the user, builds an in memory representation using Java objects and then saves it to the requested represententation. Conversion from any PROV representation to Java objects is performed by the ProvToolbox; likewise, conversion from Java objects to other representations is also performed by the Prov Toolbox.
- ProvValidator performs a series of test to check validity of an in-memory PROV representation. It returns a validation report listing issues identified by the validator.
- ProvExpander expands a provenance template using a series of bindings; it returns a PROV document.
ProvValidator and ProvTranslator can be used either interactivity from a web browser, or as REST services, according to the following API.


Utilities (bpy.utils)¶
This module contains utility functions specific to blender but not associated with blenders internal data.
-
bpy.utils.
blend_paths
(absolute=False, packed=False, local=False)¶ Returns a list of paths to external files referenced by the loaded .blend file.
Parameters: - absolute (boolean) – When true the paths returned are made absolute.
- packed (boolean) – When true skip file paths for packed data.
- local (boolean) – When true skip linked library paths.
Returns: path list.
Return type: list of strings
-
bpy.utils.
escape_identifier
(string)¶ Simple string escaping function used for animation paths.
Parameters: string (string) – text Returns: The escaped string. Return type: string
-
bpy.utils.
register_class
(cls)¶ Register a subclass of a blender type in (
bpy.types.Panel
,bpy.types.UIList
,bpy.types.Menu
,bpy.types.Header
,bpy.types.Operator
,bpy.types.KeyingSetInfo
,bpy.types.RenderEngine
).If the class has a register class method it will be called before registration.
Note
ValueError
exception is raised if the class is not a subclass of a registerable blender class.
-
bpy.utils.
resource_path
(type, major=bpy.app.version[0], minor=bpy.app.version[1])¶ Return the base path for storing system files.
Parameters: - type (string) – string in [‘USER’, ‘LOCAL’, ‘SYSTEM’].
- major (int) – major version, defaults to current.
- minor (string) – minor version, defaults to current.
Returns: the resource path (not necessarily existing).
Return type: string
-
bpy.utils.
unregister_class
(cls)¶ Unload the Python class from blender.
If the class has an unregister class method it will be called before unregistering.
-
bpy.utils.
keyconfig_init
()¶
-
bpy.utils.
keyconfig_set
(filepath, report=None)¶
-
bpy.utils.
load_scripts
(reload_scripts=False, refresh_scripts=False)¶ Load scripts and run each modules register function.
Parameters: - reload_scripts (bool) – Causes all scripts to have their unregister method called before loading.
- refresh_scripts (bool) – only load scripts which are not already loaded as modules.
-
bpy.utils.
modules_from_path
(path, loaded_modules)¶ Load all modules in a path and return them as a list.
Parameters: - path (string) – this path is scanned for scripts and packages.
- loaded_modules (set) – already loaded module names, files matching these names will be ignored.
Returns: all loaded modules.
Return type: list
-
bpy.utils.
preset_find
(name, preset_path, display_name=False, ext='.py')¶
-
bpy.utils.
preset_paths
(subdir)¶ Returns a list of paths for a specific preset.
Parameters: subdir (string) – preset subdirectory (must not be an absolute path). Returns: script paths. Return type: list
-
bpy.utils.
refresh_script_paths
()¶ Run this after creating new script paths to update sys.path
-
bpy.utils.
app_template_paths
(subdir=None)¶ Returns valid application template paths.
Parameters: subdir (string) – Optional subdir. Returns: app template paths. Return type: generator
-
bpy.utils.
register_manual_map
(manual_hook)¶
-
bpy.utils.
unregister_manual_map
(manual_hook)¶
-
bpy.utils.
register_classes_factory
(classes)¶ Utility function to create register and unregister functions which simply registers and unregisters a sequence of classes.
-
bpy.utils.
register_submodule_factory
(module_name, submodule_names)¶ Utility function to create register and unregister functions which simply load submodules, calling their register & unregister functions.
Note
Modules are registered in the order given, unregistered in reverse order.
Parameters: - module_name (string) – The module name, typically
__name__
. - submodule_names (list of strings) – List of submodule names to load and unload.
Returns: register and unregister functions.
Return type: tuple pair of functions
- module_name (string) – The module name, typically
-
bpy.utils.
register_tool
(tool_cls, *, after=None, separator=False, group=False)¶ Register a tool in the toolbar.
Parameters: - tool (
bpy.types.WorkSpaceTool
subclass.) – A tool subclass. - space_type (string) – Space type identifier.
- after (collection of strings or None.) – Optional identifiers this tool will be added after.
- separator (bool) – When true, add a separator before this tool.
- group (bool) – When true, add a new nested group of tools.
- tool (
-
bpy.utils.
make_rna_paths
(struct_name, prop_name, enum_name)¶ Create RNA “paths” from given names.
Parameters: - struct_name (string) – Name of a RNA struct (like e.g. “Scene”).
- prop_name (string) – Name of a RNA struct’s property.
- enum_name (string) – Name of a RNA enum identifier.
Returns: A triple of three “RNA paths” (most_complete_path, “struct.prop”, “struct.prop:’enum’”). If no enum_name is given, the third element will always be void.
Return type: tuple of strings
-
bpy.utils.
manual_map
()¶
-
bpy.utils.
script_path_user
()¶ returns the env var and falls back to home dir or None
-
bpy.utils.
script_path_pref
()¶ returns the user preference or None
-
bpy.utils.
script_paths
(subdir=None, user_pref=True, check_all=False, use_user=True)¶ Returns a list of valid script paths.
Parameters: - subdir (string) – Optional subdir.
- user_pref (bool) – Include the user preference script path.
- check_all (bool) – Include local, user and system paths rather just the paths blender uses.
Returns: script paths.
Return type: list
-
bpy.utils.
smpte_from_frame
(frame, fps=None, fps_base=None)¶ Returns an SMPTE formatted string from the frame:
HH:MM:SS:FF
.If fps and fps_base are not given the current scene is used.
Parameters: frame (int or float.) – frame number. Returns: the frame string. Return type: string
-
bpy.utils.
smpte_from_seconds
(time, fps=None, fps_base=None)¶ Returns an SMPTE formatted string from the time:
HH:MM:SS:FF
.If fps and fps_base are not given the current scene is used.
Parameters: time (int, float or datetime.timedelta
.) – time in seconds.Returns: the frame string. Return type: string
-
bpy.utils.
unregister_tool
(tool_cls)¶
-
bpy.utils.
user_resource
(resource_type, path='', create=False)¶ Return a user resource path (normally from the users home directory).
Parameters: - type (string) – Resource type in [‘DATAFILES’, ‘CONFIG’, ‘SCRIPTS’, ‘AUTOSAVE’].
- subdir (string) – Optional subdirectory.
- create (boolean) – Treat the path as a directory and create it if its not existing.
Returns: a path.
Return type: string
-
bpy.utils.
execfile
(filepath, mod=None)¶


{% extends "base.html" %} {% block title %} - about{% endblock %} {% block content -%}
Hello,
This site contains 29761 parsed manpages from sections 1 and 8 found in Ubuntu's manpage repository. A lot of heuristics were used to extract the arguments of each program, and there are errors here and there, especially in manpages that have a non-standard layout.
It is written in Python and uses bashlex, a bit of NLTK (to find the interesting parts of the manpage), a little d3.js (for the connecting lines graphic) and Flask. It is served with uwsgi and nginx. Source code is available on github.
My name is Idan Kamara and you can contact me at idan at explainshell dot com for any questions or suggestions.


| parse_quosure {rlang} | R Documentation |
These functions were deprecated and renamed to parse_quo()
and parse_quos()
in rlang 0.2.0. This is for consistency with the
convention that suffixes indicating return types are not
abbreviated.
parse_quosure(x, env = caller_env()) parse_quosures(x, env = caller_env())
x |
Text containing expressions to parse_expr for
|
env |
The environment for the quosures. The global environment (the default) may be the right choice when you are parsing external user inputs. You might also want to evaluate the R code in an isolated context (perhaps a child of the global environment or of the base environment). |


{{ partial "nav.html" . }}
A Comedic Biographical Serious Podcast
{{ partial "episode.html" . }} {{ partial "footer.html" . }}


A RoboFont extension to display similarly-shaped glyphs to the left & right of the glyph being edited.
Once installed, RamsayStreet will become available from the Extensions menu.
Use the menu to open the Settings window:
.ramsaySt
file.Neighbours, Everybody needs good neighbours
With a little understanding
You can find the perfect blend
Neighbours...should be there for one another
That's when good neighbours become good friends
Ooh Neighbours, should be there for one another
That's when good neighbours become good friends.


Log identification and authentication events.
This functionality should be implemented by the centralized log server solution. Follow the vendor's instructions to configure the centralized log server to log identification and authentication events.