ensegre
-
Posts
550 -
Joined
-
Last visited
-
Days Won
25
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by ensegre
-
you mean "String ranges: A range of a..c includes all strings beginning with a or b, but not c." which is known and stated? I read time ago a discussion about its rationale, but I don't remember where.
-
Different packages have different names. For instance Matlab has log and log10, LV formula and mathscript has ln, lnp1, log10 and log2. Imho you shouldn't change. You're releasing a package which is essentially muparser, and can even work happily with the unpatched muparser, so users could expect a high compatibility with it. Besides you're already at version 1.0. You're going to irk your user basis...
- 172 replies
-
- 1
-
-
- expression
- math
- (and 1 more)
-
Say the mean. RMS would give you an estimate of the standard deviation of your measurement.
-
Yes I wasn't diligent at all, I just sketched it to make the point.
-
How often you write new elements versus how often you have to read the whole array may also skew the preference given to one scheme. For example, if you write often a single element, just replacing it in place at (i mod N) may be efficient, whereas the readout which involves an array copy may be left with a more expensive solution. This is my go at it, not double checked, may be bugged.
-
Yes, to be fair I also have to admit that I used the GrabbeX in a setup with a single analog camera. An old setup to which I don't have access anymore for further checks. But these kind of converters are cheap so the risk in trying out a few may be low.
-
I've had good experiences (in the past, who uses TV cameras nowadays anyway?) with this analog->USB converter (link to a random eshop, no recommenadation). You then see the camera as IMAQdx like any vanilla webcam.
-
hm, no, I haven't yet had to upgrade any installation with vision to 2017.
-
I have a fresh 2017 on windows with vision and both VIs are in. Are you sure it is not an installation problem?
-
interesting idea. With some modifications like firing only the first time the FP is Standard or Maximized it should do what the OP is asking, and work for clones too. I presume that the cost of dropping it in every BD is minimal and could automated with scripting. Going a step further, such a drop-in could even hold the opening of the FP till it receives a notification in return, that the cosmetic job has been done by the actor which handled it.
-
Maybe not the smartest or more efficient answer. I would think at this: I'd run it periodically and generate a notification for every one of the newly open FPs. Names are identificative as long as no two VI can be in memory with the same name. Now there is the problem of clones, as I was asking here. One suggestion given in the thread points to the fact that the naming scheme of clones is known, only their number a priori is not.
-
Appreciated, thanks.
-
VI server method to get refs of all clones?
ensegre replied to ensegre's topic in Application Design & Architecture
I see... Thanks both. -
I thought there was an easy, built in, VI server way of doing the following, but I haven't found one. Am I missing something trivial? So I have one application instance, spawning clones of a certain VI. I would like to get an array of the VI refs of all of these clones. I thought I could via some property like Application:All VIs in memory, but I haven't found any suitable. All VIs in memory gets only the base VI names. Missing that, I resort to register all my clones in a FGV as they startup, , and consult the FGV at will. Is there a more linear way? RegisterMovieWriters.vi I also note that I have to associate each VI ref with its clone name in the FGV, otherwise plain refs to different clones match as equal in lookups.
-
quick test, seems to work ok in my project on windows. Noob question about vipm: I can't install the vip on linux, as it was build with vipm-2017. How can I build the package from the sources with vipm-2014, which is the latest available for linux (jki said no schedule for a new release). "Open Package Build Spec" LV_muParser.vipb gives me a blunt "VI Package Builder was unable to open the build spec due to an error".
-
No big deal, they are all very simple. The full message from mupGetErrorMsg() is already more informative, beyond that I can't imagine. See my go at it: mupCheckError.vi
- 172 replies
-
- 1
-
-
- expression
- math
- (and 1 more)
-
Indeed the other day I spent some time debugging an elusive crash-LV-second-time-button-is-clicked, which turned out nothing but a mistake attempting to destroy a stale muparser handle. A trivial issue: some of your VIs are broken because of the input varValue moved to position 3 of the conpane on Eval_SglVar_SglRef, I imagine a last minute change for uniformity.
-
I see. Yes, the difference with e.g. a camera is that you can think at scenari where multiple access could make sense. Discipline would be required nevertheless to handle races, even if a lock mechanism is built in, for instance I wouldn't see the sense of updating variables and evaluating completely asynchronously.
-
well, a disciplined programmer shouldn't do that. I think the same could be said for anything else living on some other handle wire. Camera sessions i.e....
-
wishlist: comprehensive error handling using http://beltoforion.de/article.php?a=muparser&hl=en&p=errorhandling, to locate expression syntax errors
-
I might incorporate the toolbox in a project (because it does booleans), and I found out that I would use the evaluation of multiple expressions within a single parser. mupLib/mupEvalMulti does it, but there is no equivalent mupExpr Eval function. What do you think about adding these two to the lvclass? (LV17 but I can backconvert) Besides, you named one Eval_MuliVar.vi, probably a typo. Eval_MulVarMulRes.vi MultiEval.vi mupExpr MultiMulti example.vi
-
Immediate crash "Fatal Internal Error 0x00000001 : "VariableManager.cpp", line 85" opening on linux VIs with controls bound to shared variables (project created in Windows). Something must be going on with the compiled cache, because eventually I can open the VIs (binding reset to none) at third attempt after two crashes.
-
Ah, that makes sense, thanks. As for me I don't have yet an use case for a numeric port; maybe others do.
-
I was about to write: but at least the NI TCP examples work for me, perhaps they use specific open ports? So it turns out I was reaching these examples out of their <LV>/examples/ location, not out of the Example Finder, because "NI Service Locator is not running". That link doesn't talk about linux, nevertheless put me on the track to (re?)install nisvcloc from the rpm. Suddenly my Messenging stuff works on this machine too, weird...
-
I'm evaluating the library for a project of mine, starting from minimal applications. I'm testing on LV17, one windows and two linux machines. My beginnings are fine on windows and on one of the two linuxes, while on the second one they boil down to errors like: which I get from Test Client.vi from the couple in <LV>/examples/drjdpowell/Messenging/TCP example/. On linux I'm with v1.8.3.82, limited by vipm2014. I suspect a simple network configuration difference, but I'm still too lost in the bowels of the library to attempt debugging. Any hint?