Graph annotation bug ??

Hi,
I have encounter the annotation error on graph again. And this time, I have upgraded my LabVIEW to version 8.6.
Some of the points is perfect, but some of the points, pointing to the correct x-coordinate but the label seem gone far away.
Here I attached the screenshot, and the VI.
Thanks for your time. Any idea or comment please leave here. Thanks again.
Message Edited by engwei on 01-21-2009 02:42 AM
Attachments:
graphCrazy.vi ‏43 KB
graphcrazy.JPG ‏83 KB

Yes, expression evaluation can cause these behaviors and the script uses them extensively. Nothing wrong in that regard. The rest is unclear because you made your screenshots useless by clipping out the important info like the property names. Also full system info,exact graph editor options and all that will be required.
Mylenium

Similar Messages

Graph Annotations - Major Bug !!!!!

I am using annotations on a NiGraph control(2D, single plot chart). I update the X and Y coordinates of specific annotations using m_Graph.Annotations.Item(item).Caption.SetCoordinates(... , ...)
this is done around 3 times per second. Each call to SetCordinates(...,...) causes a memory leak!!! Over a period of time my application uses up all system memory. I have validated this bug by running the National Instruments Annotations example and pressing the 'Generate Waveform' button whilst monitoring the memory usage using NT's Task Manager. Your example also leaks memory each time the annotations are repositioned !!!. Each time my graph is scaled X or Y (I use a slide control for this purpose) I reposition all annotations so they
fit nicely in the view port of the graph. This operation generates many calls to the m_Graph.Annotations.Item(item).Caption....etc) and subsequently leaks memory at a vast rate. Graph annotation are the cornerstone of my application and I am very concearned that due to this bug my application is unusable.
I would appreciate any help on this matter.
Shaun

I must disagree with your answer. I feel that the discussion forum the ideal place to warn engineers around the world of the problems with your software. This posting could save developers such as myself from developing a, at present, useless (and expensive) application. I did indeed request support and reported this bug to National Instruments (UK). Unfortunately they had no knowledge of it and could not help me any further but thanked me for pointing it out and advised me to “Watch the website for future Measurement Studio Updates”. As the Product Support Engineer for Measurement Studio and LabWindows/CVI I feel you answer was far from helpful, only pointing out this bug has been verified. Information such as possible work arounds, new
version release dates or patches would have been useful. Perhaps even helpfully passing my details to one of your Technical Engineers so we might arrive at a solution. I would have rated the answer 0.5 stars but there was no icon to click.

Change Font and Size of Graph Annotations

Just learned a cool little trick from Christina Rogers about how to change the font and size of a graph annotation after I left a comment on her blog (if you are unsure how to create a graph annotation, check LabVIEW Help).
With the Cursor Legend selected, use the Font Dropdown on the toolbar to select the font you want for the annotation. Apparently, annotation and cursor text on the graph inherit the font of the Cursor Legend. If you do not like how the Cursor Legend looks after you have changed the font, you can make it invisible again (I have never shown the cursor legend in final UI products... and I have never used "Hobo Std" in final UI products...).
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Here are two Ideas you may be interested in if you're looking at this thread:
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Customized-Fonts-for-Graph-Annotation/idi-p/1073784#M4...
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-Line-Width-and-Line-Style-to-Cursor-List-Property/...
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Graph Annotation Fonts

I have several annotations that I am adding to a graph. I would like to align their left side. Annotation text is center justified. Is there a way to set the justification? If not, I can calculate the number of characters and pad the back end with spaces to bump the left side out. But so far, I haven't gotten this to work either because the font is not a fixed width font. What font setting do the annotations use? In other words, I am willing to change the fonts of other things in order to also change the font of the graph annotation, but I kind of need to know which other font to change.
Thanks,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]
Solved!
Go to Solution.

Here is the VI that I created to do padding. It should make the separator be in the middle of the name (where the position is).
Message Edited by Bob Y. on 03-11-2009 10:45 AM
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]
Attachments:
Align Annotation Image.GIF ‏25 KB
Align Annotations.vi ‏13 KB

Re-creating graph annotations in diadem?

