-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added ragged workspace as concept Re #11810
- Loading branch information
Lottie Greenwood
committed
Jun 21, 2016
1 parent
c68d794
commit c96a4f1
Showing
2 changed files
with
17 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
.. _Ragged_Workspace: | ||
|
||
Ragged Workspace | ||
================= | ||
|
||
What are they? | ||
-------------- | ||
|
||
A ragged workspace is one where the spectra within it do not share a common set of x values. Ragged workspaces commonly occur after Converting the X units using ConvertUnits or after DiffractionFocussing. | ||
|
||
Displaying the ragged data using 1D line plots or 2D colour or contour plots is fine, but the data will display incorrectly when using 3D plots. The instrument view is unaffected as it displays integrated data. | ||
|
||
Many algorithms cannot operate on Ragged Workspaces, either due to logical or implementation restrictions. If you encounter these problems you may wish to run a Rebin algorithm first to map the data to a regular datagrid of X values. | ||
|
||
|
||
.. categories:: Concepts |