Reuse and share runs

Three days later you need the quench you ran on Tuesday — to check a number, to run the same cycle on a different grade, or to send it to the colleague who asked for it. Everything you ran in a session is still there, numbered, and reachable from the conversation itself.

How runs are numbered#

Every simulation in a session reserves the next run version before it executes: run 1, run 2, run 3. Versions are never reused. If you delete run 3, the next run is still 4. Artifacts for each run live in a run-scoped folder under a session-scoped prefix, with the run version zero-padded to three digits — run 3 stores its artifacts under run_003.

A CCT sweep of five cooling rates is one run, not five. A spot welding sweep of five currents is five runs, because each was a separate execution.

List what you have#

List my runs.

Phases replies with a count and, for each run, its version, its storage prefix, the simulator it was inferred to be, its summary line, and a map of which output files are present. Filter when a session is busy:

List my CCT runs.

List my RSW runs.

By default you get the most recent 20.

Inspect one#

Inspect run 3 and show me its plots.

inspect_run returns the run version, storage prefix, simulator type and summary, plus signed links to the plot images and a presence map of the run's artifacts. Asking without a number gives you the highest run version in the session.

Be aware of what it does not do: inspect_run does not return the numeric contents of the data files. It tells you which artifacts exist, gives you the images, and hands back the metadata the run recorded — for a CCT sweep that metadata includes the rates and the final phase fractions per rate. It is not a way to read a results table row by row.

Refer back in a later turn#

The active session material persists in a session, so a follow-up needs no re-loading:

Run the same heat treatment on 22MnB5 instead.

Two things stay true when you do this. Phases runs only the simulator you named in that message, and it will not re-run a simulation merely because you asked about an earlier one — inspecting run 3 does not authorize a new run. If you want a new run, say so.

For spot welding there is a specific reuse path: when microstructure tracking is enabled, a run can reuse a previous run's plate material card per plate. Outside that case, material reuse works through the session material or a saved workspace material, not through the run.

Browse the artifacts#

Signed in, you have two browsing surfaces: the Simulation Runs panel behind the Runs button, which lists the current session's runs and their files, and the simulation panel's Results tab, which lists them as rows with View / Hide, Reconfigure and delete actions. Both are described in full in Sessions, runs and artifacts.

The practical detail worth knowing here is how you get a file out. Neither surface has a per-row download button. In the Runs panel the file list is filtered to .png and .gif; click a file and it opens in an inline viewer below the list, which does have a download button — that is the route to a saved copy of a plot. Because of that image filter, the numeric text files a run writes are not browsable there on an ordinary account, so plan on reading results from the plots and from what the agent reports in the conversation.

Guests do not get any of this. The Runs panel, the Materials pages, the simulation panel and the chat-history sidebar all require a signed-in account — see Guests and limits.

Sharing in Phases is per conversation, not per run. In the left sidebar, open the … menu on the chat you want and choose Share. A dialog titled Share link to chat appears, with the description "Anyone with the URL will be able to view the shared chat.", the chat title, its date and its message count, and a Copy link button. Copying puts the URL on your clipboard and confirms with a "Share link copied to clipboard" toast.

The link is a /share/ URL ending in the chat's own id.

What the recipient sees on that page: the chat title as a heading, a line giving the creation date and the message count, and the full rendered conversation. What they do not see:

No sign-in is required, so treat the URL as public to anyone who has it.
The interactive configuration cards do not render on a shared page. Your reader gets the conversation and the result images, not runnable controls.
The Runs panel and artifact browsing are not on the shared page.
There is no un-share control in the product interface. Share deliberately.

If the conversation should not be public, send the results another way rather than the link.

Delete#

The same … menu has Delete, guarded by an "Are you absolutely sure?" confirmation warning that this permanently deletes the chat and removes the data. Clear chat history in the user menu does the same across your history and can report a partial result when some sessions still hold active simulation data.

Deletion is refused while a run is still executing or an artifact write is in flight; retry once the run reaches a terminal state. Deleted session IDs and run versions are permanently retired.

One caveat worth knowing: artifact links are signed and time-limited. A link that was already issued keeps working until it expires — deleting a run does not revoke a URL someone already holds.

Variations#

Pick up a comparison. List my runs, then Inspect run 2 and run 5 and show me their diagrams. See Compare two grades.

Re-run with one change. Use Reconfigure in the Results tab to load an old configuration into the Configure tab, adjust one field, and run again. This is the fastest way to extend a weld schedule sweep.

Keep the material, not just the run. If a chemistry is worth reusing across sessions, save it to your workspace rather than hunting for the run that used it.