Hi,
I am currently going through the demo version of diadem, and am impressed with it's reporting capabilities. I have an application where I am automatically placing graph annotations during my test, then when I save the .tdms, I store the annotation information (index, name etc) in groups named "annotation01", "annotation02" etc, to the tdms file. Currently, I have a separate labview utility in which I load the tdms file, and place the annotations back in the graph, so I can post process the data and see the annotations. It seems that if diadem can display text over graphs when viewing the data, I may be able to make a script to place these annotations using diadem. Is diadem capable of this?
Thanks
David J.

Hi David,
Sorry, I got lost in all those "AnnotationArrayElement" Groups. You're right, your first Group has two data channels, and I can also graph those in DIAdem. But all your label information is stuck in Group properties, and this is the information I was referring to that should be written to Channels with the "TDMS Write.vi". I've written a DIAdem VBScript to reorganize your TDMS file into the structure I think is ideal for your data and am attaching a representative TDM/TDX file as well as a picture of what the labeling could look like.
One problem I ran into when doing this was that I didn't find the label texts. Your first attached image above showed text event labels on the LabVIEW graph, but I don't see these texts anywhere in the TDMS file. So what I did instead was to pretend that the "Index1" property was the text label to display. Also, you have 2 separate XY coordinates in each "AnnotationArrayElement" Group, I just randomly picked the "Position" properties instead of the "Label_Offset" properties. Why are there 2 sets of XY coordinates as well as the value index (triple redundancy?), and how should that information be translated into the desired XY coordinate to display the event marker or label?
Finally, you have several Groups that just contain set up properties-- I'd strongly recommend you fold all those properties into the same data Group that has your measured data arrays-- that will make for much better DataFinder querying down the road. I also found a "Sample_Rate_Hz" property in one of the Groups, so I used that to turn your "Battery Current" and "Phone Voltage" channels into waveform channels in DIAdem, and I added unit assignments of "mA" and "V" respectively. But if they were waveform channels in LabVIEW you should have just wired the waveform up to the TDMS Write.vi and they would have loaded into DIAdem as waveforms automatically. As a result, I scaled the "PostionX" property from X value to Time value.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
Attachments:
david_jenkinson New.zip ‏2676 KB
Event Labels.pdf ‏69 KB

[svn] 3738: merging fix for LCDS-329 to trunk (XML graph serialization bug)

Revision: 3738
Author: [email protected]
Date: 2008-10-18 08:47:18 -0700 (Sat, 18 Oct 2008)
Log Message:
merging fix for LCDS-329 to trunk (XML graph serialization bug)
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-329
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Output.java

Graph Editor bug

Hello there, I'm having some problems with the graph editor on After Effects CC 2014. It shows like in the images below, almost as if the software couldn't process the graph, and it slowly starts to get more curved. Also I can't edit or even barely see the anchors, and it shows the curves for all the animated parameters, even though the option "Show selected properties" is enabled. It happened twice so far, and is related to specific comps, I checked on other comps in the same project and they were working just fine. My only guess so far is that it happened in comps where I am using that new script/preset called Ouroboros, but I'm not sure it's related to that, since the bug appeared on other layers without that effect. Any one has any clue or had this problem before?

Yes, expression evaluation can cause these behaviors and the script uses them extensively. Nothing wrong in that regard. The rest is unclear because you made your screenshots useless by clipping out the important info like the property names. Also full system info,exact graph editor options and all that will be required.
Mylenium

Critical graph scale bug in LV2009?

Put a graph or XY plot in LV2009 on Vista - and set the X scale to be in absolute time. If you do this in LV 8.6 you will now see multiple time stamps along the X axis. In LV2009 you will only get the two at each end.
Fill the graph with data...now you may get 1 extra axis point along the X axis...but never more, regardsless of the axis style, - and its position will either be in the middle or at either 25% or 75% of the full time range. (See attached picture of chart and graph).
I know this is not how things behaved before, but is it a bug? Unless I'm overlooking something it is, and it is a show stopper....I hope it's me.
If not, a fix should be sent out immediately.
MTO

