|
Welcome to the COE Discussion Forum!
|
|
|
|
To participate in the discussion forum, you must be logged in to the website. If you forget your login information, please contact COE Headquarters at coe@coe.org or (800) 263-2255.
If you are new to the COE Discussion Forum and would like to participate, please register.
|
|
|
The COE 2008 Fall Industry Workshops
|
| Experience two days of industry-focused education and hands-on training on the Dassault PLM solutions suite of products. All education featured at the workshop is developed by and for users of CATIA®, ENOVIA®, DELMIA® and SIMULIA®. |
| |
|
|
Automotive
Oct. 15-16
Troy, Michigan
|
Aerospace & Defense
Oct. 27-28
Wichita, Kansas
|
 |
|
Register Today!
|
 |
|
 |
| You are not authorized to post a reply.
|
|
| Author |
Messages |
|
COE-Member
 |
| 21 Jun 2005 01:41 PM |
|
Here is my question...
I want to create an annotation note using attribute links in the note. I want the note to look something like this...
Point.1
x = ###
y = ###
z = ###
Point.1 represents the name on the point in the geometrical set
x,y and z ###'s represent the coordinates of that specific point.
Here is my problem. I can not get the "Point.1" to update to a name change.
Here is how I am getting the name...
- Create a string paratemter with a formula.
Example: String.1 = PartBody\Point.1 .Name()
I use something similar for the x,y and z value's
Example: Length.1 = PartBody\Point.1 .coord(x) --- x = 1, y=2, z=3
This updates the parameter and thus the note when a change had been made to the point. But the name does not change (if I were to change it, I would have to force some type of update on it by editing the formula and adding a space somethere in the path to force an update to the parameter and thus updating the note)
Any ideas? I hope I was clear in what I was asking. Basically the name does not update automatically. v5r15ga code was what I was testing this on.
Jason
|
|
|
|
|
CRAIG HELM
|
| 23 Jun 2005 09:38 AM |
|
| You should be able to make a rule that says if that point is updated then update the formula. You might have to put an if statement in with one space in one case and two in the other. And just change it to whatever is not currently the case. |
|
-craig helm
Catia V5 R16 | Windows XP SP2 | Intel P4 3.4GHz | 2GB RAM | ATI FireGL V3100 128 MB DDR |
|
|
BPRASAD
|
| 23 Jun 2005 11:47 AM |
|
1. I tried changing the name of Point.1 by right click on Point.1, Goto Properties and say I rename the Point.1 to Point.6
2. You are right, I did notice any of the Parameters (which result from the Formulas, I had inserted before) were NOT changed at this time.
3. However, if you change any of the X, Y or Z values of the Point.6, the new values are reflected in all the assocaited Parameters (with Formulas) impacted by this change.
My Recommendations:
You insert a User-defined Boolean Parameter say Notes_Update = {true or false }. You also need to WRITE a KWA rule or a REACTION, which activates, when this Boolean Parameter is set to true.
Whenever you require your notes to be updated, you set Notes_Update = true. You have written a KWA rule, in which you have written a rule --> if (Notes_Update = true) X = NewX. This rule (or a similar logic) will automatically change one of the X, Y or Z parameters, thus, forcing a Global UPDATE to be performed on the
Part.
This way you would force an update on the Point Name.
Is this what you wanted?
|
|
Brian Prasad
COE-DPC/KBE Chairperson |
|
|
COE-FORUM-USER
|
| 26 May 2006 06:05 AM |
|
You could use atribute links
ie when u create the annotation right ouse in the text editor select atribute link then select the atribute you wish to see in the annotation
madaxe |
|
|
|
|
JMSWTLK
|
| 26 May 2006 08:16 AM |
|
The core issue here for KBE is something that ought to be covered in a FAQ or an article in the Newsnet.
In short, any of the dynamics embedded within the model (reactions, etc.) will be handled by the event control mechanism (is this concept and how it works well understood within the CATIA v5 KBE community?) in place. This mechanism (or these, I'm not sure) can become lost in all the details that may be pending at any moment (fractional, thereof, as you would expect) especially when there are unexpected interdependencies.
For instance, there may be relationships that go both ways and the necessity of temporal constraints then keep the expected results from occurring. After all, iteration and convergence are numeric processing concerns and not necessarily subsumed in relationship/rule processing.
So, one technique is to impose a procedural oversight which can be problematic; as, in some cases, potential permutations may require a not small set of enumerations which will have to be maintained (this can be costly, hence the appeal of the non-procedural methods).
I think that discussion of this might be part of the KBE Best Practices, as well.
Post Note: A related concept will be ‘pre-condition’ and what is important to an event. Like any assumption that is implicit, pre-conditions can be problematic if left without some attention. How much is required is an open issue from the Dassault tool framework. Then, each of the discipline/application areas needs to address the concern. Again, a topic that ought to be covered in a FAQ and the KBP document.
|
|
john.m.switlik@ieee.org
316-204-0758
http://en.wikipedia.org/wiki/User:JMSwtlk |
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.6
|
|
|
|