An analysis template is a saved Pool configuration — the complete chain of
Source, Filters, Analyses, Statistic and Destination nodes with all of their settings —
stored without any reference to the measurement files it was built from. Templates are saved with
the extension .vppj.
The point of a template is repeatability. Once you have set up an analysis exactly the way a test
procedure requires — the right FFT size, the right window, the right averaging, the right
weighting, the right export destination — save it as a template. Every subsequent
measurement can then be evaluated by loading the template and dropping the new file onto it,
guaranteeing that all results were produced with identical settings.
What a Template Contains
Stored in a template
Not stored in a template
Every Pool node, in every stage, with its kind, display name and enabled state
Source file paths — the single source file and the multi-file batch list
The complete parameter set of each node (FFT size, window, overlap, averaging, weighting,
frequency and order ranges, and so on)
Any file path stored inside a node, such as an
export destination or a referenced result file
Which Destination node drives the pipeline display
Window and panel layout, open
document tabs, chart zoom, axis ranges, cursors and colour maps
The visibility state of the Properties panel
Computed results and cached data
— a template holds no measurement values at all
Templates are small text files. They contain only settings, so they can be circulated by e-mail,
kept under version control, or stored next to a written test procedure without carrying any
measurement data with them.
Saving the Current Analysis as a Template
Build and verify the analysis in the Pool. Run it at least once so you know the settings
produce the results you expect.
Select File → Save as Template….
Choose a folder and file name. The suggested name is AnalysisTemplate.vppj —
replace it with something descriptive, e.g. Gearbox_RunUp_OrderAnalysis.vppj.
Click Save. The event log confirms
Saved as analysis template: <path>.
The Pool you are working in is not affected in any way — saving a template is purely an
export of the current configuration.
Templates are saved wherever you choose; there is no reserved template folder. A practical
convention is to keep a Templates folder alongside your measurement campaign so that
the procedure travels with the data.
Creating a New Session from a Template
Select File → New from Template….
Pick the .vppj file.
If the current session already contains a Pool, loaded source files or open document tabs, a
confirmation appears. Choose:
Yes — save the current project first, then load the template.
No — discard the current session and load the template.
Cancel — do nothing.
The workspace is rebuilt with the template's Pool configuration and no data loaded.
Drag your measurement file onto the Source stage and run the pipeline.
Loading a template starts a completely fresh workspace. All Data Viewer and Mark Analyzer sessions
and all workspace tabs are closed, and the Pool undo history is cleared. Save anything you still
need before you load a template.
A template path can also be passed to Deepsona on the command line, which is convenient for a
desktop shortcut that always opens the same standard analysis:
File → Open Project… / Save Project… /
Save Project As…
File → New from Template… / Save as Template…
Extension
.json
.vppj
Pool configuration
stored
stored
Source file paths
stored
removed
Appears in File → Recent
yes
no
Typical use
Resume work on one specific measurement.
Apply a standard
evaluation to any measurement.
In short: a template is a project with the file paths taken out. Use a project
when you want to come back to a particular data set; use a template when you want to reuse a method.
Recent Projects
File → Recent lists the last projects you saved or opened, most recent first,
up to ten entries. Click an entry to reopen that project. Templates are deliberately kept out of
this list, because a template is a starting point rather than a document you return to.
Typical Workflow: Standardising a Test Procedure
Load one representative measurement and build the Pool: Source, any filters, the analyses the
procedure calls for, a Statistic stage if required, and Destination nodes for the exports you want.
Run the pipeline and check every result carefully. A mistake saved into a template is repeated
on every future measurement.
Select File → Save as Template… and save as, for example,
EndOfLine_NVH_v1.vppj. Keep the version number in the file name.
Distribute the file to everyone who runs the procedure.
For each new measurement: File → New from Template…, choose the
template, drop the measurement file onto the Source stage, and run.
Save the outcome with File → Save Project… so that the specific
measurement, together with its settings, can be reopened later.
Notes and Limitations
Deepsona ships without built-in templates and there is no template browser — templates are
chosen through a normal file dialog. Organise them in folders that match your test procedures.
The .vppj extension is not registered with Windows Explorer, so double-clicking a
template does not start Deepsona. Use File → New from Template…, or
create a shortcut that passes the path on the command line.
Templates are not validated on load. If you point New from Template… at
an ordinary project file, it is accepted — and it brings its file paths with it. Keep
templates and projects in separate folders.
There is no auto-save for projects or templates, and no unsaved-changes prompt when you close
the application or click the toolbar New button. Save your work explicitly.
Save as Template is unrelated to the Template Editor on the
Start Menu. Save as Template stores an analysis pipeline; the Template Editor designs the layout of
generated reports.
Both template commands are unavailable while a pipeline is running. Wait for the run to finish.