Skip to content

Commit d688f5f

Browse files
spelling
1 parent eed33f8 commit d688f5f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

doc/specific_iocs/dae/DAE-Live-View.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,30 +2,30 @@
22

33
## normal integral 2D detector live view
44

5-
The DAE, when in [event mode](#dae_event_histogram_modes), can serve up an [AreaDetector](https://github.com/areaDetector/ADCore) image of the neutron data as a `detector live view` device screen. The data created by areaDetector canalso be viewed using an ImageJ plugin or as an Intensity plot in CSS.
5+
The DAE, when in [event mode](#dae_event_histogram_modes), can serve up an [AreaDetector](https://github.com/areaDetector/ADCore) image of the neutron data as a `detector live view` device screen. The data created by areaDetector can also be viewed using an ImageJ plugin or as an Intensity plot in CSS.
66

77
Using the live view device screens you can add several views, the DET macro indicates a view number and starts at 1 and can go up to 10
88

9-
Running the DAE in event mode works best (is quickest), this will need an event mode wiring table and also defining a second time regime in the time channels section. If you nede to run it in histogram mode it will be slower as it will have to download all histograms to integrate every time, in event mode these are pre-created for fast access.
9+
Running the DAE in event mode works best (is quickest), this will need an event mode wiring table and also defining a second time regime in the time channels section. If you need to run it in histogram mode it will be slower as it will have to download all histograms to integrate every time, in event mode these are pre-created for fast access.
1010

1111
Live view PVs have a root prefix of `%MYPVPREFIX%DAE:AD1:` for detector view 1 etc
1212

13-
Open the live view settings page and then you need to specify a few items. Standard data is stored in the DAE as a set of spectra starting at nuber 1 (spectrum 0 is a special spectrum for unassigned data). The DAE has no knowledge of detector shape, however a contiguous block of spectrum numbers usually corresponds to rastering by row or column of a 2D detector. So for example you may have a detector sized 600x400 pixels - in the DAE this may be stored as 600 contiguous blocks of 400 elements, so you need to tell the view
13+
Open the live view settings page and then you need to specify a few items. Standard data is stored in the DAE as a set of spectra starting at number 1 (spectrum 0 is a special spectrum for unassigned data). The DAE has no knowledge of detector shape, however a contiguous block of spectrum numbers usually corresponds to rastering by row or column of a 2D detector. So for example you may have a detector sized 600x400 pixels - in the DAE this may be stored as 600 contiguous blocks of 400 elements, so you need to tell the view
1414
* starting spectrum number: at what spectrum number does the first detector pixel correspond to. This is usually not 1 as the first few spectra are usually assigned to monitors.
1515
* x pixels and y pixels: size of the detector
16-
The liveview dispay will then real xsize x ysize spectra and recreate the two dimensional structure. Other variables you can set are:
16+
The liveview display will then real `xsize` x `ysize` spectra and recreate the two dimensional structure. Other variables you can set are:
1717

1818
* integral mode: see total counts so far, or counts since last poll
1919
* integral trans mode: do you want to see plot of pure counts, logarithm of counts etc.
2020
* scale to zero: is scale to use `0 -> max counts` or `min counts` to `max counts`
2121
* specify a region of interest (ROI) and binning, or just leave as as to see all
2222
* spec mode: is the dae in event or [histogram mode](#dae_event_histogram_modes)
23-
* data mode: noremally `TOFSummed`, `TOF channel` is a special mode for linear (1D) detectors, it uses the linear detector pixel number as one axes and the time of flight as the other giving a 2D view. Used on POLREF amnd INTER for example.
23+
* data mode: normally `TOFSummed`, `TOF channel` is a special mode for linear (1D) detectors, it uses the linear detector pixel number as one axes and the time of flight as the other giving a 2D view. Used on POLREF and INTER for example.
2424
* rotation: is the image the right way round or needs to be flipped
2525
* period: dae period number to display, or use 0 for current period
2626
* running: choose to enable or disable liveview.
2727

28-
depending on the number of spectra, EPICS `MAX_ARRAY_BYTES` may need adjusting - this would only be for a PCAS based server, so the gateway for example if you nede to view teh liveview off instrument.
28+
depending on the number of spectra, EPICS `MAX_ARRAY_BYTES` may need adjusting - this would only be for a PCAS based server, so the gateway for example if you need to view the liveview off instrument.
2929

3030
## 1D detector with TOF axis giving 2D view (data mode: `TOF channel`)
3131

0 commit comments

Comments
 (0)