NI Measurement Studio Idea Exchange

Community Browser
About NI Measurement Studio Idea Exchange

Have a new Idea for MStudio?

  1. Browse by label or search in the Measurement Studio Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea to the Measurement Studio Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
Top Kudoed Authors
User Kudos Count
1
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

When the installer builder is called from the system shell (cmd.exe) using a command like the following:

InstallerBuilder "D:\NI Installer Builder\INSTALLERPROJECT.iip" -Build -Log "D:\NI Installer Builder\niib.log"

It spawns a background process and the application returns with a successful run BEFORE the installer is created. As the build is started in a background and a detached process; any build automation frameworks such as bamboo, jenkins, chef, etc. cannot monitor it's creation. This results in a failed operation a breaks continuous integration systems. 

As a work around I have built a light python solution that monitors for a que event; in this case a
file either being populated or updated. I am using this application to monitor the log file as a que.
The python file should be attached to this submission.

Basically:
1. InstallerBuilder is ran – begins running building process in the background
and returns successful process run before installer is constructed.

2. IndirectProcessMonitor.py is ran (max timeout and file set):
python IndirectProcessMonitor.py 300 “D:\NI_installerbuilder\niib.log”
NOTE: Probably could set it to your setup file as well

3. IndirectProcessMonitor.py returns when timeout is exceeded or que file is
created or updated.

If the NI installer builder is to be able to be dropped into any automation
frameworks this has to be fixed on NI’s end. If this bug/support is scheduled
for development I’d be interested to know as it will/should break our
workaround.

I have a project file using .Net 4 (VS2010, properly update) which I opened in VS2013, upon opening with no warning all NI license.licx lines were removed with no warning whatsover.

 

This should never happen, if something is going to be changed the user should be informed what is happening, especially if it's going to break a build.

Hi, NI team.
I was adviced to share my idea here ( actually it was something I needed, not idea Smiley Happy ).
I have Waveform graph control in my application. There are two axes: vertical and horizontal. The plots I show on the graph have different units by vertical axis, so I decided to show those units as a caption of vertical axis. However I wasn't able to give this caption appropriate view and was forced to use label control. The problem with the caption of vertical axis is that it is oriented vertically and you can only change text direction between top-to-down and down-to-top. What I was looking for is a normal orientation from-left-to-right.

 

May be someone else will use this feature in future Smiley Happy
Regards

Plotting a big array of sample uses quite some time in the current version. I think this comes from Measurement Studio drawing a line explicitly between each two samples. However, in case of millions of samples, many of those lines will cover only one single pixel.

 

Instead of drawing all lines, it would be possible to sample the data at a rate where each sample matches just one pixel in the input axis. In order to not loose peaks, the sampling needs to do a min/max calculation and draw two lines for the minima and maxima. A shade could be used between the two curves. When zooming, the sampling needs to be repeated.

 

This feature would not only save much performance for big data (I think), it can also help to improve clarity of the graph, p.e. in case of noisy signals.

 

While it's great that Measurement Studio offers all capabilities for us to implement this functionality ourselves, such a feature could be of interest for many users.

 

Of course, this idea is not my intellectual property. It's a feature already implemented in other products.

0 Kudos

Currently, it seems that the only versions of Measurement Studio are 32-bit.  Since applications developed with 32-bit have certain limitations (particularly with memory usage), it would be great to be able to use NI analysis and filtering on larger files. Currently, this is a limitation that causes problems with processing some data files, and will only become a larger problem as the trend to store (and analyze) more and more information continues.  Perhaps I'm missing something and there's already a 64 bit version somewhere, but I did contact support and they were unaware of anything.