Skip to content

polish: EDS results header and exports name every region "Region", so region exports overwrite each other #99

Closed
mac4DSTEM/MacEMUI
#69

Description

@Paullo9

Repro. Open data/stem-edx/SI HAADF 1339 65000 x 20260508.emd (also 1840, 1456) in the EDS room. Draw a rectangle (Region 1) and an ellipse (Region 2) on the colour mix, then Quantify each. This is the new EDXRegionsRealFileJourney; it draws through the room's keyboard route (click the mix, then Return).

Seen. The results header reads Results · Region for both regions, while the region table and the spectrum legend name them Region 1 and Region 2. Results CSV writes SI_HAADF_1339_65000_x_20260508_Region quantification.csv for every region, so exporting Region 2 overwrites Region 1. The CSV's region line and the spectrum CSV also say Region.

Expected. The header, export file names and CSV region lines carry the region's own name (Region 1, or the name it was renamed to), as EDXRealFileJourney.test04 already expects (Results · Region 1). A drawn but unkept selection stays Region.

Where. MacEMUI ShellEDXModel/EDXSession.swift: regionName, exportStem, resultsCSV, spectrumCSV and the Auto ID input use region.name (always "Region" for a shape) and never the selected pin's name. The fix goes in MacEMUI, and macTEM takes it with the next MacEMUI version.

Screenshots: the journey's xcresult, step "Quantify Region 2" ($MACTEM_GATE_DIR/ui-screenshots/). Found 2026-11-05.

Activity

  1. self-assigned this
    on Nov 5, 2026
  2. Paullo9 commented on Nov 5, 2026

    @Paullo9
    ContributorAuthor

    Fix: mac4DSTEM/MacEMUI#69 (the code is in MacEMUI's ShellEDXModel). macTEM picks it up with the next MacEMUI release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions