Saving, loading and exporting — TRT Analysis user manual

Saving, loading and exporting


An interpretation is saved with the project rather than on its own. A single .ghe file carries the measured data, every phase boundary, every slider position and both sets of results, together with the work of the other modules on the same project. Reopening it restores the analysis exactly as it was left.

Creating a new project - Select to start a fresh interpretation. All inputs revert to their defaults and any loaded test data is cleared. Because the project is common to the suite, New clears the three modules and not the TRT panels alone. If it has unsaved changes you are asked to save first, and cancelling leaves everything as it was.

Saving a project - Select to write the project to its current location, or Save As to choose a new name or folder. The file dialog filters for Analysis Suite project (*.ghe). Save writes the whole project whichever module is active, so an interpretation is saved from the TRT panels and from those of the other modules alike. If no file has been assigned yet, Save behaves like Save As. The last folder used is remembered across sessions.

Opening a project - Select Open to browse for a .ghe project. Every input, every phase boundary and both sets of results come back as they were saved, and the charts and the console are refreshed with them. Projects written by earlier releases still open, including the .trt files of TRT Analysis 1.x; saving one writes it back in the current format. Opening a project activates the GHE module, even a project carrying nothing but a test: switch back to TRT with the module button of the toolbar to see the interpretation.

The .ghe project file - The .ghe extension is associated with the Analysis Suite application icon on Windows, so double-clicking a project file in Explorer opens it directly. A .ghe file is a compact binary archive (CBOR-encoded JSON) carrying the full project state.

It is also self-contained: the measured data is embedded in it, so the original .csv files are not needed to reopen, review or revise the interpretation, and the project can be sent to a colleague or archived on its own. Because the three modules share the file, a project opened and saved from one of them keeps what the others hold.

Exporting - As elsewhere in the Analysis Suite, the results can be taken out as CSV. In this module the export is automatic: two files are written alongside the project every time it is saved, one per interpretation method. Both are comma-delimited, both open in any spreadsheet, and both are overwritten at each save. Nothing is written when no test data is loaded, since there would be no result to report. A save also writes the result files of the other modules, named on the same project, so expect more than these two in the folder.

File Content
{project}_FOA.csv First-order approximation results, as displayed on the console's FOA page, reported separately for the heating and the recovery phase.
{project}_ShortTerm.csv Short-term g-function results — the calibrated parameters as left by the sliders, and the quality of the fit they produce.

Each file opens with a short header explaining every quantity it carries, then the results themselves, then the interpretation context: the settings and the geometry the numbers were produced with. That last block is what makes a result reproducible, since neither λs nor Rb* can be replayed without the regression window and the inputs that fed it.

First-order approximation results - The file carries one row per quantity and two value columns, one for the heating phase and one for the recovery phase.

Quantity Unit Description
Results
lambda_s W/m·K Ground thermal conductivity, from the regression slope
Rb* m·K/W Effective borehole resistance, from the heating-phase intercept. A dash in the recovery column: that regression carries no borehole-resistance term
q W/m Mean heat injection rate per unit borehole length used by the phase
tcr h Critical time 5rb²/αs, before which the line source does not apply
Residual mean °C Average of the regression residuals over the fitted window.
Residual sd °C Sample standard deviation of the residuals
RMSE °C Root mean square of the residuals
Interpretation context
Averaging method Arithmetic mean or p-linear average of the inlet and outlet temperatures
Cs MJ/m³·K Ground volumetric heat capacity, which sets tcr
Tg °C Undisturbed ground temperature used by the regression
H, rb m Active length and radius of the test borehole
Sampling period dt s Time between two measurements
Injection duration h Length of the heating phase, which the recovery regression relaxes from
Regression windows First and last sample fitted, for each phase

Short-term g-function results - The file carries one row per quantity and a single value column, holding the position of each slider at the moment of the save.

Quantity Unit Description
Calibrated parameters
lambda_s, Cs W/m·K, MJ/m³·K Ground thermal conductivity and volumetric heat capacity
lambda_g, Cg W/m·K, MJ/m³·K Grout thermal conductivity and volumetric heat capacity
alpha_s, alpha_g m²/s Thermal diffusivities λ/C the two pairs above imply
s m Shank spacing, centre to centre between the two pipes
Tg °C Undisturbed ground temperature fed to the short-term g-function
Quality of the fit
Residual mean °C Mean of the residuals over the whole test. Nothing forces it to zero here, so a departure from it is a bias rather than scatter
Residual sd °C Sample standard deviation of those residuals
RMSE °C Root mean square of those residuals, the figure to minimise while calibrating
Interpretation context
Excitation function How the temperature difference across the borehole was obtained
Cf MJ/m³·K Fluid volumetric heat capacity
Mean flow rate L/min Averaged over the injection phase, the value handed to the short-term g-function
H, rb, ri, ro m Borehole and pipe geometry read by the short-term g-function
kp W/m·K Pipe thermal conductivity

A dash in place of a value means the corresponding result did not converge, or does not apply. If a file cannot be written — most often because it is still open in a spreadsheet — the console reports it and the .ghe project itself is left untouched.