Your experimental session has ended. Here is some information about accessing your data and providing feedback to the beamline.
Getting your data from Diamond
There are some instructions on the user office website regarding how to access your data after your visit.
NeXus files & Dawn
We save our data using the NeXus file format. You can open nexus files using anything that can open hdf5 files, such as python, matlab, or Dawn.
Read more about NeXus files
NeXus is an effort by an international group of scientists motivated to define a common data exchange format for neutron, X-ray, and muon experiments. NeXus is built on top of the scientific data format HDF5 and adds domain-specific rules for organizing data within HDF5 files in addition to a dictionary of well-defined domain-specific field names.
For I15-1, this means that every data collections will have at least one associated nexus file, as well as some ancilliary files.
File name / path | Description |
|---|
i15-1-12345.nxs | The primary file that your data collection creates. Contains lots of data, metadata, and links to the detector data (see hdf5 files below) |
i15-1-12345_pe1AD.hdf5 | These hdf files contain the raw data from the detectors. You may have others besides these, and you may not have all of these depending on the configuration of the beamline. Rather than duplicating data, the above nxs file links to these files. |
i15-1-12345_pe2AD.hdf5 |
i15-1-12345_streami0.hdf5 |
i15-1-12345_averagei0.hdf5 |
/processed/i15-1-12345-12345.pe1AD.bragg.nxs | These are the processed nexus files - each automatic process will create its own nexus file to describe both the original data, and the process that was applied. |
/processed/i15-1-12345-12345.pe2AD.bragg.nxs |
/processed/tth_pe1/i15-1-12345_tth_det1_0.xy | The results of your processes are exported to plain-text files. |
/processed/tth_pe2/i15-1-12345_tth_pe2_0.xye |
Read more about opening NeXus files in Dawn
Session Feedback and Experimental report
Acknowledging Diamond