Difference between revisions of "SkibUserMacros:SolveMalfunctions"

From Protoi Healing

Jump to: navigation, search
(Created page with "{{UserMacroMainBox |nameUserMacro = SolveMalfunctions |authorUserMacro = Frank |descrUserMacro = Tries to solve malfunctions. |statusUserMacro = public |termsUserMacro...")
 
Line 42: Line 42:
 
# 'Own actions' are defined as all actions done by the calling macro.
 
# 'Own actions' are defined as all actions done by the calling macro.
 
# 'Counter actions' are defined as all counter actions done in the context of the calling macro.
 
# 'Counter actions' are defined as all counter actions done in the context of the calling macro.
# '''LOOP'''
+
# '''LOOP''' <T:15seconds>
 
## {{Method|Scan}} all context of the calling macro.
 
## {{Method|Scan}} all context of the calling macro.
 
## '''TRY''' to {{Method|identify}} all 'own actions' and all 'counter actions' in all context of the calling macro.
 
## '''TRY''' to {{Method|identify}} all 'own actions' and all 'counter actions' in all context of the calling macro.

Revision as of 14:27, 7 February 2017

Skib User Macro
Name SolveMalfunctions
Author Frank
Brief descr. Tries to solve malfunctions.
Status public
Terms sub-macro only
Resources for the UserMacro
1 10 100
1k 100k 1kk
10kk Gmax Omax
Resources with butterfly option
1 10 100
1k 100k 1kk
10kk Gmax Omax

Command syntax

SolveMalfunctions {Use butterfly}






Description

Whatever the User Macro will do...

{Use butterfly}


Algorithm of User Macro

  1. Use DATABASE 'Malfunction'.
  2. 'Own actions' are defined as all actions done by the calling macro.
  3. 'Counter actions' are defined as all counter actions done in the context of the calling macro.
  4. LOOP <T:15seconds>
    1. Scan all context of the calling macro.
    2. TRY to identify all 'own actions' and all 'counter actions' in all context of the calling macro.
    3. TRY to trace all found 'own actions' and all 'counter actions'.
    4. TRY to identify all 'malfunctions' in all context of the calling macro.
    5. TRY to trace all found 'malfunctions'.
    6. Create an optimal solution for all 'malfunctions'.
    7. Create optimal procedures for the solution.
    8. TRY to apply the solution by using the optimal solution procedures.
    9. IF the former solution or parts of the solution repeatedly failed and the option {Use butterfly} was given, DO:
      1. Use butterfly-method for the solution.
    10. IF-END
    11. TRY to identify the success of the solution and procedure.
    12. Store all successful parts of the solution and the procedure in the 'Malfunction' DATABASE.
  5. LOOP-END