Difference between revisions of "34ID-E Data Analysis Overview"
From 34-ID-E
Jump to navigationJump to searchm (moved 34ID-E Data Analysis Overivew to 34ID-E Data Analysis Overview: title typo corrected) |
|||
| Line 1: | Line 1: | ||
{{Incomplete}} | {{Incomplete}} | ||
<!-- Overview --> | |||
* | A wide variety of measurements can be carried out at 34ID-E: white beam or mono beam, step scans or slew scans, with area detectors or point detectors, depth-resolving or not, etc. Hence a collection of tools are developed to tackle different types of data sets. | ||
** single | |||
** | A majority of analysis and visualization functions are built into '''[[LaueGo]]''', a package developed at 34ID-E based on [[IGOR Pro]] which runs on a single PC or Mac. | ||
== Data types and formats == | |||
* Each exposure of an [[34ID-E Detectors|area detector]], if file-saving is turned on, creates a file containing 2D data. By default our detector images are saved in the [[NeXus format]] [http://www.nexusformat.org/ NeXus format], which is based on [[wikipedia:Hierarchical Data Format | HDF-5]]. | |||
** Note: with special configurations, such as the [[fly-scan mode]], multiple exposures can be saved in a single data file as a 3D array. | |||
* Each scan automatically creates a *.mda file that is sequentially numbered. The mda file stores motor positions and pre-selected scaler counts at each scan step. | |||
** Only the motors that are being scanned are recorded in mda files. | |||
* For multichannel analyzer (MCA) fluorescence detectors, total counts of each window of channels are recorded as scalers, and stored in the mda files. | |||
== Types of Analysis == | |||
=== Depth-resolved scans (wire scans) === | |||
Data from depth-resolved measurements requires [[Reconstruction of Depth-Profiling Data | reconstruction]], which is carried out by a multi-node Linux cluster at APS. | |||
=== White-beam Laue images === | |||
===== Single image ===== | |||
[[Single Laue Image Analysis with LaueGo]] | |||
===== Multiple images ===== | |||
=== Monochromatic beam data (energy scans) === | |||
=== Scaler data (mda files) === | |||
== See Also == | |||
Revision as of 23:15, 19 August 2013
| (This article/section is incomplete, please check back again or help expanding it) |
A wide variety of measurements can be carried out at 34ID-E: white beam or mono beam, step scans or slew scans, with area detectors or point detectors, depth-resolving or not, etc. Hence a collection of tools are developed to tackle different types of data sets.
A majority of analysis and visualization functions are built into LaueGo, a package developed at 34ID-E based on IGOR Pro which runs on a single PC or Mac.
Data types and formats
- Each exposure of an area detector, if file-saving is turned on, creates a file containing 2D data. By default our detector images are saved in the NeXus format NeXus format, which is based on HDF-5.
- Note: with special configurations, such as the fly-scan mode, multiple exposures can be saved in a single data file as a 3D array.
- Each scan automatically creates a *.mda file that is sequentially numbered. The mda file stores motor positions and pre-selected scaler counts at each scan step.
- Only the motors that are being scanned are recorded in mda files.
- For multichannel analyzer (MCA) fluorescence detectors, total counts of each window of channels are recorded as scalers, and stored in the mda files.
Types of Analysis
Depth-resolved scans (wire scans)
Data from depth-resolved measurements requires reconstruction, which is carried out by a multi-node Linux cluster at APS.
White-beam Laue images
Single image
Single Laue Image Analysis with LaueGo
