Error Descriptions

A place for discussing topics that do not fit into the other VGS categories

Error Descriptions

Postby jyoung » Mon Mar 23, 2009 4:48 pm

Is there a document that contins a decription of the errors listed when t-vec builds a project. I received the follow error and I don't know where to look to debug it other than posting here. I imagine these error messgaes are suppoed to help you identify where in the model there is a potential issue. I can not provide you with thsi model, but I can give you any additional information you need.

The error is listed twice, once for upper and once for lower bound test


"No Utility FCP Is Compatible With Main System Constraints At Utility Ground Level"


Also here is


Loading project D:\Documents and Settings\jyoung\My Documents\jyoung\tvec_LDRA\Test Folder\Test_temp\corrector_tvec_temp.prj...
Check_for_Comverged__Guidance_Solution
corrector_tvec_temp_root
__coreRTS
__runTimeData
Done.
Validating import list...
Done.
Checking project options...Done
Expanding inheritance structures...Done
Setting up build tasks...Done
Attempting to checkout Core license...Done
Initiating Build.
Compiling Subsystem : __coreRTS...Done.
Compiling Subsystem : __runTimeData...Done.
Compiling Subsystem : Check_for_Comverged__Guidance_Solution...Done.
Generating Vectors : Check_for_Comverged__Guidance_Solution...Done.
Analyzing Coverage : Check_for_Comverged__Guidance_Solution...Done.
Saving Vectors as HTML : Check_for_Comverged__Guidance_Solution...Done.
Saving Vectors as XML : Check_for_Comverged__Guidance_Solution...Done.
Compiling Subsystem : corrector_tvec_temp_root...Done.
Generating Vectors : corrector_tvec_temp_root...
ERROR : VG0013 in DCP 1 @ UA -> 2171143 :
No LOW BOUND vector solution was found for
Subsystem -> corrector_tvec_temp_root DCP -> 1 (MS 1)
Using SPEC_SEQUENTIAL Constrained Object binding heuristic.
Error # 1 in Error Report File.


ERROR : VG0013 in DCP 1 @ UA -> 4323640 :
No HIGH BOUND vector solution was found for
Subsystem -> corrector_tvec_temp_root DCP -> 1 (MS 1)
Using SPEC_SEQUENTIAL Constrained Object binding heuristic.
Error # 2 in Error Report File.

Done.
Analyzing Coverage : corrector_tvec_temp_root...
ERROR:3206 (User) Uncovered Domain Convergence Path #1 <corrector_tvec_temp_root, corrector_tvec_temp_root_FR__1, cv_corrector_tvec_temp_root_RP__1, corrector_tvec_temp_root_RP__1, corrector_tvec_temp_root_RP__0, RP1>

ERROR:3205 (User) Uncovered Predicate <corrector_tvec_temp_root_RP__0>

ERROR:3205 (User) Uncovered Predicate <corrector_tvec_temp_root_RP__1>

ERROR:3205 (User) Uncovered Predicate <cv_corrector_tvec_temp_root_RP__1>

ERROR:3205 (User) Uncovered Predicate <corrector_tvec_temp_root_FR__1>

ERROR:3205 (User) Uncovered Predicate <corrector_tvec_temp_root>

ERROR:3205 (User) Uncovered Predicate <RP1>
Done.
Saving Vectors as HTML : corrector_tvec_temp_root...Done.
Saving Vectors as XML : corrector_tvec_temp_root...Done.
Build Complete.
jyoung
 
Posts: 33
Joined: Wed Mar 18, 2009 2:25 pm

Re: Error Descriptions

Postby busser » Tue Mar 24, 2009 10:40 am

Analysis of the diagnostic information in the error reports is a rather difficult task to write about, especially outside the context of the model/example that a given diagnostic message is associated with. This is one reason that best information about interpreting this information comes from training class material and instruction. I'll try to provide some general information about the class of error message you are referring to. But there are probably many concepts that you may not be clear about, due to lack of hands on training

"No Utility FCP Is Compatible With Main System Constraints At Utility Ground Level"

In generally, T-VEC project subsystem hierarchy/architecture reflects the model's atomic function hierarchy when using a Simulink model as source or TTM table hierarchy when using T-VEC Tabular Modeler as source. When generating test vectors for subsystem A, any lower level subsystem is often referred to as a utility subsystem or child subsystem to the parent subsystem A.

For a give subsystem, the individual discrete logical dependency paths in the subsystem are called DCP paths. DCP stands for Domain Convergence Path. These are the foundations of logic coverage for a given subsystem and each DCP is the focus of a test vector generation run. When a given subsystem refers to lower level subsystems, the logic of the currently focused upon DCP path of the parent is applied first to determine the proper subdomain of the input space that satisfies that DCP of the parent. Once this input subdomain is established, the lower level subsystems are added to the logical domain convergence processing, with the goal of finding any one logical path through the DCP paths of the children subsystems that is consistent with the DCP input subdomain established for the parent's DCP. The combined DCP path of the parent subsystem and all of the DCP paths in the children dependency hierarchy is referred to as an FCP path - Full Convergence Path.

The DCP/FCP concept is the foundation of T-VEC's partitioning of the logical tree through an entire system such that complete logical coverage can be attained, without expanding the logic tree exponentially to astronomical proportions. The logic of every subsystem is individually focused on for generating a test vector to cover it, while treating all lower level subsystems as atomic elements with respect to the parent. If test vectors are produced for all subsystems up through the hierarchy, all of the logical paths/decisions will be covered by test vectors.

The error message ""No Utility FCP Is Compatible With Main System Constraints At Utility Ground Level" basically means that for the currently focused upon parent DCP constraints, there was no path through the lower level subsystem references that was found to be consistent with the constraints of the parent's DCP. Check out this training class slide

no_fcp_path.jpg
no_fcp_path.jpg (568.25 KiB) Viewed 5749 times


You should be able to see that even though it is possible to conceive of a test vector for just the logic of the parent SubsystemA, SubsystemA's dependency on its lower level children is such that there is no possible set of x and y values that will establish a usable test vector. This points out the inconsistency in logic across multiple levels of a subsystem hierarchy, something unit testing or manual inspection can often not find.

The rest of the information in the error diagnostics you are looking at attempts to provide some location and domain value context at the time the inconsistency was detected.

I hope this explanation is of help to you. In order to provide any more details, we would need to see the model and the t-vec project files.
busser
Site Admin
 
Posts: 52
Joined: Thu Mar 13, 2008 7:42 pm


Return to General Topics

Who is online

Users browsing this forum: No registered users and 1 guest

cron