Irrelevant Mathscript error -20033

Hi there,
I am trying to make some code work with MathScript RT in LabView 2012, but I keep getting an error -20033 (see screenshot below) for an irrelevant line of code.
The line MathScript complains about (line 45) is the following:
percentLast = floor(max(levelPercent));
This error does not make any sense for that line (levelPercent is a 1D array), and no line above or below corresponds to that error either.
If I comment out the offending line, I get the same error for another completely unrelated line.
Also note that the very same code works well with MATLAB.
Is there a known bug in MathScript that could create this behavior? If yes, is there a way to work around it?
Thanks in advance for your help.
Best regards,
Olivier H.

Actually, I could trace this error to a call to resample() at another unrelated location (and different .m file) in the code. I found it by basically commenting out one line at a time until the error disappeared. It looks like error reporting needs some work in Mathscript.
Olivier

Similar Messages

Mathscript node: an internal mathscript error has occurred: 64-bit LabVIEW 2009

Hi Folks -
I have an installation now of
LabVIEW 2009 9.03f, Vision, and Advanced Signal Processing Toolkit, all
64-bit versions on a new computer so that I can convert some code from
32- to 64-bit.
I figure I will address errors
one-by-one and here's the first one. I have a VI with a mathscript
node and the VI, which loaded and ran fine in the 32-bit environment,
is now broken and giving the error "mathscript node: an internal
mathscript error has occurred." My main concern - is mathscript not
supported in 64-bit LabVIEW right now?
I am attaching the VI. Any ideas are appreciated. I need to get this working.
Also, NI, is there a special 64-bit forum that we should post to in the future, or create to post to?
Sincerely,
Don
Solved!
Go to Solution.
Attachments:
sort.vi ‏753 KB

From 2009 help
LabVIEW MathScript is a text-based language you can use to write functions and scripts. You can process scripts using LabVIEW MathScript in the LabVIEW MathScript Window or a MathScript Node. When you create a LabVIEW MathScript, you must use supported data types.
The MathScript syntax is an intuitive and logical
syntax predominantly based on standard mathematical and computer
programming terms, terms in widespread and common use, and/or
descriptive abbreviations, truncations and concatenations of standard
terms. The LabVIEW MathScript Window and MathScript
Nodes are able to process files you create using the current MathScript
syntax and, for backwards compatibility, files you created using legacy
MathScript syntaxes. The LabVIEW MathScript Window
and MathScript Nodes also can process certain of your files that use
other text-based syntaxes, such as files you created using the MATLAB® software. Because the MathScript RT Module engine is used to process scripts in the LabVIEW MathScript Window
and MathScript Nodes, and because the MathScript RT Module engine does
not support all syntaxes, not all existing text-based scripts are
supported.
(LabVIEW 64-bit) LabVIEW MathScript is not supported in LabVIEW (64-bit).

Mathscript error in an out clusters

It appears that Mathscript Nodes do not execute if there is an error at their error in cluster. This seams to be what I would expect to happen. The error in then feeds to the error out cluster. Again this seems to be what one would expect to happen.
However, I was curious if one has access to reading the error in cluster and/or writing the error out cluster within the Mathscript Node?
Kevin

Hi Kevin,
While you cannot read the elements within the error cluster directly in the Mathscript Node, I have a couple comments that will likely help.
First, check out the link below, specifically sections 5 “Debugging Your Code Within the MathScript Node” and 6 “What Does This Yellow “Exclamation Point Mean?” This describes the functionality of the error cluster you wire into the error input.
http://www.ni.com/white-paper/3256/
Second, I think your best bet, if you would like to actually use the information contained in the error cluster, is to simply unbundle the error cluster and pass the individual items into the Mathscript Node. The error cluster contains a status (Boolean), code (integer), and source (string). Use the Unbundle function to extract one or more of these and pass them into the Mathscript node individually.
http://zone.ni.com/reference/en-XX/help/371361J-01/glang/unbundle/
http://digital.ni.com/public.nsf/allkb/BF72229C53F7633386256EDD0069331B?OpenDocument
Ryan C.
Applications Engineer
National Instruments

