Debian Codegraph @

conversion/dicomserver_sonata/siemens_include/ds_transformation_control.h

raw
1 /*[- HEADER FILE -------------------------------------------------------------------------*/
2 /*
3 Name: ds_transformation_control.h
4
5 Description: The header file defines the types, constants and macros necessary to
6 control a data set transformation.
7
8 NOTE
9 The discussion about graphic representation has not finished in the
10 moment (1989-DEC). A final declaration is possible after publishing the
11 graphic discussion results.
12
13
14 Author: THUMSER, Andreas (TH); Siemens AG UBMed CMS/SCE64; phone: 09131 844797
15 */
16 /*]-----------------------------------------------------------------------------------------*/
17
18 #ifndef DS_TRANSFORMATION_CONTROL
19 #define DS_TRANSFORMATION_CONTROL
20
21
22 /*== "Interpace Pointer List" ============================================================*/
23
24 /*[
25 Description: Entity "Interpace Pointer List"
26
27 The most important part to control the transformation is the Interface
28 Pointer List. To use the data set library build up function "ds_build_up_
29 cms_nema_data_set() to export an Internal Data Set or the data set library
30 separation function "ds_separate_common_data_set() to import a NEMA Data
31 Set this structure must be filled with data to control the transformation.
32 This structure is the link between the different data areas in the host
33 memory.
34
35 The following C-code fragment shows an example to fill an Interface Pointer
36 List before a NEMA Data Set is build up and separate respectively.
37 The example areas are named 'MyHead', 'MyGraphic', 'MyData' for Internal
38 Data Set and 'NemaSet' for the NEMA Data Set. The Interface Pointer List
39 'MyInterface' is used.
40 Please note such areas must be available and filled with valid data before
41 a data set transformation can be done. It is the user's responsibility to
42 ensure that enough storage is available for the different areas.
43
44 To avoid nested comments in the source file the C++ comment sign "//" is
45 used.
46
47 // SEQUENCE: build up CMS defined NEMA Data Set
48 ...
49 // update interface pointer list
50 MyInterface.In.HeadAddress = &MyHead; // pointer to head area
51 MyInterface.In.HeadLength = sizeof(header_t); // length of head area
52 MyInterface.In.GraphicAddress = MyGraphic_p; // pointer to graphic area
53 // or DS_VOID_NIL
54 MyInterface.In.GraphicLength = MyGraphicLength; // length of graphic area
55 // or Integer_UNDEFINED
56 // or 0
57 MyInterface.In.DataAddress = (void *)MyData_p; // pointer to data area
58 MyInterface.In.DataLength = MyDataLength; // length of data area 1)
59
60 MyInterface.Ex.HeadAddress = MyNema_p; // pointer to NEMA area
61 MyInterface.Ex.HeadLength = Integer_UNDEFINED; // filled during build up
62 MyInterface.Ex.GraphicAddress = DS_VOID_NIL; // filled during build up
63 MyInterface.Ex.GraphicLength = Integer_UNDEFINED; // filled during build up
64 MyInterface.Ex.DataAddress = DS_VOID_NIL; // filled during build up
65 MyInterface.Ex.DataLength = Integer_UNDEFINED; // filled during build up
66 MyInterface.Ex.DataGroup = (short) Integer_UNDEFINED; // filled during build up
67
68 MyInterface.CntStatus.Owner = DS_owner_UNDEFINED; // initialization
69 MyInterface.CntStatus.Modality = <required modality>; // p r e s e t t i n g !!
70 MyInterface.CntStatus.Code = DS_code_UNDEFINED; // initialization
71 MyInterface.CntStatus.StatusFileAddress = MyFileAddress; // pointer to mapped status file
72 MyInterface.CntStatus.StopItem.GroupNumber = 0; // initialization
73 MyInterface.CntStatus.StopItem.ElementNumber = 0; // initialization
74 ...
75
76 1) The pure data length in bytes is also stored into item Number of Data Bytes
77 (0019'H,1060'H).
78
79
80 // SEQUENCE: separate common Data Set
81 ...
82 // update interface pointer list
83 MyInterface.In.HeadAddress = &MyHead; // pointer to head area
84 MyInterface.In.HeadLength = sizeof(header_t); // length of head area
85 MyInterface.In.GraphicAddress = MyGraphic_p; // pointer to graphic area
86 MyInterface.In.GraphicLength = Integer_UNDEFINED; // filled during separation
87 MyInterface.In.DataAddress = (void *)MyData_p; // pointer to data area
88 MyInterface.In.DataLength = Integer_UNDEFINED; // filled during separation
89
90 MyInterface.Ex.HeadAddress = MyNema_p; // pointer to NEMA area
91 MyInterface.Ex.HeadLength = Integer_UNDEFINED; // filled during separation
92 MyInterface.Ex.GraphicAddress = DS_VOID_NIL; // filled during separation
93 MyInterface.Ex.GraphicLength = Integer_UNDEFINED; // filled during separation
94 MyInterface.Ex.DataAddress = DS_VOID_NIL; // filled during separation
95 MyInterface.Ex.DataLength = Integer_UNDEFINED; // filled during separation
96 MyInterface.Ex.DataGroup = (short) Integer_UNDEFINED; // filled during separation
97
98 MyInterface.CntStatus.Owner = DS_owner_UNDEFINED; // initialization or presetting
99 MyInterface.CntStatus.Modality = Modality_UNDEFINED; // initialization or presetting
100 MyInterface.CntStatus.Code = DS_code_UNDEFINED; // initialization
101 MyInterface.CntStatus.StatusFileAddress = DS_STATUS_FILE_NIL; // not used during separation
102 MyInterface.CntStatus.StopItem.GroupNumber = 0; // initialization
103 MyInterface.CntStatus.StopItem.ElementNumber = 0; // initialization
104 ...
105 */
106
107
108 /* DECLARATION: declare the interpace pointer list types */
109
110 typedef enum transformation_status_tag
111 {
112
113 /* NOTE: enum transformation_status_tag */
114 /* The data set library defined transformation control status is supported by native
115 language support (nls). This means it is possible to use this code for a detailed status
116 messages after a transformation task. For example the following lines
117
118 // SEQUENCE: transformate data set
119 MyStatus = ds_separate_common_data_set(&MyInterface);
120
121 // SEQUENCE: show transformation task status
122 printf("\ninfo: separate data set: (%s)", nls_message((int) MyStatus));
123 printf("\n (%s)", nls_message((int) MyInterface.CntStatus.Code));
124
125 print after transformatin task with error
126
127 info: separate data set: ret: (DS_RET_WITH_ERROR an error occur during transformation task)
128 (DS_CODE_SET_OUT_OF_ORDER data set out of order)
129
130
131 */
132
133 DS_code_DATA_SET_OUT_OF_ORDER =
134 DS_CODE_SET_OUT_OF_ORDER, /* Error - groups or elements not
135 in ascending order. Build up or
136 separation was aborted. */
137 DS_code_END_OF_DATA_SET_FOUND =
138 DS_CODE_END_OF_SET_FOUND, /* Error - End Of Data set was
139 encountered. Build up or
140 separation was aborted. */
141 DS_code_FATAL_ERROR =
142 DS_CODE_FATAL_ERROR, /* Error - fatal error occured
143 during data set transformation
144 Build up or separation was
145 aborted. */
146 DS_code_FIRST_ELEMENT_IN_GROUP_INVALID =
147 DS_CODE_FIRST_ELEMENT_INVALID, /* Error - first element in group
148 is not element Group Length
149 (x'H,0000'H). Build up or
150 separation was aborted. */
151 DS_code_INVALID_MODALITY =
152 DS_CODE_INVALID_MODALITY, /* Error - desired modality is not
153 supported. Build up or
154 separation was aborted. */
155 DS_code_INVALID_SOM0_PARAMETERS =
156 DS_CODE_INVALID_SOM0_PARAMETERS, /* Error - given data set can not
157 transformed. Build up or
158 separation was aborted. */
159 DS_code_INVALID_INTERFACE =
160 DS_CODE_INVALID_INTERFACE, /* Error - the interface pointer
161 list dosen't contain length
162 information. Separation of
163 internal data set was aborted. */
164 DS_code_NO_OWNER =
165 DS_CODE_NO_OWNER, /* Error - no owner entries found
166 in shadow groups. Build up or
167 separation was aborted. */
168 DS_code_TRANSFORMATION_NOT_POSSIBLE =
169 DS_CODE_TRANSFORM_NOT_POSSIBLE, /* Error - The transformation is
170 not possible, because required
171 dependencies are not fulfilled.
172 Please see data set library
173 function descriptions
174 "ds_*_check_if_transformation_pos
175 sible()" for more information. */
176 DS_code_UNKNOWN_COMPRESSION_CODE =
177 DS_CODE_UNKNOWN_COMPRESSION, /* Error - compression code is
178 unknown or not supported. Build
179 up or separation was aborted. */
180 DS_code_UNKNOWN_DATA_SET =
181 DS_CODE_UNKNOWN_DATA_SET, /* Error - data set format is
182 unknown. Build up or separation
183 was aborted. */
184 DS_code_UNKNOWN_HEADER =
185 DS_CODE_UNKNOWN_HEADER, /* Error - header format is
186 unknown. Build up or separation
187 was aborted. */
188 DS_code_UNKNOWN_OVERLAY =
189 DS_CODE_UNKNOWN_OVERLAY, /* Warning - a given overlay number
190 is invalid. The build up task
191 omitted the build up of this
192 overlay group. */
193 DS_code_MISSING_TYP_1_VALUE =
194 DS_CODE_MISSING_TYP_1, /* Warning - not all type 1 NEMA
195 items could be build up, that
196 means an invalid NEMA Data Set
197 was build up or separated. */
198 DS_code_MULTIPLE_ERROR =
199 DS_CODE_MULTIPLE_ERROR, /* Warning - several errors
200 detected. This means more than
201 one type 1 item values are
202 missing or a type 1 value is
203 missing and one or more other
204 item values are not filled. An
205 invalid NEMA Data Set was build
206 up or separated. */
207 DS_code_MULTIPLE_FATAL_ERROR =
208 DS_CODE_MULTIPLE_FATAL_ERROR, /* Error - several fatal errors
209 detected. This means more than
210 one error occures to abort the
211 transformation. No external data
212 set is filled. */
213 DS_code_NOT_ALL_FILLED =
214 DS_CODE_NOT_ALL_FILLED, /* Warning - not all Internal Data
215 Set parameters could be filled
216 or not all required NEMA items
217 could be built up. This
218 parameters are set 'undefined'.
219 That means an valid NEMA Data
220 Set was build up, but it is
221 possible that this data set
222 contains to less information for
223 special CMS internal use. */
224
225 DS_code_NORMAL = DS_CODE_NORMAL, /* successful transformation */
226 DS_code_UNDEFINED = DS_CODE_UNDEFINED /* initialization value */
227
228 } transformation_status_t;
229
230
231
232 typedef enum data_set_owner_tag
233 {
234 DS_owner_CMS_NEMA = 1, /* The data set is NEMA defined
235 with CMS expansions. The format
236 is defined in [DS File Format]
237 and [DS Item Format] */
238 DS_owner_NEMA = 2, /* The data set is NEMA defined.
239 Possible available expansions
240 are unknown and not analyzed.
241 The format is defined in [NEMA
242 Image], [NEMA Image88] and [NEMA
243 Image89]. */
244 DS_owner_NUMARIS2_FRAMED = 3, /* The data set is Siemens defined
245 with a NEMA frame. The format is
246 defined in [MR Header]. */
247 DS_owner_SOMARIS1_FRAMED = 4, /* The data set is Siemens defined
248 with a NEMA frame. The format is
249 defined in [CT Header] and [CT
250 Image]. */
251 DS_owner_SOMARIS1_BLOCKED = 5, /* The data set is Siemens defined
252 as a binary data stream. The
253 format is defined in [CT
254 Header]. */
255 DS_owner_SOMARIS0_FRAMED = 6, /* The data set is Siemens defined
256 with a NEMA frame. The format is
257 defined in [CT DRH Header] and
258 [CT Image]. */
259 DS_owner_SOMARIS0_BLOCKED = 7, /* The data set is Siemens defined
260 as a binary data stream. The
261 format is defined in [CT DRH
262 Header]. */
263 DS_owner_CMS_BLOCKED = 8, /* The data set is CMS defined
264 as a binary data stream. The
265 format is defined in [DS File
266 Format], [DS Item Format] and
267 [DS Reference Manual]. */
268 DS_owner_NUMARIS1_FRAMED = 9, /* The data set is Siemens defined
269 with a NEMA frame. The format is
270 defined in [MR NUM1 Header]. */
271 DS_owner_NUMARIS1_BLOCKED = 10, /* The data set is Siemens defined
272 with a binary data stream. The
273 format is defined in [MR NUM1
274 Header]. */
275 DS_owner_UNKNOWN = -99, /* The data set format is unknown.
276 No separation is possible */
277
278 DS_owner_UNDEFINED = Enum_UNDEFINED /* initialization */
279 } data_set_owner_t;
280
281
282
283 typedef struct keyword_tag
284 {
285 short GroupNumber; /* item group number */
286 short ElementNumber; /* item element number */
287 } keyword_t;
288
289
290 typedef struct control_area_ex_tag /* - NEMA Data Set - */
291 {
292 char *HeadAddress; /* header area address (base
293 address of NEMA Data Set byte
294 stream, is also base address of
295 item key of item Group Length
296 (0008'H, 0000'H)) */
297 long HeadLength; /* header area length in byte */
298 char *GraphicAddress; /* graphic area address (base
299 address of item key of item
300 Group Length (6021'H, 0000'H)) */
301 long GraphicLength; /* graphic area length in byte */
302 char *DataAddress; /* data area address (base address
303 of item key of item Group Length
304 (<DataGroup>, 0000'H)) */
305 long DataLength; /* data length in byte */
306 short DataGroup; /* NEMA data group */
307 } control_area_ex_t;
308
309
310 typedef struct control_area_in_tag /* - Internal Data Set - */
311 {
312 header_t *HeadAddress; /* header area address */
313 long HeadLength; /* header area length in byte */
314 char *GraphicAddress; /* graphic area address */
315 long GraphicLength; /* graphic area length in byte */
316 void *DataAddress; /* data area address */
317 long DataLength; /* data length in byte */
318 } control_area_in_t;
319
320
321 typedef struct control_status_tag
322 {
323 data_set_owner_t Owner; /* Format of source data set. This
324 parameter must be initialized by
325 separation with the known owner
326 or with 'DS_owner_UNDEFINED'. If
327 'DS_owner_UNDEFINED' is used,
328 the data set library will
329 determine the data set owner. If
330 a preset owner not equal the
331 real owner of data set the
332 separation is aborted. During
333 build up the owner is always set
334 by data set library functions to
335 'DS_owner_CMS_NEMA'. */
336 modality_t Modality; /* Modality of source data set.
337 This parameter must be
338 initialized by separation with
339 the required modality or with
340 'Modality_UNDEFINED'. If
341 'Modality_UNDEFINED' is used,
342 the data set library will
343 determine the data set modality
344 during separation. If a preset
345 owner not equal the real owner
346 of data set the separation is
347 aborted. During build up the
348 modality must be always preset
349 with a supported modality value
350 ('Modality_CT' or
351 'Modality_MR'). */
352 DS_STATUS_FILE_TYPE *StatusFileAddress; /* Common Status File address. This
353 parameter can be set if a status
354 file mapped outside of the data
355 set library. Otherwise this
356 parameter must be set to nil
357 (DS_STATUS_FILE_NIL). If acssess
358 to a status file possible the
359 Unique Identifier
360 (0009'H,1015'H) is build up with
361 common status file information
362 otherwise the non PACS
363 presettings are used. */
364 transformation_status_t Code; /* Detailed status code. This
365 parameter is set by data set
366 library. */
367 keyword_t StopItem; /* Last handled item. If an fatal
368 error occur during
369 transformation this parameter
370 contains the error produced item
371 group and element number. This
372 two parameters must be
373 initlaized with 0. */
374 } control_status_t;
375
376
377
378 typedef struct interface_pointer_list_tag
379 {
380 control_area_ex_t Ex; /* Internal Data Set information */
381 control_area_in_t In; /* NEMA Data Set information */
382 control_status_t CntStatus; /* common status information */
383 } interface_pointer_list_t;
384 /*]*/
385
386
387 /*== "NEMA Parser Pointer List" ==========================================================*/
388
389 /*[
390 Description: Entity "NEMA Parser Pointer List"
391
392 The NEMA data set parser works as an anticipationed scanner. In this manner it is possible
393 to analyse the current work item in his NEMA data set context. Detection of end of
394 data set, group change, subgroup change, generation of subgroup owner list, position
395 control during parsing etc. can be done with the same data set library features.
396
397 The NEMA parser pointer list contains several pointers (addresses) to special locations
398 in a NEMA data set, like begin of data set, end of data set, end of current worked
399 group, end of group containing next item. In addition the item keys of current
400 worked item and the following next item are stored.
401
402 But the most importent information for a application programmer is the pointer to
403 the item value of the current worked item. This pointer is used to split, convert or
404 fill the item for internal use.
405
406 For clearness, the 'current worked item' is the item currently analysed, transfered,
407 tested etc. by the running seperation.
408 The 'next item' is the item directly following the worked item in the Nema data set.
409 Durring item separation it is used to approach to the given (searched) item. But this
410 subject is transperent for a application which works in a level higher as level of
411 function ds_seperate_given_item().
412
413
414 The following table shows a comparision of work and next/this item parameter:
415
416 parameter parser base parser current location
417 =========================================================================
418 item group number WorkKey.GroupNumber NextKey.GroupNumber
419 item element number WorkKey.ElementNumber NextKey.ElementNumber
420 item value length WorkKey.ValueLength NextKey.ValueLength
421 begin of item key - BeginOfNextKey
422 begin of item value BeginOfWorkValue -
423 end of group
424 containing item EndOfWorkGroup EndOfThisGroup
425
426 The work item is the current item used by the separation application but the base of
427 scanning by parser.
428 The next/this item is the item current analyzed by the parser. The parameter 'EndOf-
429 ThisGroup' is not named 'EndOfNextGroup' to avoid confusion during reading source
430 code. The term 'next' discribe not the right situation for this pointer.
431 */
432
433
434 /* DECLARATION: declare the NEMA parser pointer list types*/
435
436 typedef struct item_key_tag
437 {
438 short GroupNumber; /* item group number */
439 short ElementNumber; /* item element number */
440 long ValueLength; /* item value length */
441 } item_key_t;
442
443
444 typedef struct nema_parser_pointer_list_tag
445 {
446 item_key_t WorkKey; /* current worked item */
447 item_key_t NextKey; /* next item in data set */
448 char *BeginOfWorkValue; /* points to first byte of item
449 value */
450 char *BeginOfNextKey; /* points to first byte of next
451 item key */
452 char *EndOfWorkGroup; /* points to first byte of group
453 following the current worked
454 group. The last address in this
455 group is EndOfWorkGroup - 1. */
456 char *EndOfThisGroup; /* points to first byte of group
457 following group containing next
458 item. The last address in this
459 group is EndOfThisGroup - 1. */
460 char *BeginOfDataSet; /* points to first byte of data
461 set. */
462 char *EndOfDataSet; /* points to first byte behint the
463 NEMA data set. The last address
464 in the data set is EndOfDataSet
465 - 1. The address EndOfDataSet is
466 not part of the data set. The
467 pointer is only used as stop
468 mark during data set parsing.
469 Don't dereference this pointer
470 to avoid segmentation fault. */
471 } nema_parser_pointer_list_t;
472 /*]*/
473
474
475 /*== "Shadow Subgroup Owner List" ========================================================*/
476
477 /*[
478 Description: Entity "Shadow Subgroup Owner List"
479
480 In each odd-numbered group expect the command information shadow group 1, a fixed block
481 of data element numbers is reserved to identify the "ownership" of sets of data elements.
482 The elements 0010'H to 007F'H are reserved to identify the manufacturer sets of elements.
483 Each identifier element (0010'H to 007F'H) is a type 1 free-formatted (FF) single (S)
484 ASCII string (AT) and contains e.g. the OWNER_STRING_SPI (SPI Recognition Code) for blocks
485 of data elements reserved by SPI or the OWNER_STRING_MED for blocks of data elements
486 reserved by Siemens UBMed.
487
488 The shodow subgroup owner list is used to fit subgroup location order in the NEMA data
489 set byte stream to the CMS program separation order without a parser reset at change
490 from one shadow subgroup to the next. This is necessary for higher performance.
491
492 The shadow subgroup owner list is a two-dimensional array. In the first column are stored
493 the subgroup numbers found by function ds_get_subgroup_owner_code() in ascent order as
494 item element base number.
495 In the second column are stored the CMS defined subgroup owner numbers.
496 The last element of the shadow subgroup owner list must be marked with the end of list
497 element END_OF_OWNER_LIST.
498 The length of the list must be equal the number of listed shadow owner strings.
499
500 The following graphic shows the shodow subgroup owner list format and an example for a
501 CMS defined Identifiying Information (0009'H) shodow group:
502
503 OWNER_NUMBERS SUBGROUP_NUMBERS 'ListCounter'
504 +------------------+------------------+
505 |ItemElementBase |OwnerNumber | 0
506 +------------------+------------------+
507 |ItemElementBase |OwnerNumber | 1
508 +------------------+------------------+
509 |ItemElementBase |OwnerNumber | 2
510 +------------------+------------------+
511 |END_OF_OWNER_LIST |END_OF_OWNER_LIST | 3
512 +------------------+------------------+
513 ..... ..
514 +------------------+------------------+
515 |END_OF_OWNER_LIST |END_OF_OWNER_LIST | MAX_OWNER
516 +------------------+------------------+
517
518 OWNER_NUMBERS SUBGROUP_NUMBERS 'ListCounter'
519 +------------------+------------------+
520 | 0x1000 |OWNER_NUMBER_SPI_1| 0
521 +------------------+------------------+
522 | 0x1100 |OWNER_NUMBER_MED | 1
523 +------------------+------------------+
524 | 0x1200 |OWNER_NUMBER_CMS | 2
525 +------------------+------------------+
526 | 0x1300 |OWNER_NUMBER_LAB | 3
527 +------------------+------------------+
528 |END_OF_OWNER_LIST |END_OF_OWNER_LIST | 4
529 +------------------+------------------+
530 ..... ..
531 +------------------+------------------+
532 |END_OF_OWNER_LIST |END_OF_OWNER_LIST | MAX_OWNER
533 +------------------+------------------+
534
535
536 With this list it is possible to handle the shadow group flexibility defined in
537 [SPI Image] document 4. This means it is possible to parse a NEMA data set
538 without reset the parser at change from one shadow subgroup to the next.
539 */
540 /*]*/
541
542
543 /* DECLARATION: declare the supported shodow subgroup owner */
544
545 #define OWNER_STRING_ACQU "SIEMENS CM VA0 ACQU"
546 #define OWNER_STRING_CMS "SIEMENS CM VA0 CMS "
547 #define OWNER_STRING_CT "SIEMENS CT VA0 GEN "
548 #define OWNER_STRING_CT_COAD "SIEMENS CT VA0 COAD"
549 #define OWNER_STRING_CT_IMA "SIEMENS CT VA0 IMA "
550 #define OWNER_STRING_CT_RAW "SIEMENS CT VA0 RAW "
551 #define OWNER_STRING_LAB "SIEMENS CM VA0 LAB "
552 #define OWNER_STRING_MED "SIEMENS MED "
553 #define OWNER_STRING_MR "SIEMENS MR VA0 GEN "
554 #define OWNER_STRING_MR_COAD "SIEMENS MR VA0 COAD"
555 #define OWNER_STRING_MR_IMA "SIEMENS MR VA0 IMA "
556 #define OWNER_STRING_MR_RAW "SIEMENS MR VA0 RAW "
557 #define OWNER_STRING_MR_SPEC "SIEMENS MR VA0 SPEC"
558 #define OWNER_STRING_SPI_1 "SPI RELEASE 1 "
559 #define OWNER_STRING_SPI_2 "SPI "
560 #define OWNER_STRING_SPI_3 "SPI Release 1 "
561 #define OWNER_STRING_SPI_4 "SPI-VERSION 01.00 "
562 #define OWNER_STRING_SPI_5 "SPI_RELEASE_1_"
563
564
565 /* NOTE: shodow subgroup owner list */
566 /* Don't change the order of the following define-blocks! */
567
568 #define PRE 0
569 #define OWNER_NUMBER_ACQU 0
570 #define OWNER_NUMBER_CMS 1
571 #define OWNER_NUMBER_CT 2
572 #define OWNER_NUMBER_CT_COAD 3
573 #define OWNER_NUMBER_CT_IMA 4
574 #define OWNER_NUMBER_CT_RAW 5
575 #define OWNER_NUMBER_LAB 6
576 #define OWNER_NUMBER_MED 7
577 #define OWNER_NUMBER_MR 8
578 #define OWNER_NUMBER_MR_COAD 9
579 #define OWNER_NUMBER_MR_IMA 10
580 #define OWNER_NUMBER_MR_RAW 11
581 #define OWNER_NUMBER_MR_SPEC 12
582 #define OWNER_NUMBER_SPI_1 13
583 #define OWNER_NUMBER_SPI_2 14
584 #define OWNER_NUMBER_SPI_3 15
585 #define OWNER_NUMBER_SPI_4 16
586 #define OWNER_NUMBER_SPI_5 17
587
588
589 #define MAX_OWNER 17 + 2
590 #define OWNER_STRING_SPI OWNER_STRING_SPI_1
591
592 #define END_OF_OWNER_LIST (-1)
593 #define OWNER_NUMBERS 0
594 #define SUBGROUP_NUMBERS 1
595
596 typedef long shadow_owner_list_t[MAX_OWNER][2];
597
598
599 #endif