07-31-2016 10:55 PM
Continued from the July 2016 bug thread
The posting rules are as always:
08-15-2016 09:28 PM
08-19-2016 09:16 AM - edited 08-19-2016 09:17 AM
08-19-2016 09:33 AM - last edited on 11-16-2024 02:08 PM by Content Cleaner
As hinted in the discusssion of the bug right above, there is an omission for the "Map coordinates to xy" method. It does not say what the boolean returns. (The method for the other direction is better described)
Mentions that it "returns true" (Good!), but the boolean output is not listed in the parameter table (Bad!).
(It is listed under "data type", but I don't even know what the means here....Why does it even need a data type? Since it is always true, it carries no useful information)
Does not mention the boolean output at all (except as the "data type"), even though it is there. (Bad!&Bad!)
Hmmmm.... Feel free to discuss in the linked thread.
08-24-2016 03:00 AM - edited 08-24-2016 03:05 AM
The error seems to be only in the "Constraint Nonlinear Curve Fit" , details & work around here
> CAR 590370 has been filed to track this issue. This will be fixed in next release of LabVIEW.
08-28-2016 12:29 PM
Many years ago, it was achnowledged that the output of reshape array is inconsistent if one of the dimensions is zero. Behavior is still present in LV2016. I wonder if there is a CAR.
08-29-2016 10:46 AM
Under certain conditions, feedback nodes fail to work with matrix data, breaking perfectly legal code, either at edit time or on first run. (details).
09-01-2016 12:03 AM
05-25-2017 10:41 PM - last edited on 11-16-2024 02:09 PM by Content Cleaner
CAR 590370 was fixed in LabVIEW 2017. See the 2017 LabVIEW Bug Fix List for details: https://www.ni.com/en/support/documentation/bugs/17/labview-2017-bug-fixes.html