In a project as big as LabVIEW bug fixes that involve changing the actual executable as opposed to changing some VI components, either in vi.lib or in one of the frameworks, is not a matter of days but more like several weeks, especially if it is something like this most likely going very deep into the operational handling of LabVIEW. This bug isn't there because of a typo but most likely because of an addition of some other code that now causes this behaviour. And simply changing it to behave as before might turn other features, specific to 2009 but also earlier ones suddenly into running havoc, so it is definitely not like changing some lines of code and then recompiling the entire thing and voila. It basically has to go through the entire regression test suit on all platforms as well as going through some serious interactive tests of many UI aspects by several guys/gals, before they can even consider wrapping everything up into a patch distribution. By that time this is done, the impationetly awaited Service pack fix for 2009 most probably is around the corner anyhow, so it will likely get wrapped into that release.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

3D Graph Color Bug

I am just discovering the new 3D graph objects (LV 2010) and noticed some odd behavior.
If you color the Graph object (not the plots), this cannot be undone (in other words Ctrl-Z does not work).
This is fine since a simple work around is to paint the object back with the original color.
I think it qualifies as a bug nonetheless.
However, here is an even more odd thing: if you paint the "ViewPoint" buttons (or whatever they are called), depending on where you click with the brush, you may end up with a square smack in the middle of the button as shown below (bottom right):
The problem is that there does not seem to be a workaround.
Since Ctrl-Z does not work, I tried to paint the square with a transparent color, and a few color combinations, but could not find a way to revert to the original "no square hidding the glyph" situation.
The only fix is to "Revert" to the previous VI status (which is pretty drastic), or delete the Graph object and put a brand new one instead (or replace it by a brand new one), which is barely less drastic.
Is this a known "feature"?
Solved!
Go to Solution.

Hi there, so that behavior is intended but there is a workaround that I was able to find for you. The attached vi lets you color the 3d graph and modify the properties and those properties will stay after you save.
Scott A
SSP Product Manager
National Instruments
Attachments:
Facade_2D_and_3D.vi ‏157 KB

Graphing visualization bug - holes in 3D stacked area graphs

Has anyone seen this bug in the grapher?
http://web.mac.com/iconoplasty/iWeb/Site/other_data/numbers-bug-1.pdf
http://web.mac.com/iconoplasty/iWeb/Site/other_data/numbers-bug-2.pdf
These are both 3D stacked area graphs of similar periodic data from two different time frames. I'm currently working on a spreadsheet that has four of these. These two have the same type of bug in the rendering (note the holes in the graphs), the other two look fine.
3D stacked area graphs that I generate from other tables in the spreadsheet, or even 3D stacked area graphs that I generate from subsets of the two tables that generated these graphs, also look fine. The only time I encounter the error (at the moment) is when I generate 3D stacked area graphs from these two full tables. And it happens for every 3D stacked area graph I generate -- I tried generating a second and third graph with slightly different display attributes, but the error persists for those graphs as well.
Anyone have any insight on this?

Hello
May you pack a sample document in a zip archive
attach it to a mail
and send it to:
koenig PERIOD yvan AT tele2 PERIOD fr
I would be able to check that the behaviour may be reproduced. If it may, I will post a report to Apple.
Send a document with NO confidential datas because it would be necessary to send the document with the report.
Yvan KOENIG (from FRANCE mardi 4 mars 2008 21:11:33)

XY graph cursor position bug

I have reproduced the bug mentioned here:
http://forums.lavag.org/Graph-Cursor-XY-Position-Bug-t1366.html&gopid=40859#entry40859
I've reproduced this bug (?) in Labview 8.5, with an XY graph doing
much the same as Jack. The attached zip file contains a stripped down
version of my program (originally written by my coworker, Andrew
MacDonald). Run "RENA3 Data Viewer.vi" and follow the instructions.
As Jack said, changing Cursor.PosX to Cursor.Index solves the problem.
I did not find this bug mentioned anywhere other than the above link.
Fraser
Attachments:
XY Graph Cursor Bug.zip ‏142 KB

