- The integration reads log files read-only and never modifies or moves them.
- It uploads each file’s raw bytes as they are written. Atomscale keeps the original file and parses it into timeseries.
- For CSV logs, you name channels in a parsing schema. Atomscale recognizes common channels, such as source shutters and substrate temperature, and shows them under a standard name, for example Source Shutter(element=Ga) for
ga_shutter.
Supported Formats
The Format list also shows Riber (CHR), but Atomscale can’t decode native Riber CHR files
yet. They upload but end with a parsing error. On Riber systems, export the recorder data as CSV
and use the CSV format.
Requirements for CSV Logs
What You Get in Atomscale
Each log file becomes one Tool State data item named after when its capture started, for example Tool Logs - 5:14 PM, Jan 6, 2026. With EpiTrend, each hour of recording becomes its own data item.
A tool log joins the growth it ran alongside only when its integration is linked to the same Growth Instrument as the RHEED camera. See Finding Your Data.
Set It Up
Set Up Tool Logs
Configure the Tool Log Streamer for CSV or EpiTrend logs.
Parsing Schema Reference
Describe your CSV log’s columns, units, and timestamps.