Saving and exporting¶
The Export tab on the right twopy sidebar holds every save and export action.
Save ROIs + analysis¶
Click Save ROIs + analysis to save the active recording’s ROIs and the full response analysis. twopy writes the following files beside the current local converted recording:
rois.h5— the ROI masks.analysis_outputs.h5— dF/F traces, grouped responses, the response window / dF/F / smoothing / normalization / QC settings, per-ROI scale factors, and QC scores.response_heatmaps.h5— the heatmap data shown in the Heatmaps tab.exports/csvs/response_summary_trials.csv— per-trial flat table.exports/csvs/response_summary_grouped.csv— per-epoch grouped table.
The save uses the same response window, smoothing, and normalization values you see in the Plot tab.
Cache sync¶
With analysis_caching: true (the default), twopy saves locally first and then syncs the changed files to analysis_output in a background worker. The Metadata tab shows whether the sync succeeded or failed. When the sync publishes export PDFs and PNGs, twopy deletes the local cache copies after the destination copy succeeds.
Image and plot exports¶
Button |
Writes to |
What it saves |
|---|---|---|
Save recording view |
|
The current recording view as an image |
Save ROI view |
|
The ROI Labels layer view |
Save recording ROI overlay |
|
Recording with the ROI overlay |
Save plots |
|
Per-epoch response plot figures |
Save plots with ROIs |
|
Paired ROI-overlay + response figures |
Save heatmaps |
|
The visible heatmaps as PDF + PNG |
All export folders live beside the converted recording. Export PDFs and PNGs follow the same cache-publish flow as the saved analysis files when caching is on.
Reload after editing elsewhere¶
If a teammate updated analysis_outputs.h5 on the network, you can pull it back into the open view with Reload saved analysis on the Load tab. It also rereads the saved ROIs.