Bug in coefficients output of General LS Linear Fit LabView 8.5.1?

Hi
I compiled my application from LabView 7.1.1 to LabView 8.5.1. This application use the "General LS Linear Fit.vi". I noticed that there differences in the calculation of the coefficients.
There are attached two files, one comiled in LV7.1.1 and the other with LV 8.5.1, with two different results. Please make sure you open this files with the correct version.
If I change in "General LS Linear Fit.vi" the link to the lvanlys.dll of the LV7.1.1 version, the calculations are correct.
Any help would be appreciated, thanks.
Fil

Hi André
I think the results in the 8.5 Version are completely wrong. If the result would deviate a few percent one could say that the new version could be more exact. But not like that.
Fil
Attachments:
calc_71.JPG ‏154 KB
calc_85.JPG ‏184 KB

Similar Messages

Bug in MSE output of General LS Linear Fit.vi?

Hi: In the General LS Linear Fit.vi, output MSE. Help for the vi describes the formula as (I attached a picture, but I'm not sure if it will appear in the post), but it looks like something is missing, because if I use the formula to my input values, I get a match only if all input Standard Deviations are 1's. As Standard Deviations increase, this formula gives me smaller MSE, higher MSE if Standard Deviations decrease; but I noticed MSE of the vi doesn't change so much, and every time all input Standard Deviations have the same value (no matter how large or small they are), MSE returns to the same original value.
According to the formula, MSE is inverse proportional to the square of Standard Deviations, no way to return to original value if they're changed. Is this formula correct or shuld it be different?
Attachments:
untitled6.jpg ‏5 KB

Hi, Karunya:
I actually rechecked my stuff, and I found that the formula that Mehak_D showed me in
MSE formula.JPG
is correct and really works. and the one I found in one of the LV 5 help files were wrong
untitled6.jpg
I'm attaching 2 pictures showing the LV5 Help file where I found it, as well as the Index where I clicked to open it. Just let me know if the formula were corrected in the Help file for later LV versions.
Thank you very much.
Attachments:
General LS Linear Fit Theory.jpg ‏96 KB
Help Index.jpg ‏34 KB

General LS Linear Fit - Number of Equations

Hi Folks,
I'm using the "General LS Liner Fit" VI to interpolate Measurement Data depending on 2 Variables. To do this i would like to use an poly-equation of the form:
z = A + Bx + Cy + Dxy + Exyy ... Kxxxyyy ... etc.
This sems to work fine, but im not able to generate more than ~ 100 Parameters. If i try to do so the VI doesen't give me any results.
I have ~ 2000 Data Points so i create a H-matrix of 2000 x 100 Values as Input for the VI. Can this be too much? For an Matrix of 2000 x 81 Values the System still works an takes ~2 Seconds to evaluate a result.
If anyone knows this problem, knows a better solution or can tell me what im doing wrong please help me.
Greetings
Hans

What I am seeing is that all of the algorithms (SVD, Givens, Givens2, etc.) work up to 90 coefficients (although SVD sometimes reports error -20003 in my application), but fail starting at 91 coefficients. I need something more like 600+ coefficients.
Has anyone run across an alternative LS Fit VI? I found a customer-sumitted alternative called "General_LS_Linear_Fit+.vi", but it still uses the same NI DLL function.
I wouldn't mind writing one myself if someone could point me to a write-up of any of the algorithms.
Thanks,
Travis

My test instrument is outputting a 5 line string but labview only read until the carriage return. how can I get it to read the whole string?

I have a labview sub-VI reading the string being outputted by a pH meter. The meter outputs a 5 line string and labview is only reading up to each lines carriage return, there-by giving me 5 separate strings is there anyway to rectify this and have the 5 line read as one string?
NAS1
St Petersburg FL
Labview 2010

Yes, LabVIEW will automatically update. What happens is that the old serial functions still exist in 7.1 and above but the code (the block diagram) has been modified to use VISA functions. Older versions of LabVIEW are fully supported in this manner. The only way you can avoid the automatic update is to have the old serial functions in an llb and your top level VI refer to these. Having any VI that was part of vi.lib in an llb is a very bad idea and the way to fix things is to remove any VIs in the llb that are part of the LabVIEW distribution.
I don't remember how the old serial config worked and what the new version does with the VISA Configure Serial Port. Your program should only have a single serial config and you might just be able to directly replace that with the VISA configure Serial Port.

The output of a power supply in labview using a Magna Power LXI over RS232 to simulate a periodic voltage.

How can I toggle the output of a power supply in labview using a Magna Power LXI over RS232 to simulate a periodic voltage? Any help would be apreciated?

LXI is Ethernet communication.
Does the power supply have an RS232 port?
Are you looking for an RS232 to Ethernet (LXI) Converter
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=rs232%20to%20ethernet%20ip
But to simulate a periodic voltage you need to send the SCPI "Source" command to the power supply in a loop.
Changing the Voltage setting in periodic value.
How fast of a periodic voltage do you need?
You may be limited to how fast LabVIEW, Windows and your power supply can respond to commands.
Use VISA writes. It is the same for LXI as it is for RS232. The LabVIEW code would be the same.
After you select the corrent VISA Ref, either a com port or an IP address, LabVIEW does not care if it is LXI or RS232.
From a Magna manual I found
Command Syntax
[SOURce]:VOLTage[:LEVel][:IMMediate][:AMPLitude] <nrf+>
[SOURce]:VOLTage[:LEVel]:TRIGgered[:AMPLitude] <nrf+>
Examples
VOLT 200
VOLTAGE:LEVEL 200
VOLTAGE:LEVEL:IMMEDIATE:AMPLITUDE 2.5

Bug with Bridge CS5 output /web gallery - renames files with ASCII

has anyone found a fix around this ? It makes my HTML galleries useless since it renames all the original files in ASCII code and there is no work around this.
I know that this issue has been going on for a while but Adobe hasn't done anything about this yet

Solved!
This works for Windows. I imagine the Mac solution is similar. Props to William Zauscher for helping find an answer.
I take no responsibliity for any damage caused to your computer, Photoshop or Bridge...
In Windows, browse to C:\Program Files\Common Files\Adobe\Bridge CS5 Extensions\Adobe Output Module\mediagallery\resources\scripts
In the file named "galleryCreator.jsxinc" replace the lines:
AOM.AmgGalleryCreator.createUniqueFileName = function(filePath, jpgFile, createMode)
    var alteredName;
    while (true)
         alteredName = "_";
        for (var i=0; i<10; i++)
             alteredName += Math.floor(Math.random() * 10);
         alteredName += ".jpg";
        var f = new File(filePath + alteredName);
        if (!f.exists)
            break;
     return alteredName;
...with the following:
AOM.AmgGalleryCreator.createUniqueFileName = function(filePath, jpgFile, createMode)
                var alteredName;
                while (true)
                                alteredName = "_";
                                alteredName += jpgFile += ".jpg";
                                var f = new File(filePath + alteredName);
                                if (!f.exists)
                                                break;
                return alteredName;
You can cut and paste the above. Just save a version of the original file somewhere in case of screwups...
Cheers!
-Mark

Captivate 7.0.1 Mac - Huge Bug in HTML 5 output

Hi everybody,
Have anyone got this problem as well? In the HTML 5 output there are no radio buttons or check boxes in the multiple choice/single choice questions at all.
If I generate the same content in SWF, everything is fine. Is it only my problem?
Thanks for info. :-)

