Correlative SECCM–SEM/EBSD dataset for 316L pitting: CA traces, descriptors, and imaging tables

This record provides the dataset associated with a correlative SECCM–SEM/EBSD study of localized electrochemical activity (chronoamperometry, CA) on 316L stainless steel. The dataset includes raw SECCM CA traces, complementary acquisition parameters, electrochemical descriptor tables, footprint-area estimates used for normalisation, and correlative imaging tables (SEM/EBSD). A derived descriptor table normalised by footprint area is also included. Main use-case Reproduce the preprocessing and descriptor extraction workflow used in the study. Enable re-analysis, benchmarking, and development of alternative descriptor extraction / ML pipelines. Support correlative analysis between SECCM activity and SEM/EBSD-derived microstructural features. Files (CSV/TXT)Required by the main notebook workflow: SS_NaCl_CA_M_1031_C.csv — raw SECCM chronoamperometry (CA) traces. CA_SECCM_descriptors_area.csv — electrochemical descriptor table derived from the CA traces (non-normalised). labels.csv — labels used for downstream analysis (e.g., classes/clusters). SEM_EBSD.csv — SEM-derived table for the region correlated with EBSD. selected_oval_pixels.csv — footprint (droplet/cell) estimates used to compute footprint area for each site. Optional / auxiliary: SS_NaCl_Parameters_M_1031_C.csv — complementary SECCM acquisition/metadata parameters. ebsd_filtered.csv — EBSD-derived table for the correlated region (processed/filtered). oxygen_flux.txt — COMSOL FEM table (droplet diameter vs total oxygen flux magnitude). Derived (generated by the notebook; included for convenience): CA_SECCM_descriptors_area_normalised.csv — descriptor table normalised by footprint area (per cm²). How to use Download this dataset and place the files in a local folder (keep filenames unchanged). Run the reproducible preprocessing and descriptor extraction notebook from the companion GitHub repository: GitHub: https://github.com/bcoelho-leonardo/seccm-ebsd-316l-pitting Related work Associated publication DOI: 10.1016/j.corsci.2026.113708 (linked in “Related identifiers”) Notes The primary index key used across tables is map_id (or equivalent site identifier). Filenames are intentionally fixed to simplify reproducibility and reduce configuration overhead. ContactLeonardo Bertolucci Coelho (contact person)