Retrieve RowSet and Display in Output Text Component

To retrieve a row object, took more effort than I expected with this tool. I wanted to populate a simple output text component with a db object pulled from a row, and I binded it to the rowset column. It worked great, but it kept retrieving the first row, since in the JSP it was calling this:
#{questionsetup.questionRowSet.currentRow['question']}
To get it to increment rows per output text component I did this:
questionRowSet.setDataSourceName("java:comp/env/jdbc/SelfService");
        questionRowSet.setCommand("SELECT ALL dbo.Question.quesId, dbo.Question.question, dbo.Question.lastChangeDate FROM dbo.Question");
        questionRowSet.execute();
        questionRowSet.next();
        outputText3.setValue(questionRowSet.getString("question"));
        questionRowSet.next();
        outputText4.setValue(questionRowSet.getString("question"));
        questionRowSet.next();
        outputText5.setValue(questionRowSet.getString("question"));Is there another way to do this automatically? The Studio Creator way? Or is this correct? The Studio Creator help file explains how to bind a simple component, and using the binding, but it even says it will retrieve the data in the first row. Incremenet rows or specifying a specific one would really help!
Thank you very much!

Maybe take control of the Select statement myself...
So I decided to get the MIN value of my ID
like this
"select MIN(T21id) AS ttt from persons"
now this is valid in SQLyog
BUT Creator says
Description: An unhandled exception ...
Exception Details: javax.faces.el.PropertyNotFoundException
Invalid column name: BaseRemuneration
nb why is this "unhandled" since it is inside a try block?
why does it mention BaseRemuneration which is a completely different but valid column??
So Sun Creator will accept an unknown subset of valid SQL commands, and give bizarre irrelevant exception error messages on the set of valid SQL statements that it doesnt like.
The documents appear to state that MIN is not handled by the IDE but can be entered manually.
In fact it can NOT be enmtered manually.
So is there an accurate list of valid SQL that is accepted?

How to REALLY monitor a J2EE-engine?