I'm not on Mac. Can you check if you don't have objects on the master slide that are not merged into the background?

A general buffer block for Labview?

Has anybody made a function which stores acquired values and returns the contents when needed. In other words I need a buffer which is as simple and fast as possible and does not waste resources.
Of course, I can make a VI which has an uninitialized shift register and call it in the loop but it is not efficient enough in some demanding situations. And also, this kind of buffer will slow down the execution of the loop because the buffer increases all the time. (Clearing the buffer is possible by writing the contents to the file but it is a little bit complicated)
In many of my applications where the acquired data is needed to be plotted I have used waveform chart which has a history for the data. I have noticed th
at history feature can be effectively used as an buffer, it does not slow the execution like shift registers and you don't need to build any buffers by yourself.
In some cases I don't need to display the data but I just want to buffer it, therefore it could be very useful to have a general buffer block in the Labview which does not have any kind of appearance in the front panel, just a node in the block diagram.(of course one way is to use the history of the waveform chart and hide the chart)
I have been programming with LV over two years daily but making of efficient buffers has always been a question to me. I have noticed that other colleagues have same kind of problems.
Maybe this kind of buffer block could be made by c-language code and called it by the LV, but calling functions from dlls take also some time overhead which can be too much.

Hi Wirer,
see attached file.
Mike
Wirer wrote:
> Has anybody made a function which stores acquired values and returns
> the contents when needed. In other words I need a buffer which is as
> simple and fast as possible and does not waste resources.
>
> Of course, I can make a VI which has an uninitialized shift register
> and call it in the loop but it is not efficient enough in some
> demanding situations. And also, this kind of buffer will slow down the
> execution of the loop because the buffer increases all the time.
> (Clearing the buffer is possible by writing the contents to the file
> but it is a little bit complicated)
>
> In many of my applications where the acquired data is needed to be
> plotted I have used waveform chart which has a history for
the data. I
> have noticed that history feature can be effectively used as an
> buffer, it does not slow the execution like shift registers and you
> don't need to build any buffers by yourself.
>
> In some cases I don't need to display the data but I just want to
> buffer it, therefore it could be very useful to have a general buffer
> block in the Labview which does not have any kind of appearance in the
> front panel, just a node in the block diagram.(of course one way is to
> use the history of the waveform chart and hide the chart)
>
> I have been programming with LV over two years daily but making of
> efficient buffers has always been a question to me. I have noticed
> that other colleagues have same kind of problems.
>
> Maybe this kind of buffer block could be made by c-language code and
> called it by the LV, but calling functions from dlls take also some
> time overhead which can be too much.
Attachments:
FIFO_WO_LocalVar2_6i.vi ‏48 KB

