Michael Aivaliotis Posted August 30, 2006 Report Share Posted August 30, 2006 Original Post: http://forums.ni.com/ni/board/message?boar...ssage.id=200378 I was trying to make a bit of code in 7.1, win2k do the following: If an index is contained in a row of a 2D array of integers, output all of the integers for that row, otherwise, just output that index. My somewhat convoluted VI to do so is attached. Now, am I overthinking this (which I've been known to do ), or is it actually taking a modification of the row downstream and modifying the input array? I checked this on an 8.20 eval, win xp machine with the same results. Thanks, Joe Z. Reported: # 40DAF67U Download File:post-2-1156914149.vi Quote Link to comment
LAVA 1.0 Content Posted September 4, 2006 Report Share Posted September 4, 2006 Original Post:http://forums.ni.com/ni/board/message?boar...ssage.id=200378 Reported: # 40DAF67U This is really weird.... Can I trust my LabVIEW to compute correctly after bugs like this and the constant loop bug? Quote Link to comment
Wolfram Posted September 6, 2006 Report Share Posted September 6, 2006 This is really weird.... Can I trust my LabVIEW to compute correctly after bugs like this and the constant loop bug? Strange thing like the "For Loop" bug in 7.1. I guess, we can expect LV 8.2.1 I also found out the same behaviour in LV 7.1.1 and 8.0.1 Wolfram Quote Link to comment
Jacemdom Posted September 6, 2006 Report Share Posted September 6, 2006 :headbang: :!: Quote Link to comment
LAVA 1.0 Content Posted September 6, 2006 Report Share Posted September 6, 2006 :headbang: :!: These kind of bugs normally indicate that the software architecture is too complicated and not modular, and the bugs arise from the fact that new functionality is added to an environment where it doesn't fit to the architecture. :thumbdown: Quote Link to comment
Gepponline Posted September 7, 2006 Report Share Posted September 7, 2006 This bug worries me a lot...how can i go on if i can not rely on labview??? So i made some test. The error occur at the indexing in the while loop. If we carry the 2d array into the while loop and extract each element using the index of the cycle no more error occurres. So....there must be an explanation to this thing... I don't like auto indexing in the while loop...i use them only when are useful even to determine the number of cycles of the for loops. Can it be relate to this bug? Three Cycles..same operations... only while loop is wrong... It's not possible such a bug! and.....if the problem is the "+1" module combined with the while loop? If we substitute the "+1" with a sum with an array of 1 the problem don't occur. Download File:post-1899-1157618194.vi Quote Link to comment
LAVA 1.0 Content Posted September 7, 2006 Report Share Posted September 7, 2006 and.....if the problem is the "+1" module combined with the while loop? The error occurs also with '-x' so I suspect it occurs with all 'in-place' operations which do not create a new buffer but modify present buffer. Quote Link to comment
daal Posted September 11, 2006 Report Share Posted September 11, 2006 Hi, I found that if you enable the Show folding feature the error don't occur anymore :thumbup: Dany Download File:post-223-1157980624.vi Quote Link to comment
Grampa_of_Oliva_n_Eden Posted September 11, 2006 Report Share Posted September 11, 2006 Hi, I found that if you enable the Show folding feature the error don't occur anymore :thumbup: Dany Download File:post-223-1157980624.vi Yikes! Talk about being on the horns of a dilema! Since I generally do not auto-index While Loops I'll leeve the "Show Constant folding" off and try to remember not to auto-index on while loops. Ben Quote Link to comment
Gepponline Posted September 11, 2006 Report Share Posted September 11, 2006 yes but.... in LbVIEW 7.1 there is no "show folding" options...... :headbang: :headbang: Quote Link to comment
LAVA 1.0 Content Posted September 11, 2006 Report Share Posted September 11, 2006 Hi, I found that if you enable the Show folding feature the error don't occur anymore What the F... ? How can visualization option have anything to do with how LabVIEW generates code? Is there a name collision, on bug collides with another and both desappear... :headbang: :beer: Quote Link to comment
Craig Smith Posted September 11, 2006 Report Share Posted September 11, 2006 Original Post:http://forums.ni.com/ni/board/message?boar...ssage.id=200378 Reported: # 40DAF67U This is indeed a bug in LabVIEW's inplaceness algorithm, the result of an overzealous optimization, having to do with using auto-indexing input tunnels on a While Loop inside another loop. It is slated to be fixed in the next maintenance release. Craig Smith LabVIEW R&D National Instruments Quote Link to comment
jaegen Posted September 15, 2006 Report Share Posted September 15, 2006 This is indeed a bug in LabVIEW's inplaceness algorithm, the result of an overzealous optimization, having to do with using auto-indexing input tunnels on a While Loop inside another loop. It is slated to be fixed in the next maintenance release.Craig Smith LabVIEW R&D National Instruments Well, I guess now we know we're going to see 8.2.1 before 8.3 or 9.0 Jaegen Quote Link to comment
Bob Y. Posted September 15, 2006 Report Share Posted September 15, 2006 Well, I guess now we know we're going to see 8.2.1 before 8.3 or 9.0 Jaegen :!: Yes, but we will have to wait a year until LabVIEW is 21 years old to see LabVIEW 8.21 Quote Link to comment
jaegen Posted September 19, 2006 Report Share Posted September 19, 2006 :!: Yes, but we will have to wait a year until LabVIEW is 21 years old to see LabVIEW 8.21 Thank you - that brightened my otherwise rather grey day fighting with upgrading a project to 8.2. It is rapidly becoming counter-productive: See here, and here. Jaegen Quote Link to comment
etrnaly Posted December 20, 2006 Report Share Posted December 20, 2006 Hi, I found that if you enable the Show folding feature the error don't occur anymore :thumbup: Dany Download File:post-223-1157980624.vi Setting the folding option didn't seem to fix that bug. What I did figure out was that putting the index of the for loop into the while loop caused the bug. Quote Link to comment
jzoller Posted April 11, 2007 Report Share Posted April 11, 2007 QUOTE(Michael_Aivaliotis @ Aug 29 2006, 10:02 PM) Original Post:http://forums.ni.com/ni/board/message?boar...ssage.id=200378 Reported: # 40DAF67U Apologies to Michael for interrupting... just updating. Fixed in 8.2.1. http://zone.ni.com/devzone/cda/tut/p/id/5674 Bug # 40DAF67U Joe Z. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.