Derived results and workspaces¶

Use these guides to preserve source data, update derived results, reuse operations, and manage workspaces.

Keeping source data during a transformation¶

Use a managed child result when an ImageTool transformation must preserve the source data and record how the result was made.

Open the source data in ImageTool Manager.
Open the required transformation from the ImageTool Edit menu.
Enter the transformation parameters.
Set Result Placement to Open Child Window.
Open the result and inspect it before continuing the analysis.

The Manager places the result below its source and records the operation. Use Copy Code in the dialog or Copy Full Code in the Manager to reproduce it in Python.

Use Replace Current only when replacing the current ImageTool is intended. See Data operations for the available operations and Result placement for all placement states.

Repeating an analysis after an input change¶

When a source row changes, select its derived row and check the state badge:

Stale means the recorded operation can be repeated with the current source.
Unavailable means the current source no longer satisfies the recorded selection or operation.
Auto means automatic updates are enabled and the row is current.

Click the badge or the update banner in the tool window. Choose Update Now to repeat the operation once. To change future behavior, enable or disable automatic updates and choose Save. Saving the preference does not update the current result.

For ftool, goldtool, or restool, enable Refit after update only when the same fit model and settings remain valid for the changed input. Inspect the repeated fit before using its parameters.

Updating a result with several inputs¶

For a concatenation or console expression made from several ImageTools:

Confirm whether the badge is Changed or Missing.
Restore any missing live input or confirm that its recorded source file is available.
Choose Reload Data.
Inspect the recomputed result and its input list.

If a recorded file moved, edit the file-load step and enable Also relink selected file loads to update related inputs together. Only replay console expressions from workspaces you trust.

Use Applying recorded operations to other data when the recorded steps must be applied to a different open dataset.

Applying recorded operations to other data¶

Select the derived ImageTool row whose operation sequence must be reused.
In the side panel, inspect the recorded inputs and steps.
Right-click the step list and copy the required steps.
Select the target ImageTool row.
Choose Paste and inspect the generated result.

Use Reorder Steps… before copying when the recorded order must change. A step can be reused only when the target data contains compatible dimensions, coordinates, and metadata.

To continue in Python, copy the selected steps or choose Copy Full Code. Inspect file paths, variable names, and operation parameters before running the code. Code for data loaded from files includes the load operation. Code for watched data uses the watched variable name.

Saving and reopening a workspace¶

In Manager or any managed child window, press Ctrl+S.
Choose a .itws path and save the workspace.
Confirm the active path with File ‣ Workspace Properties.

The workspace stores managed windows, their state, row notes, derived relationships, and Figure Composer recipes. Row notes remain workspace metadata and do not modify the underlying DataArray attributes.

Important

Keep the original measurement files and record the software environment separately. A workspace restores the Manager session. It does not reproduce a notebook kernel or install the packages used by the analysis.

To reopen the session, choose File ‣ Open Workspace…, press Ctrl+O, or drag the .itws file into Manager. Inspect the restored windows and derived rows before continuing work.

Use File ‣ Add Windows From Workspace… when selected windows from another workspace must be added without replacing the current session.

Watched notebook rows reopen disconnected. Recreate their variables and follow Reconnecting variables after restarting to reconnect them.

Reviewing stored workspace code¶

Use this procedure when Manager shows the warning that stored executable content is paused.

Confirm who created the .itws file and how you received it.
Select Review and Trust… in the warning banner. You can also open File ‣ Workspace Properties and select Review and Trust… there.
Inspect every item in the review details. The approval applies to the complete workspace code listing, not only to the operation that was blocked.
If a serialized fitting payload shows only a digest and you cannot verify its source, cancel the review.
If you accept all listed content, select Trust Workspace and Run Code.
Repeat the blocked action, such as Reload Data or a Figure Composer render.

If you cancel, data and other non-executable workspace state remain available. Manager keeps stored code paused.

After a successful save, an unchanged approved workspace normally opens without another review on the same computer. If its executable content no longer matches the stored approval, review the workspace again.

Stored code lists the content that Manager can keep paused. Use the Security settings only for a controlled analysis folder.

Reducing Manager memory use¶

Save the current Manager session as a workspace.
Select the ImageTool rows whose data can be read from the workspace on demand.
Choose Offload to Workspace.
Confirm that the rows show the Dask badge and that their ImageTools still display the required slices.

Offloaded data uses less memory but responds more slowly because slices are read from the workspace file. Keep the workspace file available at its saved path.

To restore selected data to memory, use Dask ‣ Load Into Memory in ImageTool.