I'm getting an error - VxD NIPALK(01) when trying to output a 5 second tone through LabVIEW and AO...a 2 second tone is no problem.

I'm using LabVIEW 6i, Windows 98, and a PCI-MIO-16E-4 board which is supported only by earlier versions of NIDAQ. Any suggestions?

Hello;
To give you better advise I would need more details about the signals you are trying to output to the analog channel of your DAQ board; such as update rate, frequency of the signal, number of channels, etc.
Regards
Filipe

General Purpose Signaling with LabVIEW 7

I need LabVIEW 7 to handle the following situation. I have 3 concurrent VI's - A, B and C. A and B want to hear different sets of "signals" from C. Specifically, A wants to hear only signals 2, 4 and 6 while B wants to hear only signals 1, 3 and 5. These sets are arbitrary and NOT known at compile-time. Furthermore, A and B can listen for their signals one or more at a time, service any received signals, and loop to listen for one or more additional signals. Neither A or B want to poll and both must hear all their respective signals regardless of the order they are generated by C and regardless of the order A and B choose to listen for them.
LabVIEW 7 Notifiers almost solve this problem except for the timestamp feature that
prevents notifications from being received out of order. For example, if C sends notifier 1 to B while B is waiting on notifier 3, and then C sends notifier 3, notifier 1 will NEVER be heard by B (unless, of course, B has a Wait on Notification icon on his diagram for each possible notification he is to receive).
User defined events look very promising for solving this problem but I am not sure how to get the event structure to hear different sets of events (not known until run-time) at different times. For example, A may first want to listen for signals 2 and 4, say with a timeout, and then listen for signals 4 and 6.
Any insights into solving this problem would be appreciated.
W. Brown

Attached is a workaround that answers this problem.
W. Brown
Attachments:
Notifier_Problem.llb ‏91 KB

How to implement general error handler in labview projects

Thanks,

Hello,
You may also find these links useful:
Custom Error Handling In LabVIEW
http://zone.ni.com/devzone/conceptd.nsf/webmain/de4f036f22c4b9f286256fee0010b6fd
LabVIEW Introduction Course - Six Hours (has a section on error handling)
http://zone.ni.com/devzone/learningcenter.nsf/03f7c60f17aad210862567a90054a26c/55974411828f779086256...
Hope this helps!
Charlie S.
Visit ni.com/gettingstarted for step-by-step help in setting up your system

Bug sur la fonction "Linear Fit" entre LW 8.0 et LW 2009

Bonjour,
nous rencontrons des différences sur le résultat de la fonction LINEAR FIT.vi (avec méthode bisquare)
Le même programme, un compilé sous LabVIEW 8.0 et l'autre sous LabVIEW 2009, donne des résultats différents.
Je ne trouve pas les corrections qui ont pu être apportées sur cette fonction entre les différentes versions de LabVIEW.
Comment être certain que la fonction donne de bons résultats ? Celle sous LabVIEW 8.0 est-elle correcte ?
Pour info, le résultat sous Lw 2014 est le même que sous LabVIEW 2009.
Merci

