-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathMambo.rst
1281 lines (862 loc) · 38.7 KB
/
Mambo.rst
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
|image0| ICA Group
**P**
**Mambo User Manual**
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| **Diffusion date** | **Writer** | **Auditor** | **Approver** | **Approver’s** | **Modifications** | **Index** |
| | | | | | | |
| | | | | **stamp** | | |
+======================+===============+===============+================+==================+======================================+=============+
| 2005/10/26 | L.Claisse | M.Ounsy | A.Buteau | A.B. | Creation | 1.0 |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| 2005/11/17 | L.Claisse | M.Ounsy | A.Buteau | A.B. | Added multi-AC/VC and file system | 1.1 |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| 2006/11/17 | R.Girardot | M.Ounsy | A.Buteau | A.B. | Screenshots updated | 1.2 |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| 2012/02/15 | A. Fourneau | G.Abeillé | A.Buteau | A.B. | Added tdb long term | 2.1 |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| 2018/02/08 | M.Thiam | R.Girardot | A.Buteau | A.B. | - Document template updated | 3.0 |
| | | | | | | |
| | | | | | - Screenshots updated | |
| | | | | | | |
| | | | | | - Added some missing descriptions | |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
| | | | | | | |
+----------------------+---------------+---------------+----------------+------------------+--------------------------------------+-------------+
Diffusion: for information
Receivers: Any archiving User
|
| **Index**
`*1.* *Introduction* 4 <#_Toc505844906>`__
`*2.* *Application’s context: Historic and Temporary archiving*
4 <#_Toc505844907>`__
`*3.* *Application’s description and goals* 5 <#_Toc505844908>`__
`*3.1* *Application’s goals* 5 <#_Toc505844909>`__
`*3.2* *A first look at Mambo* 6 <#a-first-look-at-mambo>`__
`*4* *Account manager* 7 <#account-manager>`__
`*4.1* *Creating a new account* 7 <#creating-a-new-account>`__
`*4.2* *Deleting an existing Account* 8 <#_Toc505844913>`__
`*4.3* *Launching application with an existing account*
8 <#_Toc505844914>`__
`*5* *Control archiving* 9 <#_Toc505844915>`__
`*5.1* *Creating/modifying an AC* 10 <#_Toc505844916>`__
`*5.2* *The opened ACs menu* 16 <#_Toc505844917>`__
`*5.3* *Starting/Stopping archiving on an AC*
17 <#startingstopping-archiving-on-an-ac>`__
`*5.3.1* *The Current Archiving Configuration detail panel*
17 <#the-current-archiving-configuration-detail-panel>`__
`*5.3.2* *Starting/Stopping archiving on an AC* 17 <#_Toc505844920>`__
`*5.4* *Displaying an AC* 18 <#displaying-an-ac>`__
`*5.4.1* *The Current Archiving Configuration detail panel*
18 <#the-current-archiving-configuration-detail-panel-1>`__
`*5.4.2* *The Archiving assessment window*
19 <#the-archiving-assessment-window>`__
`*5.5* *Saving/Loading an AC* 19 <#_Toc505844924>`__
`*5.5.1* *Saving an individual AC* 19 <#saving-an-individual-ac>`__
`*5.5.2* *Saving all opened ACs* 20 <#saving-all-opened-acs>`__
`*5.6* *Transfer to VC* 20 <#_Toc505844927>`__
`*6* *Exploit archived data* 21 <#exploit-archived-data>`__
`*6.1* *Creating/modifying a VC* 22 <#creatingmodifying-a-vc>`__
`*6.2* *The opened VCs menu* 26 <#the-opened-vcs-menu>`__
`*6.3* *Displaying a VC* 27 <#_Toc505844931>`__
`*6.4* *Saving/Loading a VC* 30 <#savingloading-a-vc>`__
`*6.5* *Using the Variations functionality* 30 <#_Toc505844933>`__
`*7* *Options* 32 <#_Toc505844934>`__
`*7.1* *Application’s history save/load options* 32 <#_Toc505844935>`__
`*7.2* *AC options* 33 <#ac-options>`__
`*7.3* *VC options* 34 <#vc-options>`__
`*7.4* *General options* 35 <#general-options>`__
`*8* *The Mambo toolbar* 36 <#the-mambo-toolbar>`__
\ *Introduction*
================
This document is an end-user guide to using the Mambo application, and a
brief developer-oriented presentation of the application’s architecture.
\ *Application’s context: Historic and Temporary archiving *
============================================================
The goal is the automatic archiving of the values of a set of Tango
Attributes, in a given time range.
In this time range, the value of an attribute is archived:
- Every [*given time interval*]
***AND***
- When the attribute’s value meets [*given condition on attribute’s
value*],
where [*given time interval*] and [*given condition on attribute’s
value*] are user-defined for each attribute (individually or for a
group of attributes).
Each attribute value is associated with a time stamp, representing
the time when the attribute value was read. This time stamp is
archived as well.
Attributes can be archived in two distinct databases:
- The Historical Data Base (***HDB*** henceforth): attributes values
are stored forever.
- The Temporary Data Base (***TDB*** henceforth): every [*given
deletion time*], the oldest attributes values records are
deleted. The TDB is regularly purged. The Interval of this purge
is defined by the data base administrator and the system
administrator.
When an attribute is “being ***archived***\ ”, it means that every
[*base time unit*], the archiving device tests whether the current
value of the attribute has to be stored in HDB (resp. TDB).
If the test is positive, a record is added in the table for this
attribute.
Later, those values can be ***exploited***. It can be selected from
HDB/TDB to be displayed and saved in a file
\ *Application’s description and goals*
=======================================
\ *Application’s goals*
-----------------------
Mambo allows the user to define *configurations* that describe the
archiving and exploitation for a group of attributes. Those
*configurations* can be saved as files and modified.
Mambo is thus naturally divided (both in functionalities and
display) in two parts:
- The archiving control part.
- The archived data exploitation part.
\ **
**
*A first look at Mambo*
-----------------------
|image1|
Figure 1: General view of Mambo
- The Archiving Control panel is where the user controls the archiving
of Tango attributes in HDB/TDB.
To do so, the user can create/modify archiving configurations, and
Start/Stop those configurations.
An ***Archiving Configuration*** is a list of attributes to be
archived, with a list of archiving parameters for each attribute.
Users can also start/stop the archiving of some attributes in the
configuration, (see 5.3.2 *Starting/Stopping archiving on an AC*).
- The Data Exploitation panel is where the user exploits the previously
stored data, mainly displaying curves and extracting raw data
from HDB/TDB.
He does so by creating/modifying ***View Configurations***, and
calling **View** **Stop** on those configurations.
A ***View Configuration*** is a list of attributes to be displayed,
with a list of displaying parameters for each attribute.
- The Menu and the Tool bar are for actions shortcuts and application’s
options.
Each panel will be detailed in its own subsection.
**
**
*Account manager*
=================
The Mambo Account Manager is here to manage accounts, which means:
- Creating a new account.
- Deleting an existing account.
- Launching application with an account chosen in a list.
An account is associated with a directory, in which are stored
application setup and history. Having various accounts allows different
users to have their own application configuration and history.
|image2|
Figure 2: Mambo Account Manager
The above figure presents the account Manager Interface, at
application start. With this manager, user can create a new account,
or delete or use an existing one.
To quit the application, simply click on |image3| or |image4|
button.
Existing accounts are listed in the account Selection Combo Box,
which you can be reloaded by clicking on |image5| button (if you
think that someone could have modified it by creating a new account
or deleting an existing one, for example).
*Creating a new account*
------------------------
To create a new account, click on the |image6| button (at the bottom
left of the panel). A new dialog will appear, as following.
|image7|
Figure 3: Creating a new account
In this new dialog, you will have to enter the name of your new
account and the path of the application working directory for this
account. If you prefer, you can browse for the path by clicking on
the |image8| button. Then, a classic browsing dialog will be
displayed, in which you can choose the directory. When both fields
(“Name” and “Path”) are fulfilled, click on |image9| button to
validate your new account, which will be automatically added in the
list of existing accounts. If you click on |image10| or |image11|
button, you go back to the first dialog, as presented in, and
nothing is done.
\ *Deleting an existing Account*
--------------------------------
To delete an existing account, first select the account in the
account Selection Combo Box, as following:
|image12|
Figure 4: Account selection
When the account is selected, click on |image13| button to delete
it. If you do it, you won’t be able to use this account any more
(and no other user either), because the account is definitely
removed from list. The account deletion doesn’t involve the
corresponding directory (neither its content) deletion.
If you want to see your account path, you can check “Show account
path”.
|image14|
Figure :Show account path
\ *Launching application with an existing account*
--------------------------------------------------
To launch application with an existing account, first select the
account in the account Selection Combo Box, as presented in *Figure
4: Account selection*.
Then, click on |image15| button, and you will reach the application
main panel configured with this account (the account name is
displayed in frame title).
\ **
**
\ *Control archiving*
=====================
This section deals with controlling archiving of Tango attributes
through **Archiving Configurations** (henceforth **AC**).
An AC describes which attributes to archive and how, and consists
of:
- General information (when the AC was created …).
- A list of attributes to archive.
- For each attribute, a set of HDB/TDB archiving modes.
ACs is accessed/used in the AC panel:
|image16|
Figure 6: The AC panel
**
**
\ *Creating/modifying an AC*
----------------------------
The creation or modification of an AC is done the same way, using
the New/Modify button respectively. We will see how to load an AC
later.
*Step 1: AC general properties*
- Click the New/Modify button in the AC actions panel
- The following dialog appears
|image17|
Figure : Step1, general properties
- You can choose a name for the AC. This field isn’t mandatory but it
is recommended to fill it, to better identify your different ACs
later.
- The creation and update dates are filled or modified automatically
upon saving an AC. Click next
*Step 2: Select the AC attributes*
There are 2 ways to select the AC attributes. The user can choose a
selection method in the Options.
*Step 2, method 1:*
|image18|
Figure 8: Step 2, select AC attributes (standard method)
- The left tree lists the Tango attributes. The right tree represents
the current attributes of the edited AC. Both trees have the same
structure of TANGO\_HOST/Domains/Families/Members/Attributes.
*WARNING* The left tree listing the Tango attributes is initially
only loaded up to Members level to avoid overloading. The attributes
are loaded upon user selection of a Member (device) node.
- Adding attributes to the current AC:
- Select a tree node to expand it.
- Select attributes in the left tree then press the right arrow to
add them to the current AC.
- Select a node in the left tree then press the right arrow to add
all attributes under this node to the current AC (only works
if those attributes were loaded).
- Removing attributes from the current AC:
- Select attributes in the right tree then press the red X to remove
them from the current AC.
- Select a node in the right tree then press the red X to remove all
attributes under this node from the current AC.
- Using “Match” to filter attributes:
The user can enter an expression of the form D/F/M and click match
to filter attributes in the left and right trees.
D represents the Domains; F represents the Families, and M the
Members. All trees can contain the joker character ‘\*’.
Since the tree loading is initially only up to Member level, it’s
not possible to filter up to Attributes level.
*Step 2, method 2:*
|image19|
Figure 9: Step 2, select AC attributes (alternate method)
- Attribute selection and automatic attributes adding:
- Choose a Domain. This refreshes the list of possible Device
classes for this Domain.
- Choose a Device class. This refreshes the list of possible
Attributes for this Domain and Device class.
- Choose an Attribute and press Add attribute:
- All Attributes
- with the selected name
***AND***
- belonging to any Device of the selected Class and Domain are added to
the current AC’s list of attributes.
All new attributes are red until the AC is saved.
- Line level sub-selection of loaded attributes:
Each attribute is initially checked, but this check can be removed
by the user. When the user clicks on next, all unchecked attributes
will be removed from the current AC.
- Click “Select All” to select all lines.
- Click “Select None” to select no line.
- Select lines in the list (CTRL and SHIFT are usable), then click
“Reverse for selected lines” to reverse the checked/unchecked
status of all selected lines.
*Step 3: Set the AC attributes properties*
|image20|
Figure 10: Step 3, selecting archiving modes
- A general description of the properties setting process:
The way you set up archiving modes for each attribute is as follows:
- Select a group of attributes.
- Edit HDB/TDB modes.
- Call “Set” for the current group of attributes: the currently
displayed modes are applied to all attributes of the selection.
- Repeat with next group of attributes.
- End edition by clicking “Finish”.
- Attributes selection
The setting up of archiving modes can be “factorized” for a
selection of attributes. All attributes of the selection will be set
up with the currently displayed properties when the user presses
“Set”.
The multiple selections can consist of:
- A manual select at Attributes level (CTRL and SHIFT are usable).
- Selection of an upper node level: all Attributes nodes under this
node will be set up.
- A combination of the two.
- Unset attributes and default values
Attributes which haven’t received any Mode yet (unset) are displayed
in *Italic*. Attributes which have (set) are displayed in **Bold. **
Clicking on a set attribute displays its archiving modes.
Clicking on an unset attribute displays default archiving modes.
- Controls upon AC validation.
The user can not choose any and all combination of modes, nor any
and all numeric values for each mode. Thus, controls are performed
upon call to “Finish”:
- If any HDB (resp. TDB) mode is chosen for a given attribute, it must
also have the basic HDB (resp. TDB) Periodic mode.
- Any unset attribute will be removed from the AC; the user is prompted
to continue editing the AC, or ignore them.
- Numeric values are controlled for each mode.
When the validation is over, the AC is displayed in the
application’s AC panel.
\ *
*
\ *The opened ACs menu*
-----------------------
Mambo can have several opened ACs at once, even if only one is
displayed on screen at a time. A drop-down menu allows the user to
choose an AC in the list of opened ACs:
- Each time the user loads an AC, it’s added to the top of the opened
ACs list (the older ACs are shifted downwards in the opened ACs
list)
- The list identifies ACs by their name and date of last update. When
the user selects an AC, it becomes the current AC, and its
general information and attributes are displayed.
- To remove an AC from the list, push the red X button (this will do
nothing if the list is empty or only has 1 element). The next AC
in the reduced list (i.e. the one that was added to the list the
most recently) is automatically displayed.
- The list can hold no more than *[MAX\_NUMBER]* ACs, this number can
be defined in the AC tab of the options panel (default=5). If the
list’s length reaches *MAX\_NUMBER,* the oldest AC will be
removed from the list when needed.
- ACs that have unsaved modifications are identified by a red star.
If Mambo has the “History save” option turned on, the list of opened
ACs will be saved at shutdown, and loaded at startup.
|image21|
Figure 11: Acs menu
\ *
*
1. .. rubric:: *Starting/Stopping archiving on an AC*
:name: startingstopping-archiving-on-an-ac
1. .. rubric:: *The Current Archiving Configuration detail panel*
:name: the-current-archiving-configuration-detail-panel
Attributes are displayed differently in selection trees, with
respect to their current archiving status. The display shows their
current status in DB, not their archiving modes in the current AC.
- Attributes which aren’t being archived are displayed as off bulbs:
|image22|
- Attributes which are being archived only in HDB are displayed as on,
yellow bulbs: |image23|
- Attributes which are being archived only in TDB are displayed as on,
brown bulbs: |image24|
- Attributes which are being archived in HDB and TDB are displayed as
on, bicolor bulbs:\ |image25|
1. .. rubric:: \ *Starting/Stopping archiving on an AC*
:name: startingstopping-archiving-on-an-ac-1
*Starting archiving*:
- Create/Load an AC or just use the current AC. The AC that will be
used is the one displayed in the application’s AC panel.
- Call Start to start archiving each attribute by all its modes.
*Stopping archiving: *
- Create/Load an AC or just use the current AC. The AC that will be
used is the one displayed in the application’s AC panel.
- Call Stop to stop archiving of each attribute. All archiving modes
will be stopped.
In both cases, a success/failure message confirms the action.
\ **
**
1. .. rubric:: *Displaying an AC*
:name: displaying-an-ac
1. .. rubric:: *The Current Archiving Configuration detail panel*
:name: the-current-archiving-configuration-detail-panel-1
|image26|
Figure 12: Detail of the current AC
This panel represents the current Archiving Configuration.
On the left, a tree lists all of the AC’s attributes.
When the user selects a given attribute on this tree, its HDB and
TDB modes are displayed on the right sub-panel.
This displays the attributes modes individually. To get a global
view of the AC’s Archiving Modes, use the “Archiving assessment”
command.
*The Archiving assessment window*
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|image27|
Figure 13: Global view of all the modes of an AC
This window sums up the current Archiving Configuration in two tabs
(one for HDB, one for TDB).
For each attribute contained in the current AC, its archiving modes
are detailed, and if the attribute is being archived, can be
compared to the modes values found in HDB (resp. TDB).
1. .. rubric:: \ *Saving/Loading an AC*
:name: savingloading-an-ac
1. .. rubric:: *Saving an individual AC*
:name: saving-an-individual-ac
Archiving Configurations are saved /loaded as XML files, with the
.ac file extension.
In the menu, select “ACs/Save” or “File/Save/Archiving
configuration”:
Saved operations work like they do with Word (for example):
- The first time a file is saved, the user is prompted to choose a path
and file name. Initially the file chooser dialog is in the “ac”
subdirectory of the Mambo working directory. The “.ac” file
extension is automatically added if the user doesn’t.
- If a file was already saved, it will automatically be saved in the
same file the next time the “Save” menu is selected.
- The user can still specify a different file, by using the “ACs /Save
as” menu (or “File/Save As/Archiving configuration”).
When an AC is loaded, it becomes the current Archiving Configuration
and it is added to the list of opened ACs.
In both cases, a success/failure message confirms the action in the
log panel.
*Saving all opened ACs*
~~~~~~~~~~~~~~~~~~~~~~~
It is possible to save all opened ACs. Only modified ACs will be
saved (i.e. the ACs that has a “red star”).
In the menu, select “ACs/Save All”:
For each modified AC, the save operation will follow the same rules
as an individual save:
- If the file has already been saved before, it will be saved silently.
- Otherwise, the user will be prompted to choose a directory and file.
In this case, the ACs that are being saved are successively selected
before each file chooser prompt (so that the user knows which AC
he’s choosing a path for).
The generic “Save All” menu item in “File/ Save All” does this and
the same thing for opened VCs.
\ *Transfer to VC*
------------------
This functionality is used to quickly create a VC on the same
attributes as a given AC (for example, when the user wants to
monitor the values of attributes after starting archiving on an AC).
It will create a VC automatically, with the following properties:
- Its attributes list is the same as the AC the “Transfer to VC”
functionality is used on
- The attributes values are all extracted from HDB, even if some of the
AC’s attributes were only archived in TDB (obviously, the display
for such an attribute will be empty).
- The date range of a one-hour range ends when the VC is created
- Every Attribute has an automatically determined color (if there are
more attributes than colors to choose from, different attributes
will have the same color).
\ **
**
*Exploit archived data*
=======================
This section deals with controlling exploitation of archived
attributes (HDB/TDB) through **View Configurations** (henceforth
**VC**).
A VC describes which attributes to display and how, and consists of:
- General information (when the VC was created, the date range to
extract …).
- A list of attributes to display.
- For each attribute, a set of display properties.
The archived attributes of a VC either all come from HDB or all come
from TDB, since it wouldn’t make sense to display HDB and TDB
attributes in a common plot,
VCs are accessed and used in the VC panel:
|image28|
Figure 14: The VC panel
\ **
**
*Creating/modifying a VC*
-------------------------
Creation or modification of a VC is done the same way, using the
New/Modify button respectively. We will see how to load a VC later.
*Step 1: VC general properties*
Those properties don’t depend on a specific attribute. They are
common to all VC attributes or describe the VC.
Click the New/Modify button in the VC actions panel, the following
dialog appears:
|image29|
Figure 15: Step 1, general properties
*Step 1.1: VC properties*
- You can choose a name for the VC. This field isn’t mandatory but it
is recommended to fill it.
- The creation and update dates are filled automatically upon saving
the VC.
- The user must define a date *range* (Start/End dates\ *)* to extract
data from. This can be done either manually, or by selecting a “Since
xxx” item in the “Date range” drop-down menu.
In the latter case, the user can check the “Dynamic date range”.
What this option does is recalculate the Start/End dates at each
edition or refreshing the VC (see 6.3 *Displaying a VC*).
Example: At 09:00 the user chose “Last 1 hour” as the “since
option”.
The date range will be [08:00-09:00].
If the VC is then edited at 11:00, and “Dynamic date range” was
checked, the date range will be [10:00-11:00]; otherwise it will
still be [08:00-09:00].
- If the “Historic” checkbox is checked, VC attributes will be chosen
among HDB attributes (otherwise, TDB).
- If the “History” checkbox is not checked, you are in TDB mode so you
can import long term snapshot. In this case you can’t modify start
and end date because the snapshot configures it himself.
*Step 1.2: General chart properties*
- The user can define global chart properties (title, background …).
|image30|
Figure 16: Step 1, general chart properties
*Step 1.3: Y1 axis properties*
|image31|
Figure 17: Step 1, Y1 axis properties
- The user can define the left vertical axis properties (title, scale,
…).
*Step 1.4: Y2 axis properties*
|image32|
Figure : Step 1, Y2 axis properties
- The user can define the right vertical axis properties (title, scale,
…).
*Step 2: Select the VC attributes*
The attributes selection works the same way as an AC attributes
selection, except for two differences:
- The only available selection mechanism is the tree selection
The trees are initially loaded to the attributes level.
|image33|
Figure : Step 2, selecting attributes
- The left tree lists the HDB (resp. TDB) attributes. The right tree
represents the current attributes of the edited VC. Both trees have
the same structure of HDB (resp.
TDB)/Domains/Families/Members/Attributes.
*WARNING* Unlike AC trees, VC trees are initially loaded to the
Attributes level since archived attributes are a small subset of all
Tango attributes.
- Consequently, the match functionality works up to attributes names:
one can use a D/F/M/A criterion.
*Step 3: Set the VC attributes properties*
- General flow
To set the VC attributes, user can refer to the ACs, it’s the same
process.
|image34|
Figure 20: Set the vc attributes
*Step 4: Controls upon VC validation *
- Any unset attribute will be removed from the VC; the user is prompted
to continue editing the VC, or ignore them.
- The VC’s date range is controlled
When the validation is over, the VC is displayed in the application’s VC
panel.
*The opened VCs menu*
---------------------
The VCs menu opens in the same way as the ACs menu.
See 5.2 *The opened ACs menu*
\ *
*
*Displaying a VC*
-----------------
|image35|
Figure 21: The current VC panel
This panel represents the current View Configuration; a tree lists
all the VC’s attributes.
To view specific parameters, the user must use the “Modify” button.
Thanks to the docking, users can see two generals information.
|image36|
Figure 22: Extraction of Number and Boolean Scalars
This panel shows the attribute’s extractions.
If the user wants to extract attributes, he must select his time
range then press to the button refresh\ |image37|.
If he wants to stop the refreshing he will press to the button
cancel\ |image38|.
|image39|
Figure 23: Extraction of String and State Scalars
This panel gives Extraction of the string and state scalars.
|image40|
Figure 24: Extraction of Boolean Spectra
This panel shows the results of the Extraction of Boolean spectra.
\ *
*
*Saving/Loading a VC*
---------------------
The user does the same thing as in ACs to save or load VC.
See 5.5 *Saving/Loading an AC*.
\ *Using the Variations functionality*
--------------------------------------
The Variations functionality is a filter which comes between a VC
and the final plot display.
|image41|
Figure 25: The "variations" attributes selection window
The Variations window lists the VC attributes and their “variation”,
which is defined as the difference between the min and max values in
the VC’s date range.
The user can then select attributes which variations that seem
abnormal or interesting, and only plot those attributes.
The Variations window is made of two different tables:
- The first one shows for every attribute its minimum and maximum
values, and its variation.
- The second one gives every attribute and its balanced variation.
Select lines in the left table, and press “View Selected Attributes”
to display the filtered plot.
|image42|
Figure 26: The View selected attributes
\ *Options*
===========
Mambo manages global options. Those options are saved on application
shutdown, and loaded on startup.
The Options menu is located in the Menu bar: ToolsOptions.
\ *Application’s history save/load options*
-------------------------------------------
These options define whether Mambo has a history, i.e. a persistent
state when closed/reopened.
If “Yes” is checked, a XML History file will be saved in Mambo’s
workspace, and on next start up the current AC and VC will be
loaded.
|image43|
Figure : The history options
\ **
**
*AC options*
------------
Options for all Archiving Configurations, the user can define:
- An attribute selection mechanism for AC edition (see 5 *Control
archiving*).
- Default modes selection and values for HDB and TDB archiving (see 5.1
*Creating/modifying an AC*).
- The selected modes and values will be preset for all unset
attributes.
- The default values can be saved to /loaded from an Archiving
Configurations Defaults file (.acd extension).
- The “Restore defaults” button reloads the defaults with non
user-modifiable predefined values.
- The size of the “AC stack”, that is the maximum number of opened ACs.
|image44|
Figure : The AC options
\
*VC options*
------------