...
Warnings and Fixes to be done
DEVIL204-Porting to LV12 for Linux on Virtual Machine
# | Title | User Story | Importance | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | DEVIL204-Global write to memcached
| As a developer I want GGODSta.vi and GGODDyn.vi have the "append" and "write" cases ENABLED so that I can validate real memcached write operations. | Must Have |
| ||||||||||||
2 | DEVIL204-Update DBFiles
| As a developer I want updated versionof DEVILs' DBFiles so that I can use them for loading data. | Must Have |
| ||||||||||||
3 | DEVIL204-Program data loading
| As a developer I want valid orbit values (that is equal to legacy Apple data) so that I can use the same UI. | Must Have | |||||||||||||
4 | DEVIL204-Optimize bundleORB VIs | As a developer I want a fast ORB dataset recontruction so that I can obtain a real time orbit acquisition. | Must Have |
| ||||||||||||
5 | DEVIL204-Database
| As a developer I want all the data available in the new program global variables so that I can develop the acquisition code. | Must Have | |||||||||||||
6 | DEVIL204-DBFiles | As a developer I want the DEVIL204 DBSta and DBDyn in the real working directory so that the DCS can find them where espected. | Must Have |
| ||||||||||||
7 | DEVIL204-HWMaskArray
| Fix the HW mask | Must Have |
...
Data type | Name | Description |
---|---|---|
[DBL] | part X | Array of 32 DBL: see corresponding control description above. The array is returned both for read and write operations. |
[DBL] | part X | Array of 32 DBL: see corresponding control description above. The array is returned both for read and write operations. |
errorCluster | errorOut | [ACQ numbers mismatch (num0, num1, num2, num3)] |
Details
Each one of the 4 DEVILs has a circular buffer of 1927 lines named "sockets". Write operations of the four circular buffers are synchronized via a common stobe so that the four write pointers are always alligned. At each strobe, each DEVIL stores a "socket" composed as:
DBL ACQNum [0, 1926]; The socket header is written twice: at the beginning of the socket (before part X) and again in the middle of the socket (before part Y) the content of the two headers being the same; this is due to historical reasons and – although it is a waste of memory space – it was left in order not to compromise the functioning of other pieces of code that access the same memory area.
[DBL] 32 values of the BPM X signals from the Bergoz modules read from that DEVIL;
[DBL] 32 values of the BPM Y signals from the Bergoz modules read from that DEVIL. The 32 components in part X and Y are ordered according to the cabling and do not necessarily follow the sequence of the BPMs along the vacuum chamber. Moreover the 32 values refer to both e- and e+ rings for which the BPMs sequence is obviously different. As a consequence, part X and Y must be considered as raw containers and their content must be further processed in order to reconstruct the real orbit. |
...