Sorry for the delay.
I added two sreenshots with the same function and the same datas: the first example runs on LW8.0 and the 2nd runs on LW2014.
We encounter differences on results (slope, interception ... etc)
Thank you for your help
Attachments:
RegLin_8.0.JPG ‏132 KB
RegLin_2014.jpg ‏144 KB

Linear Fit Weight Input Modifying Control Input - Impossible? Bug?

I was having some strange data array issues with a program I was debugging and ended up distilling the issue to this. When "Linear Fit" is called twice it modifies the weight input array passed to it. Sounds crazy; but its true. I've been able reproduce this with a simple vi that I've attached.
The terrible thing is that if the weight array input is a control; its values will be modifed after calling Linear Fit. And if you've branched that wire and used its values for some other part of your program; the values on that wire will also change.
I'm using LV 8.5.1
I'd appreciate it if someone could verify this is happening on their machine. I'm too delirious from beating my head against the wall after tracking this down.
Milan
Attachments:
Linear Fit Test.vi ‏19 KB
Linear Fit Test capture.png ‏79 KB

You can also patch the problem by inserting an "always copy" primitive right before the linear fit. See attached.
Message Edited by altenbach on 12-15-2008 01:52 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
LinFitpatch.png ‏11 KB
Linear_Fit_TestMOD.vi ‏20 KB

Multivariable least square fitting

Can Labview, specifically General LS linear Fit VI do the following fitting?
I have x, y, P as independent variables, and fit a curve B to a function of :
B = b0 +b1*x +b2* y +b3 *P + b4 *x^2 + b5*y^2 + b6 * P^2 + b7* x*y + b8*x*P + b9 * y*P;
There are 12 data points to get 10 coefficients, b0-b9.
I'd appreciate any comments. Thanks,

You have three independent variables (x,y,P), one dependent variable (B), 10 linear coefficients, and 12 datapoints B(x,y,P) in 3D.
All coeefficinets are linear, so all you need to do is setup the H matrix and B vector according to your data, then use general linear fit.
How does the data look like? What does it represent? Can you attach a typical dataset?
Note: Since you call it "general LS linear fit", you must have an older LabVIEW version, but it is the same as "general linear fit" I mentioned above. It should be able to handle this problem easily. Have you tried?
LabVIEW Champion . Do more with less code and in less time .

Audio Looping bug in rendered output

I've hit a recent issue where I'm getting audio looping / stuttering bugs in the rendered output. Doesn't happen at the start of the clip, but elsewhere if I fade everything down to black / nothing, and then fade up again into the next clip, the audio loops / stutters during that fade in. Using "Constant Power" to bring up the audio from nothing to full. Clip plays fine in Premiere, just the final output has the issue. Have encoded audio as both WAV and AC3, same issue.
Curiously, if I output a WAV file only (no video) straight from Premiere, it is clean. That's how I'm now working around this, and coding the AC3 track in Audacity when required. Also (even more curiously!) I recently installed Audition, I'm wondering if that has messed anything up in Premiere. Audition wasn't actually used in any of these corrupt projects (and the project I used Audition for was fine as far as I am aware), but I've never had it installed until 2 or 3 weeks ago.
Anyone else hit this, or know how to fix it? Between this and the video render issue I posted a couple of months back (still not resolved), I'm rapidly losing faith in Adobe's encoding tools.
I can post some example clips if anyone wants a listen. Reminds me of the XDCAM looping bug that existed a while back, although the scenario there was somewhat different (audio at the end of the clip looped, and my current video is AVCHD from a Sony NX5, not XDCAM).
Premiere Pro CC 7.2.1 (4)
Media Encoder CC 7.2.0.43 (64-bit)
Audition 6.0 Build 732 (64-bit)

Hi madmaxmovies,
Thanks for posting on Adobe forums,
Please follow suggestion provide in this link http://forums.adobe.com/message/5997457
Thanks,
Sandeep

Bug in coefficien​ts output of General LS Linear Fit LabView 8.5.1?

Similar Messages

Maybe you are looking for

Bug in coefficients output of General LS Linear Fit LabView 8.5.1?