Hi Karla,
Sorry if that wasn't as obvious as I thought! :-) Hopefully the attached image makes it clear. On the front panel, 'Cursor Channel' is inputted. This is directly wired to Histogram.Cursor.PosX. Immediately following, Histogram.Cursor.PosX is read and wired to the front panel indicator 'Cursor.Cursor Position:Cursor X'. There is always a difference of 15 or 16 between the two values. If there was no bug, these two values should be identical! I can only conclude that Labview is doing something funny...
As I mentioned before, changing Cursor.PosX to Cursor.Index fixes the problem.
A bit of background: my FWHM function outputs the peak channel, and the cursor is supposed to go through the peak so you can have a visual check that it is analyzing the right peak. I noticed that the line would never go through the peak; the line would always have an offset. After wasting a couple of hours, it became clear that I was wiring the correct value into 'Cursor.PosX', but something was going wrong beyond that.
Cheers,
Fraser
Message Edited by fjharris on 01-25-2008 11:34 AM
Message Edited by fjharris on 01-25-2008 11:36 AM
Attachments:
Labview Bug.png ‏27 KB

LabVIEW 8.6.1 did not fix glaring Mixed Signal Graph bug :(

I'm pretty dissapointed that NI has JUST NOW released 8.6.1 (more than 6-months after releasing the buggiest LabVIEW version, ever). The Mixed Signal Graph bug still exists and is very annoying. The visual bug occures when you add more than 1 plot on a mixed signal graph and then try to resize the legend. The Y-Axis labels do not move appropriatly. You really can't resize the legend with this bug.
Where can I find a list of known bugs in LabVIEW and verify that this is in that list? How can I add weight to this bug report so that NI will address it for the LabVIEW release? How can I express to NI that I don't want LabVIEW 9 until they can fix all the problems in v8?

LV_Pro wrote:
One way might be to get in on the LabVIEW 2009 Beta, see if it fixes the problem, if not, report it while there may still be time to fix it.
Not sure about the "buggiest version", v2.5 had its share. Had to save your work every 1/2 hr. or risk loosing everything when you got the almost guaranteed "insane error" which always seemed to occure when you had done the most editing since your last save.
Message Edited by LV_Pro on 02-10-2009 09:07 PM
The OP obviously never had to work withLabVIEW versions prior to 5.1.
And while 8.6 had a few nagging bugs including visual ones it is actually quite stable and good. No comparison with 8.0 for instance or even 8.0.1
Nickerbocker wrote:
I'm pretty dissapointed that NI
has JUST NOW released 8.6.1 (more than 6-months after releasing the
buggiest LabVIEW version, ever). The Mixed Signal Graph bug still
exists and is very annoying. The visual bug occures when you add more
than 1 plot on a mixed signal graph and then try to resize the legend.
The Y-Axis labels do not move appropriatly. You really can't resize
the legend with this bug.
Where can I find a list of
known bugs in LabVIEW and verify that this is in that list? How can I
add weight to this bug report so that NI will address it for the
LabVIEW release? How can I express to NI that I don't want LabVIEW 9
until they can fix all the problems in v8?
You just did! But unless you are a site with several 1000 LabVIEW licenses you will not outweigth those other customers who do have that many licenses and do want more features as soon as possible rather than an annoying graph display bug getting fixed.
Rolf Kalbermatter
Message Edited by rolfk on 02-11-2009 10:02 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Xy Graph Auto Scale Bug - Need AutoScale VI

I have another bug to report, I have come across more bugs in the past year than before.
This bug is present in all versions since 7.1 to the latest 8.5.
Here is the bug.
Create and Graph.
Make sure the X-Scale is set to Auto Scale.
Go to Properties and Choose "Formatting and Representation" and Choose Relative Time for X-Axis . Select HH:MM.
Click OK
Now Set the scale to say 20 Hours. You Should see 10 Divisions of X-Axis
Right Click on the Graph and Select "Scale Object with Pane"
Maximize the VI now.
The Graph will scale nicely!!
Look at the X- Axis Scale. It is 20 Hours.
What happened to the 10 Divisions? It is one big Division of 20 Hours.!! Why?
Set the Scale to 10 Hours and all the divisions reappear!!
Restore the VI window to Previous and Now All divisions of the scale are gone.
This Behavior is random based on the size of the graph and Screen resolution.
Can someone suggest a VI that does Auto Scaling elegantly
Attached find Pictures of the Phenomenon and VI which exhibits this behavior. Any one to help...
Mache
Good Luck!
Mache
Attachments:
XY Graph 2.jpg ‏370 KB
XY Graph Autoscale bug.vi ‏9 KB
XY Graph 1.jpg ‏116 KB

Here are the additional attachments
Good Luck!
Mache
Attachments:
XY Graph 3.jpg ‏124 KB
XY Graph 4.jpg ‏350 KB

How can I change annotation font and/or size?

I would like to change the font of the graph annotations. I know how to change other parameters of the annotation list, such as color, type, visibility etc. But there seems to be no option to change the font or at least the font size.
Thanks!
Message Edited by Filipp on 01-29-2007 02:33 PM

This is a very old thread, but in case you stumble across this thread wondering how to change annotation or cursor fonts, it is possible.
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Why don't Grapher's Frame Limits work correctly with saved Grapher files using multiple equations on Mountain Lion?

Hi,
I generally enjoy using Grapher in OS X (I am using Mountain Lion v10.8.2). However, I have repeatedly encountered what seems to be broken basic functionality in setting the limits on the display frame (View> Frame Limits…). When opening saved Grapher files with multiple valid equations in them (equations which include constant terms defined as sets of numbers), I repeatedly get the following behavior:
1. Frame limits are not correctly saved. As in, the file opens with a different view than it was saved and closed in.
2. Frame limits no longer work as expected. For example, I might set the Y axis frame limits to be -2 to 2, but the Y axis of the frame display will run from about -1.95 to about -0.35.
3 Performance is degraded. Making a change to the frame limits (for ecxample, changing the Y frame limits to -2.2 and 5 in an attempt to display something approximating the range -2 to 2) take an inordinate amount of both processor time and clock time. The spinning ball appears and hangs out far longer than is welcome, and at times seems to hang requiring a force quit of Grapher.
These problems occur regardless of coordinate system.
Is there a solution? If I create a new file and start from scratch the problems reappear. The problems reappear across a wide range of 2D equation types.
Is Grapher simply broken in this regard?
Thanks for the input.

Bonjour Lexy-Lou,
   You are right, the bug was born with Grapher as you may read on the website
<http://y.barois.free.fr/grapher/> :
Grapher’s bugs and their remedies (OS X in French).
          Bug nr. 1. (Grapher 1.1, 2.0, 2.1, 2.2, 2.3). When modifying the main 2D window size, the graph length and height already formatted (menu Format) are changed : axis scale values stay the same, added objects remain same size on the same places (unit pixel) relative to the graph left upper corner ; but the graph view changes for the ratio H/L do so : very annoying !
                    The remedy : To restore the 2D graph after changing the window size : menu Format > Layout > Size > redo the initial choice (paper size or L and H values)… or avoid having to do so by selecting a window large enough to begin with.
                    Proposed correction : making the graph size independent of the main window’s one.
          Bug nr. 2. (Grapher 1.1, 2.0, 2.1, 2.2, 2.3). Saving is wrong in 2D (menu File > Save, Save as, Save a copy as). Are not seved : the last location on the screen of the main window, the graph size, the maximum and minimum values of the ordinate scale : very very annoying !
                    Note : The new windows of Grapher 1.1 (Grapher secondary window > New Graph > 2D or 3D Graph) always open in the same place on the screen( OS X 10.4.11 configured in French) depending on the language used by Grapher : if it’s English, well placed and covering most of the screen, if it is French, the windows are half length but same height and are located on the right side of the screen. This anomaly disappeared with Grapher 2.0, 2.1, 2.2 (English or French).
                    The remedy : to restore the 2D graph after opening a GCX files (.gcx) : menu Format > Layout > Size > redo the initial choice (Paper size or L and H values) to be done twice ; then menu View > Frame limits... > enter minimum and maximum vaues of the y scale. This requires to note four numerical values, L, H, y-min, y-max, for example at the top of the equation list (or at the bottom : see bug nr. 27).
                    Proposed correction : complete saving in 2D.
For the full list of Grapher's bugs please download "Instructions for Use - Grapher" (English) or "Mode d'emploi de Grapher" (French). Quick glance at the Contents (pages 2 & 3) you'll be surprised by the possibilities of Grapher.app despite the bugs.
Enjoy,
Au revoir,
YB24

Graph annotation bug ??

Similar Messages

Maybe you are looking for