We recently started implementing an EP 6.0 project as well as a NWDI infrastructure to develop some thing for Internet Sales on CRM 2005.
I installed a NW2004s SR1 and patched the instance up to SP7 - so latest and greatest.
However, doing a search for "exception" in the log directory I get a number of 201670 (yes, you've read right).
Using the logviewer I see on each start and during runtime ~ 200 - 300 exceptions that are getting thrown, some of them often, some of them only one - so I counted about 80 - 90 different exceptions.
How should I as an administrator find out, which ones of them are crucial for the application, what is a real error and what is just an exception, because something is installed but not (yet) configured?
Setting up NetWeaver Administrator will not help much since I would get 90 mails every day with different errors and I would see there also those 90 different errors.
How to distinguish between relevant/irrelevant exceptions/errors? There's no source code around and I doubt, that it's necessary for an administrator, to learn the full J2EE API just to get those informations. It can't also be that I need to create OSS calls to get an answer from the development.
Where is some documentation what part of the engine is used where, what errors can be ignored and which of them needs to be followed?
Markus

Apologies, this thread is old but worth a mention.
No problem with that!
I was in ramp up for 630 J2EE and starting from the beginning it was clear that ERROR means there is some type of error that can even be of user cause and so ERROR was a rubbish thing to monitor (a bit like looking for red messages in SM21).
We don´t have many "red messages" in SM21 - and if, then there is really a problem (like a dump)
However, right from the start I have been alerting on CRITICAL errors as these mean trouble. Seems to work well..
There are less of them - true - but they are even less speaking:
#1.5^H#00118513360B002E000000250000399900044B606D5EC8B1#1208777430714#com.sap.engine.services.failover.st
orage#sap.com/irj#com.sap.engine.services.failover.storage#Guest#0##n/a##55b6fe700f9611ddbf4800118513360b
#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.failover.exceptions.PersistentStorageException: Exception occurred during
I/O operations.
        at com.sap.engine.services.failover.storage.DatabasePersistentStorage.serializeSession(DatabasePe
rsistentStorage.java:123)
        at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.serializeSess
ions(ApplicationThreadDestroyer.java:104)
        at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(Applicati
onThreadDestroyer.java:72)
or
#1.5^H#00118513360B00070000000100006B1100044D3854843446#1210804238299#com.sap.engine.services.security.po
licyconfiguration##com.sap.engine.services.security.policyconfiguration####n/a##60ab1ab0220511dda5f700118
513360b#SAPEngine_System_Thread[impl:5]_67##0#0#Warning#1#/System/Security/PolicyConfiguration#Java###Exc
eption occurred during remove of policy root [{0}].
[EXCEPTION]
{1}#2#service.iiop#com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration entry
with the name "service.iiop" cannot be found in the configuration "security/configurations".
        at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getValue(ConfigurationDat
aCacheAllImpl.java:98)
        at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getConfigEntry(ReadAccessConfig
uration.java:849)
        at com.sap.engine.services.security.server.PolicyRoots.removePolicyRoot(PolicyRo
I gave up on Java.
We run the instances and in case of a problem we restart all affected Java systems subsequently until the error vanishes because trying to "find" an error in a federated portal network (with some scenarios 6 or 7 machines affected) is not only cumbersome and very time consuming but in most cases meaningless because the support needs a reproducibility, a case, otherwise they can´t help - and recommend to "install the latest support packages". This is also true for production system. In case I open a prio-1 call I don´t only got hold off sleep because they are working on the call 24 h but we finally end in restarting the engines though.
There´s one call open since June 2006 - which is now two years old - about the dependencies in the packages and how to find out which service/applications needs which, to monitor only the really necessary ones. Since the development itself is not able to tell which dependencies they generate then, well, it´s better for everyones nerves and finally health to "just reboot" as you were (and maybe are) doing with Windows boxes if they don´t behave as they should. Maybe it´s by design/defnition like this, I don´t know.
We´re now in the process of putting all Java instances onto clusters to do an automatic switchover so the instances get restarted every few days and we avoid any problems that are caused by instances running too long.
I wish there was another solution or an idea of how to deal with that - I don´t know how others handle that but I have to take of about 50 instances (ABAP + Java) so I don´t just have the time of collecting dozens of logfiles of half a dozen machines and open an OSS call try to explain someone at the other side of the world in a foreign language (english is not my native language) what´s happening. The problem starts with "in which component do I open the call?"
Markus

Failed assert: unexpected type_builder::visit_unspec (Studio 12.1 CC)

Folks,
I'm trying to port a largish chunk of code from GCC to Studio. The following snippet, whittled down from the
larger code, works fine with g++ but fails with CC 5.10 SunOS_i386 2009/06/03, attempting a 32-bit build on
an Ultra-27, Solaris 10.
Compile command is `CC vectest.cpp'. Error is
>> Assertion: unexpected type_builder::visit_unspec (../lnk/v2mangler.cc, line 1635)
while processing vectest.cpp at line 33.
Code for vectest.cpp is
template <class T> class BCP_vec {
public:
typedef T* iterator;
iterator start;
iterator finish;
BCP_vec() {} ;
iterator begin() { return start; }
iterator end() { return finish; }
template <class T> void purge_ptr_vector(
       BCP_vec<T*>& pvec,
       typename BCP_vec<T*>::iterator first,
       typename BCP_vec<T*>::iterator last)
/* Actual code seems to be irrelevant to error */
int main (int argc, char* argv[])
BCP_vec<double*> vars ;
purge_ptr_vector(vars,vars.begin(),vars.end());
}Any suggestions for a workaround appreciated.
Thanks,
Lou

It is a known bug. Next version of the compiler (CC 5.11) will compile the code. For CC 5.10, you going to need a patch that I hope will soon be available.

Mathscript csvread error

I've been wrestling with this one:
Mathscript vi with some csvread() statements (copied in from an old Matlab program I'm converting).
I run the vi and it generates a file not found error:
Error -90001 occurred at Error in function csvread at line 1. LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Of course before this I made sure to set the path using the Mathscript window options menu to the full path where the files are (and the files are there).
Here's the rub: if I open up the Mathscript window and cut and paste the exact code from my vi into the command line - it works perfectly - no errors.
I must be doing something wrong. Is there maybe a global LV project search path that needs to be set or something. BTW: it's weird that the error comes from NI-488 GPIB interface - I'm not connected to any hardware - it's a completely sw application right now.
Thanks in advance for any suggestions,
Tom

Dear Chris,
First thanks for your advice.
BTW, I could solve it just adding absolute path.
The offending line of code was:
data=csvread('a.csv');
t=data(:,1);
y=data(:,2);plot(t,y);
I changed it to:
data=csvread('F:\1MY-DATA\Labview\Mat\a.csv');
t=data(:,1);
y=data(:,2);plot(t,y);
it worked,
Thank you very much, Chris
Have a great day!

Labview 8.5.1's MathScript window failed running imread with an error "A problem occurred in a subVI call."

Hi,
I am trying to port a Matlab program into a MathScript script. Following is the first few lines of the script:
clear;
image1=imread('C:\LV_VertAlign\DSC_0104.jpg','jpg');
image_double1=im2double(image1);
image_gray11=rgb2gray(image_double1);
In the first line, imread is supposed to read in a photo taken from a DSLR camera, so I think it's a 32-bit image. And this is the error I got when trying to run this script in the Labview 8.5.1's Mathscript windows:
"Error in function imread at line 2. A problem occurred in a subVI call."
What is the problem here? and why does it complain about a subVI call?
Thanks for any help to point me in the right direction.
-Anh

Hello Anh,
As you may know, LabVIEW MathScript is implemented on top of LabVIEW. The error message you received indicates that a problem occurred in one of the LabVIEW subVIs that MathScript calls. As Jim indicated, the problem is in the file type specifier you passed to the function. MathScript requires the use of 'JPEG' and not 'jpg' or even 'jpeg.' In this case, we could return a better error message. I have filed a bug report (115804) for this issue.
You will find that once you fix this, the im2double and rgb2gray functions are not supported. In LabVIEW MathScript, you generally can execute scripts written in the MATLAB® language syntax. However, the MathScript engine executes the scripts, and the MathScript engine does not support some functions that the MATLAB software supports.
We will look into adding these functions in a future release of LabVIEW MathScript. If you need this functionality now, these functions are very simple to write yourself. If you are performing additional image analysis in your script, you may wish to purchase the IMAQ toolkit. It doesn't add any functions to MathScript at this time, but you could continue your analysis outside of MathScript with LabVIEW VIs.
MATLAB® is a registered trademark of The MathWorks, Inc.
Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

Finding Permutations using perms in MathScript throws Memory is full error

I'm using the perms Mathscript function to find possible permutations of single digit numbers in an array. According to the perms function help it will accept 15 elements or fewer. I can feed this function up to 9 elements but when I try 10 I get the error - LabVIEW: Memory is full. I've increased the Virtual Memory per the suggestion in the Why do I get "Memory is Full" Error KB.
The error occurs when Windows Task manager reaches 628 M no matter what I change my Virtual Memory to. I do have 2 GB of RAM in my computer. Any suggestions?
Thanks,
Message Edited by CactusCoder on 11-14-2008 11:02 PM
Message Edited by CactusCoder on 11-14-2008 11:04 PM
Solved!
Go to Solution.
Attachments:
pirm.vi ‏16 KB

This is expected. With N=10, the final matrix will be 10!x10, or about 36Million elements of DBL. Each contains 8 bytes, bringing the footprint to ~290MB for a single copy of the expected output matrix.
Looking at the memory use of the VI for N=9, it is already 100MB, so it looks like there are about 4 copies of the final array in memory. No wonder N=10 is impossible.
I would recommend to implements this in plain LabVIEW (wires and loops) with a U8 datatype, you'll probably be able to go higher than 9.
Don't forget that 15 is unrealistic, because the array dimensions are I32, but the array size will be N!. This means you don't have enough rows for e.g. N>12 anyway.
Do you have a good reason that you need such huge arrays?
LabVIEW Champion . Do more with less code and in less time .

VA88 - Error list of settlement run displays irrelevant sales orders

Hi All,
This is a problem relating to transaction VA88 for settlement of sales orders into COPA. The error list of the settlement run is unnecessarily long since it also includes old, irrelevant sales orders that have no postings since the last VA88 run.
'Old' sales orders without recent postings on them are considered in the settlement run despite having the indicator "check trans. data" switched on in the VA88 selection screen.
What could be the reason???
Ideally, system should ignore the irrelevant sales orders (those without any transactional postings since the last settlement) if we select the "check transactional data" option in the VA88 selection screen
Any suggestions, thoughts, solutions would be highly appreciated.
Regards,
Soumya
Edited by: Soumya Bhattacharya on Mar 17, 2009 10:42 AM

Hi Soumya
Please see below. Transaction data checks are not made in the following situations, even
if the indicator is set:
1. The sender has a results analysis key, and an accrual calculation
    was already executed. In Customizing for accrual calculation, line
    item updates are not active for a version relevant for settlement.
2. The sender has a variance key and variances have already been
    determined.
3. The sender is a capital investment measure and has the technically
    completed status. Alternatively, the sender is an investment measur
    and the settlement was started with processing type 3.
4. The settlement rule was changed since the last settlement.
5. There is a valid distribution rule for fixed amounts.
6. Both a periodic distribution rule and an overall distribution rule
    have been defined for the settlement of costs with the same origin,
    and only the periodic distribution rule was used for the last
    settlement.
Basically you should see if any of these scenarios exist in your case. Item no. 6 looks like the most probable cause. Please check them again.
Hope this helps. Let me know.
Karthik

Error in Mathscript exercise (3.2) in "Introduction to LabView in 6 hours" tutorial

Hello,
I am working through the 6 hours introductory manual and I have noticed a few minor errors here and there. Also, as I am using version 8.6, some of things are slightly different.
However, I am stumped with exercise 3.2 regarding Mathscript. I even tried running the solution which I downloaded from the ni.com site but I still get the following error:
Error -90011 occurred at Error in function times at line 4. The sizes of the input matrices are incompatible. Verify that the matrices have the same size or that one is a scalar.
Does anyone know of an errata for this manual? Any other suggestions or hints are appreciated.
Thank you
Solved!
Go to Solution.

Hi,
I reproduced you error code, it isn't caused by an errata in the manual. Check the line 19 c. it is said that "Now multiply the Exp and In arrays element by element by typing “Out = In.*Exp;” and pressing Enter."
"Error -90011 occurred at Error in function times at line 4" means that
the times function isn't implemented correctly, according to the help
the good syntax is .*
So take a look at your code line 4 and check if the syntax is correct, otherwise replace those symbols byt he function name like in pictures I attached.
Hopefully this helps.
Regards,
Message Edité par Steve Mohamed le 02-19-2009 04:26 PM
Steve M.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Vidéo-t'chats de l'été : présentations techniques et ingénieurs pour répondre à vos questions

Mathscript Syntax Error

Can anyone let me know what the syntax error is in this
if((A>=1.70)&(A<=1.71))
A=1
if((A>=1.34)&(A<=1.36))
A=1
if((A>=0.925)&(A<=0.935))
B=1
if((A>=1.305)&(A<=1.32))
B=1
if((A>=1.935)&(A<=1.941))
C=1
if((A>=1.72)&(A<=1.73))
D=1
if((A>=1.70)&(A<=1.71))
E=1
if((A>=1.65)&(A<=1.66))
F=1
if((A>=1.29)&(A<=1.30))
G=1
if((A>=1.0)&(A<=1.05))
H=1
else
I=1
end
thanks chris
Solved!
Go to Solution.

I assume you want all of those if's (except the first one) to be an elseif. If this is not the case, then you want to put an end after each individual if.
Also, it's not a bad idea to throw a ; at the end of each statement. (Not the lines containing if, elseif or end)
Also, you probably want to use && instead of &. I'm not sure if mathscript differentiates between the two, but I know some languages do. The help file for mathscript uses &&, so I'd go with that. Anyone care to confirm if there's a difference?
Message Edited by elset191 on 05-07-2010 10:19 AM
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect

Error in Mathscript (FOPDT Transfer Function)

Hi all, i am trying to write a First Order Plus Dead Time system into the mathscript, unfortunetaly i found that it appear an error (please refer to the attachements), do anyone have idea or approach to write an FOPDT Transfer function in mathscript?
Thankyou veery much.
Solved!
Go to Solution.
Attachments:
error.png ‏18 KB

Thank you very much barp, both method work for me, but now i had face another problem.
I had try your method and design the PI controller, but the result (overshoot) is different compare to the result (overshoot) by using Matlab.
I had try to copy and paste the code from the Mathscript to the Matlab and step plot it. Consequently, the overshoot shown different value.
I also had try to check all the value and i found that everything is ok until the last line sys_cl=feedback(Gf,1), Labview has given the answer in transfer function but Matlab has show the answer in continuous time state space model.
The value of the transfer function : Gain = 58.46; Time constant = 0.55 and time delay = 0.06.
The value of Pi controller : Kp = 0.0784 and the Ti = 0.24.
I had attach some picture which show the difference.
Am i did something wrong in the mathscript and should i do it in Labview by different way?
Thankyou very much
Attachments:
matlab1.png ‏24 KB
labview bd1.png ‏28 KB
labview bd2.png ‏43 KB

Global - MathScript Node Failed To Compile Error

I have Labview 2009 SP1 with Mathscript Module.
While using 'global' command, I've encountered "MathScript Node Failed To Compile Error" from the first time I tried it.
In Mathscript window:
'Error in line 0: An internal error occurred while processing this MathScript. Contact National Instruments with the MathScript you used.'
is produced for any simple 'global a' (or any other variable name used).

Opps, one step you missed in the error code: Contact National Instruments with the Mathscript you used.
Go ahead and attach some example code that is throwing this error and I'll see if I can reproduce it on this end. There were a bunch of updates to the Mathscript Node in the F3 Patch so make sure that or LabVIEW 2009 SP1 is installed.
Also, are you seeing this on any other computers?
Look forward to hearing back!
Logan H
National Instruments
Applications Engineer

Getting -90031 (can't find function) error from Mathscript node when running executable, but works when I run the pre-compiled VI

I have set the Mathscript preferences 'Path' and 'Working Directory' parameters to the folder containing my scripts, and it works when
I run the VI, but I get a -90031 error when I run the executable.
What am I doing wrong?

Hi Umars,
I had the same problem. In my case it turned out that it was caused the surrounding code. Plus the error
message was missleading. I got the error message -90031 (unknown symbol CalcWelchCorr2) for the
following piece of code:
ecorr= 1;
if setup & src== 1
   for lag= 1:50
   rho= CalcWelchCorr2( lag, win );
   if rho > 0.001, ecorr= [ecorr; rho]; else, break; end
end
CalcWelchCorr2 is a user defined function located in the MS search path. The problem was caused by the
"break" in line 5. Actually this line was marked by some little warning symbol. Eventualle I modified the code
to get rid of the break
ecorr= 1;
if setup & src== 1
   lag= 1; rho= CalcWelchCorr2( lag, win );
   while rho > 0.001 && lag <= 50
      ecorr= [ecorr; rho];
      lag= lag+ 1; rho= CalcWelchCorr2( lag, win );
   end
end
and voila, the executable worked fine.
However, I had to check all my VIs ( > 200 !) for similar errors which gave me headaches.
Why does the application builder doesn't produce some appropriate error message ?
E.g. "Line xxx in MathScript node in VI xxx cannot be executed"? Currently you get the
impression that the application was build successfully but eventually you get strange errors
or even erroneous results. Keep in mind that tracking down bugs in the final application is
much more difficult that in LV. Also the error message produced by the executable was not
helpfull at all.

Irrelevant Mathscript error -20033

Similar Messages

Maybe you are looking for