How to measure error on peak detect?

Hello!
I'm using the vi Waveform Peak Detect to find peaks in some signals that we analyze at the lab where i work. However, i must know also what's the error on the measure. Anyone knows if there is a vi that measures peak AND the error on the values found? Or at least a mathematical way to find the error myself?
Thanks!

This is not an simple question to answer. When you search for the peak value of a signal you have to make some assumptions about that signal. For example if your signal looks like [1, 1, -1, -1, 1, 1, -1, -1, ...], it may be difficult to define its peak value.
The first approach is, that your signal is a square wave of amplitude 1.0 and normalized frequency = 0.25. It this case the peak value is also 1.0
But the same signal could be the result of the sampling of a pure sine tone of amplitude 1.4142 (SQRT(2)). if you sample your sine tone at 45, 135, 225 and 315 degrees of phase, you get the same sequence of samples. In this case you would like your peak result to be 1.4142.
So the error can be as big a 41% (3 dB). This is of course an extreme situation, and
in most case the error is much smaller.
In general, the higher the relative bandwidth of your signal is (the ratio between the signal bandwidth and the used sample rate), the most uncertain is your result. So if you want to "stay in control" you need to make sure your signal is sampled at a rate that is high enough to give a good representation of your original analog signal.
As an option, you may want to re-sample your signal (to a higher rate) using an appropriate algorithm. The new resampling VIs offer various interpolation algorithm that you can experiment with, depending on the nature of your signal. The peak detection VI will then do the work for you.

Similar Messages

How to use peak detection in labview to detect peaks from data acquisition information

Hi
I am a university engineering student who is working in a team to develop a coin detector, its purpose is to recognize different coinage and detect fakes.
For this we are using LabVIEW 8.5.1. I am relatively new to labview and have had no experience of using to before. We are trying to integrate four voltage signals produced by an electromagnet, straingauge, optical sensor and a proximity sensor. We have already developed signal conditioning for these tests and now wish to put them into labview.
Our plan is to use peak detection on each of the tests so that labview can detect peaks which correspond to different coin types, provided they meet set criteria for each coin. Then to combine these either using logic or mathscript to produce a Boolean output for each coin.
One of our advisors helped us develop a peak detection program for a simple simulated sine wave however we are struggling to adapt this for data acquisition information and itegrate it with mathscript and to be honest it does not make much sense. I have attached the program below. Thanks in advance for your assistance.
Attachments:
Strain 2.vi ‏25 KB

Chris,
Here are several ways to help you get started with peak detection:
1. On your functions palette, you can search for "peak detect" and you'll find several different variations of VIs that will do peak detection.
2. You may also want to take a look at this tutorial: Peak Detection Using LabVIEW and Measurement Studio
3. There's an example in the example finder called "Peak detection and display" that will probably be useful.
Hope this helps,
Misha

6i can't find waveform peak detection vi. Load error code 20

6i can't find waveform peak detection vi. Load error code 20

The waveform peak detection VI is found only in the Full and Professional development systems. Do you have the base package?

Peak detect error

Hey guys.
I have a problem with my peak detect on a Power spectrum signal. from http://www.ni.com/white-paper/4278/en/ I know that
I would like to have f = 1 meaning that the frequency at which the acquired time-domain signal was sampled (Fs) has to be equal to the number of points in the acquired time-domain signal (N).
When i try to do this the peak detect returns the error 20013 the width must be greater than zero and smaller than sample rate.
this makes no sens to me ?
When i have Fs = N x 10 it runs.
I have added the VI that i have problems with ! if you need the whole project I will gladly add that to.
Attachments:
Both sensors.zip ‏329 KB

Hi Genex,
instead of that huge VI you should attach a smaller one, that demonstrates the problem! Right now we would need your DAQ setup to generate a signal to be able to try that VI...
So please:
Generate some typical waveforms, make them default in a waveform control and attach a VI with those waveforms and a typical call (with all your parameters) of PeakDetector!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Peak detection/DAQ

Hi! I am new in LabView.
I try to solve a problem with a peak detection in signal. I use BNC-2110.
This is my input signal - graph above show just digitized signal, and graph under - signal with "mean".
I have found 2 suitable .VI. They found peaks, but in simulate signal. I have try to change this program for using DAQ-Date as input signal. But it was not successful, I have become many errors etc.
Can you advise me, where is a problem?
With best regards, Alex
Attachments:
Signal.PNG ‏78 KB
Peaks_ermitteln2.vi ‏49 KB
peakxmpl.llb ‏40 KB

I now about this peak detectors, but they show very many peaks instead of 1
And in this Program (peaks_ermittlen) it was very good realized. But I don't understand, how can I change the type of Input Signal.
In this pic I have to draw, what i measure must - Time between 2 peaks
With best regards, Alex
Attachments:
Unbenannt.PNG ‏48 KB

Fetch and peak detection all channels of PXI-5105 with 4M record... HELP!

Dear collegaues!
Please help me to improve performance my application, see attachment, and sorry for my English.
So, my task is to fetch and peak detection all (eight) channels of PXI-5105 with 4M record and sample rate 4M with loop 1 sec...
Inputs of all my channels are wiring to NaI detectors with 0,5...1 microsec of pulse width (really) and freq from 0 kHz to no more than 40 kHz.
Why I've selected 4M record and 4M sample rate namely? Answer is that I've tested PXI-5105 previously by generator 40 kHz and 0,5 microsec width pulse. It is working fine and peak detection indicate for me 40000 pulses/sec. If I set lower than 4M record and 4M sample rate it is no working. In my honest opinion 4M record and 4M sample rate are very min settings.
In the present time peak detection working only 6 channels... When I've connected to diagram more than 6 "peak detector.vi" - I see the error "...out of memory...".
Please advise me, what is to be done for that is all working fine.
Solved!
Go to Solution.
Attachments:
consumer-producer7.vi ‏44 KB

What you are running into is an out of memory error in LabVIEW. You have enough onboard memory to capture 4M samples per channel on the digitizer. The issue is with fetching and manipulating that data in your LabVIEW application. You will want to step back and take a look at how you are handling your data to understand why that is happening.
1) 4M samples/ch = 4M Samples x 2Bytes/sample/ch = 8M Bytes/ch
2) Expanding to 8 channels creates 64M Bytes of data in the raw binary format
3) You are scaling your data by fetching in a 1D WDT format. This stores each sample in a 32 bit double, expanding the memory to 256M Bytes (in addition to timing information)
4) By splitting up the array of waveforms and branching data it you can easily create copies of this data, and if your consumer loop is not completed with the last data, you may be trying to capture a whole new set, creating yet another copy.
So you can see that while you have 1.5GB of controller memory, when dealing with large arrays of data you can easily eat up that memory. There are several things you can try to make your application more efficient. You could work with an unscaled binary data format, you can wire the array of waveform directly to the peak detect vi (instead of creating 8 copies, you will have a single copy with arrays of output) or you could revisit the record size you have chosen (experimenting with your threshold and width settings might help you to get the results you want with smaller record lengths).
-Jennifer O.

Problem in peak detection

Respected sir/madam,
i am actually processing human radial artery pulse signal... i acquired that signal and linearised that by using filter...
there is a problem in peak amplitude detection and location...by manually we can say there is more number of peaks ..but peak detector shows only 25 peak's amplitude and their locations...i can't understand about locations that shows..i attached the data which is in .lvm extension and the vi
please help me to rectify the problem..
thank you
Attachments:
Untitled 2.vi ‏100 KB
Untitled 2.vi ‏100 KB

Once again the Dynamic Data Type (DDT) generated by the Express VIs hides the real problem.
The data segments are too short to reliably detect the peaks - not every segment has a peak and some peaks may be partly in one segment and partly in the next. By combining all the data into one waveform before filtering and peak detecting, it is possible to get reliable matching between the "eyeball" peak detector and the software peak detector.
Note that the large transients at the beginning of the data set are detected as peaks. These transients are due to the real transient in the data and the transients of the filters. I did not attempt to remove them. You could use Array Subset with either manual selection of the end of the transient or some automated process based on the larger amplitude and lower frequency of the transient compared to the real signal.
There is a lot of "stuff" in this VI - things I tried and did not remove and multiple ways of doing things. The enabled diagrm of the Diagram Disable structure has a constant with the data from your file so that I did not need to read and process the file repeatedly while working on the filters and peak detector.
Comments in no particular order regarding what I did and how the posted VI works.
1. The DDT data from Read from Measurement File.vi is converted to an array of waveforms. The Waveform data type is well docmuented and the internal data structure is readliy accessible.
2. Each element of the array of waveforms from Read from Measurement File.vi is appended to the corresponding element from the previous iteration to form one array of waveforms containing all the data in the file. This is displayed on Array of Waveform, Array of Waveform 4, and Signals total. Note that these are graphs, not charts. The data is also put into 2D arrays as Array of Waveform 2 and Array of Waveform 3.
3. I do not have Advanced Peak Detector PtByPt.vi, but I think the data is not truly point by point so this may be a poor choice.
4. I used the standard filter VIs (rather than Express VIs) to stay away from DDT. The outputs are slightly different, but the Express VIs do not give you complete control or knowledge of what the filter setup is. I used Butterworth filters for both filters and adjusted the cutoff frequencies slightly to get similar waveforms.
5. I used the standard Peak Detector.vi from the Signal Processing >> Signal Operations palette. It reliably finds 104 peaks over a wide range of widths and some variation in thresholds. That count includes the transients at the beginning as mentioned above.
The .2 VI contains all the junk code I described above. The .3 VI is a cleaned up version.
Lynn
Attachments:
Untitled 2-9.2.vi ‏760 KB
Untitled 2-9.3.vi ‏183 KB

Peak Detection Algorithm for FPGA LabView

I am in the process of migrating my Labview software of a fiber optic sensor to an FPGA using a single board RIO. However, my program uses the pre-built Peak Detector VI, which contain some floating point math. I was wondering if there were any existing peak detection algorithms out there that uses the fixed-point math, required in the operation of the FPGA. Thanks in advance for your time and consideration.

mdnb2,
Here is a document on our website that talks about Peak Detection Using LabVIEW and Measurement Studio, though it references the VIs that are not available in FPGA, it has interesting information on peak detection in general.
As far as writing your own algorithm, here is how I would start writing one. Basic Steps :
1.) Search the array samples to find the top X number of points and their locations.
2.) Filter out multiple samples on the same peak by removing points close to other points by witdth of Y samples.
3.) Filter out low peaks by comparing the all remaining peaks to each other.
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Peak detection( take 100 ms samples?)

Hi...
I have a problem using peak detection under Analysis=>waveform monitoring.
I want to get the real data (ECG data), and detect the peak of the data. Then i want to store the index of the peak into array so that i can measure the time difference between two peaks.
my problem is that when i use peak detection, i cannot get the result as above mentioned. Before this i have tried to test the peak detector and found that if it will detect the peak for 100 ms time interval only. SO if i have waveform with f=100 Hz, then it will detect only 10 peaks..Is it correct that this vi takes 100 ms sample for detection? *correct me if i'm wrong
And since i want to get the real data from ECG hardware, is there any method to measure index of the occurence of all peaks and store it into array? (not only for 100 ms)
-I saw the formula in peak detector help :
To view the locations in terms of time, use the following equation.
Time Locations[i] = t0 + dt*Locations[i]
What does [i] here represent?
Thanks for the help...
Regards,
Rismi *newbie...:d

Hi...
Thanks, now i can understand about peak detection for simulate signal...
Then if i use this vi to detect peak of ECG data(data from DAQ or recorded data)..This vi will detect the locations of peak of current block of data. what "current block of data" in this case represents..??
i attach my simple program to detect the index of peak of my data. But i cannot get my desired result. And when i detect the number of the peak, the values is either 0 or 1. I don't know how to fix this problems.Can anyone give me advice?
Attachments:
retrieveSunday22.vi ‏161 KB

How to measure signal duration and statistics for each pulse

The attached vi has data for the maximum value of six different cutting tools while machining a part for 48000+ consecutive cycles. How would I measure the length of time each tool was used before being changed??(when profile makes a large negative transition.) Since the first three tools are related to the same holes in the part, I would also like to be able to get statistics(average) for each individual peak to see how the life of one tool affects the other tools. I am not sure if I need to do some more averaging or a differentiation to detect slope change points?? The peak detection vi's did not work real well since the peaks are not a constant value each time. This is a version 7 file.
Attachments:
display_tooling_data_max_values.vi ‏1643 KB

Judging by your graphs, what you need is a differential operation:
Break the wire going from the MEAN output to the graph.
Insert a TIME DOMAIN MATH block (from the ARITHMETIC AND COMPARISON palette)
Make sure it's set for DIFFERENTIAL.
Wire the output to your graph.
See all those negative spikes? That's the transitions in your data. Put a threshold on those, and you'll determine where the changes are.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

An unexpected error has been detected by HotSpot Virtual Machine:

Hi
When I upload the xml file with dubug window.
When I have debug then this message will come..
So give me a solution..
Here at below I have pasted files. in which I want to by pass the ldap..
So give me suggestion what to do with that files.
What's wrong with that file ?
Jiten
18 Oct 2007 17:02:09 0 INFO [main] security.SecurityUtil - SecurityUtil.login: Called with [email protected]; password=[C@1797795; sourceIpAddress=192.168.5.14; weblogin=false; realm=null
18 Oct 2007 17:02:09 16 INFO [main] security.SecurityUtil - login: start login: username: [email protected]
18 Oct 2007 17:02:09 125 INFO [main] BOOT - -- boot log messages -->
[BOOT] INFO: Loading OJB's properties: file:/C:/LMS/gsnx/deploy/webapp/gsnx.ear/webapp.war/WEB-INF/classes/OJB.properties
[BOOT] WARN: Can't read logging properties file using path 'OJB-logging.properties', message is:
C:\LMS\gsnx\OJB-logging.properties (The system cannot find the file specified)
Will try to load logging properties from OJB.properties file
[BOOT] INFO: Logging: Found 'log4j.properties' file, use class org.apache.ojb.broker.util.logging.Log4jLoggerImpl
[BOOT] INFO: Log4J is already configured, will not search for log4j properties file
18 Oct 2007 17:02:12 3282 INFO [main] security.SecurityUtil - SecurityUtil.login: Calling authentication with [email protected]; password=[C@1797795; realm=null
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d85c14f, pid=4032, tid=3260
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode)
# Problematic frame:
# V [jvm.dll+0x11c14f]
# An error report file with more information is saved as hs_err_pid4032.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Here :This is my login.config file..
* Copyright (c) 2003-2005 E2open Inc. All rights reserved.
* gnsx security configuration file
* Note:
* 1. At installation time, java.security file in your jre's lib/security/ directory should
* be edited add the following line (ganx.home} is the home directory of gsnx install
* login.config.url.1=file:{gsnx.home}/conf/login.config
* 2. Edit this file to replace ldap-url with the correct url for your
* LoginModule configuration.
* @version $Id: login.config,v 1.8 2006/02/04 18:38:11 vgeorge Exp $
gsnx.security.Login
* LdapLoginModule Options:
* ldap-url - LDAP connection URL, such as ldap://localhost:389
* e.g. ldap-url="ldap://192.168.31.63:389"
* dn-mask - The DN mask for user. The number 0 refers to the parameter
* number for username. If this is specified then user search is ingored.
* **This option is DEPRECATED**.
* e.g. dn-mask="cn={0},ou=People,dc=gsnx,dc=com"
* initialContextFactory - Class name of the initial context factory
* e.g. initialContextFactory="com.sun.jndi.ldap.LdapCtxFactory"
* connection-username - The DN used by the login module itself for authentication to
* the directory server.
* e.g. connection-username="uid=admin,ou=system"
* connection-password - Password that is used by the login module to authenticate
* itself to the directory server
* e.g. connection-password="password"
* connectionProtocol - The security protocol to use. This value is determined by the
* service provider. An example would be SSL.
* e.g. connectionProtocol="ldap"
* authentication - The security level to use. Its value is one of the following
* strings: "none", "simple", "strong".
* e.g. authentication="simple"
* user-search-base - the base DN for the user search
* e.g. user-search-base="ou=users,ou=system"
* user-search-pattern - filter specification how to search for the user object.
* RFC 2254 filters are allowed. For example: (uid=user1). To parameterize the value
* of the CN attribute type, specify (uid = {0}). The number 0 refers to the parameter
* number for username. This query must return exactly one object.
* e.g. user-search-pattern="uid={0}"
* user-search-scope-subtree - Directory search scope for the user (ture | false)
* ture - directory search scope is SUBTREE
* false - directory search scope is ONE-LEVEL
* e.g. user-search-scope-subtree="true"
* user-password-changepw-gsnx-handler - hander to change password
* If this handler is not specified, the change password feature will not be available
* if "com.gsnx.core.server.security.LdapLoginModule", is used the the
* option - user-password-attribute is required.
* e.g. user-password-changepw-gsnx-handler="com.gsnx.core.server.security.LdapLoginModule"
* user-password-attribute - attribute in LDAP that stores the user password
* If this is not specified, the change password feature will not be work
* when "com.gsnx.core.server.security.LdapLoginModule", is used as
* user-password-changepw-gsnx-handler
* e.g. user-password-attribute="userPassword"
* role-search-base - The base DN for the group membership search
* e.g. role-search-base="ou=groups,ou=system"
* role-name-attribute - LDAP attribute type that identifies group name attribute in the object
* returned from the group membership query. The group membership query is defined
* by the role-search-pattern parameter. Typically the group name parameter is "cn".
* e.g. role-name="cn"
* role-search-pattern - The filter specification how to search for the role object.
* RFC 2254 filters are allowed. For example: (uniqueMember = {0}). The number 0
* refers refers to the DN of the authenticated user. Note that if role membership
* for the user is defined in the member-of-like attribute (see user-role-name
* parameter) you may not need to search for group membership with the query.
* e.g. role-search-pattern="(uniqueMember={0})"
* role-search-scope-subtree - Directory search scope for the role (ture | false).
* ture - directory search scope is SUBTREE
* false - directory search scope is ONE-LEVEL
* e.g. role-search-scope-subtree="false"
* user-role-attribute - LDAP attribute type for the user group membership. Different LDAP
* schemas represent user group membership in different ways such as memberOf,
* isMemberOf, member, etc. Values of these attributes are identifiers of groups that
* a user is a member of. For example, if you have: memberOf: cn=admin,ou=groups,dc=gsnx,
* specify "memberOf" as the value for the user-role-name attribute. Be aware of the
* relationship between this parameter and group membership query. Typically
* they will return the same data.
* e.g. user-role-name="memberOf"
* ldap://ldap-qa.dev.e2open.com:389
* ldap://192.168.31.63:389
com.gsnx.core.server.security.PassthruLoginModule required
*com.gsnx.core.server.security.LdapLoginModule required
initial-context-factory="com.sun.jndi.ldap.LdapCtxFactory"
ldap-url="ldap://ldap-qa.dev.e2open.com:389"
connection-username="cn=Manager,dc=gsnx,dc=com"
connection-password="slapface"
connection-protocol="ldap"
authentication="simple"
user-search-base="dc=gsnx,dc=com"
user-search-pattern="cn={0}"
user-search-scope-subtree="true"
user-password-changepw-gsnx-handler="com.gsnx.core.server.security.PassthruLoginModule"
user-password-attribute="userPassword"
role-search-base=""
role-name-attribute=""
role-search-pattern=""
role-search-scope-subtree=""
user-role-attribute="";
This is LoginConfig.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policy PUBLIC "-//JBoss//DTD JBOSS Security Config 3.0//EN" "http://www.jboss.org/j2ee/dtd/security_config.dtd">
<policy>

<application-policy name="gsnx.security.Login">
<authentication>

<login-module code="com.gsnx.core.server.security.PassthruLoginModule" flag="required">
<module-option name="initial-context-factory">com.sun.jndi.ldap.LdapCtxFactory
</module-option>

<module-option name="user-password-changepw-gsnx-handler">com.gsnx.core.server.security.PassthruLoginModule
</module-option>


<module-option name="ldap-url">ldap://ldap-qa.dev.e2open.com:389</module-option>
<module-option name="connection-username">cn=Manager,dc=gsnx,dc=com</module-option>
<module-option name="connection-password">slapface</module-option>
<module-option name="connection-protocol">ldap</module-option>
<module-option name="authentication">simple</module-option>
<module-option name="user-search-base">dc=gsnx,dc=com</module-option>
<module-option name="user-search-pattern">cn={0}</module-option>
<module-option name="user-search-scope-subtree">true</module-option>
<module-option name="user-password-attribute"/>
<module-option name="role-search-base"/>
<module-option name="role-name-attribute"/>
<module-option name="role-search-pattern"/>
<module-option name="role-search-scope-subtree"/>
<module-option name="user-role-attribute"/>
</login-module>
</authentication>
</application-policy>
<application-policy name="client-login">
<authentication>
<login-module code="org.jboss.security.ClientLoginModule" flag="required">
</login-module>
</authentication>
</application-policy>

<application-policy name="jbossmq">
<authentication>
<login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
<module-option name="unauthenticatedIdentity">guest</module-option>
<module-option name="dsJndiName">java:/DefaultDS</module-option>
<module-option name="principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
<module-option name="rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
</login-module>
</authentication>
</application-policy>


<application-policy name="HsqlDbRealm">
<authentication>
<login-module code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag="required">
<module-option name="principal">sa</module-option>
<module-option name="userName">sa</module-option>
<module-option name="password"/>
<module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
</login-module>
</authentication>
</application-policy>
<application-policy name="JmsXARealm">
<authentication>
<login-module code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag="required">
<module-option name="principal">guest</module-option>
<module-option name="userName">guest</module-option>
<module-option name="password">guest</module-option>
<module-option name="managedConnectionFactoryName">jboss.jca:service=TxCM,name=JmsXA</module-option>
</login-module>
</authentication>
</application-policy>

<application-policy name="jmx-console">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="usersProperties">props/jmx-console-users.properties</module-option>
<module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>

<application-policy name="web-console">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="usersProperties">web-console-users.properties</module-option>
<module-option name="rolesProperties">web-console-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>

<application-policy name="JBossWS">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="unauthenticatedIdentity">anonymous</module-option>
</login-module>
</authentication>
</application-policy>

<application-policy name="other">

<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"/>
</authentication>
</application-policy>
</policy>
This is : java.security
# This is the "master security properties file".
# In this file, various security properties are set for use by
# java.security classes. This is where users can statically register
# Cryptography Package Providers ("providers" for short). The term
# "provider" refers to a package or set of packages that supply a
# concrete implementation of a subset of the cryptography aspects of
# the Java Security API. A provider may, for example, implement one or
# more digital signature algorithms or message digest algorithms.
# Each provider must implement a subclass of the Provider class.
# To register a provider in this master security properties file,
# specify the Provider subclass name and priority in the format
# security.provider.<n>=<className>
# This declares a provider, and specifies its preference
# order n. The preference order is the order in which providers are
# searched for requested algorithms (when no specific provider is
# requested). The order is 1-based; 1 is the most preferred, followed
# by 2, and so on.
# <className> must specify the subclass of the Provider class whose
# constructor sets the values of various properties that are required
# for the Java Security API to look up the algorithms or other
# facilities implemented by the provider.
# There must be at least one provider specification in java.security.
# There is a default provider that comes standard with the JDK. It
# is called the "SUN" provider, and its Provider subclass
# named Sun appears in the sun.security.provider package. Thus, the
# "SUN" provider is registered via the following:
# security.provider.1=sun.security.provider.Sun
# (The number 1 is used for the default provider.)
# Note: Statically registered Provider subclasses are instantiated
# when the system is initialized. Providers can be dynamically
# registered instead by calls to either the addProvider or
# insertProviderAt method in the Security class.
# List of providers and their preference orders (see above):
security.provider.1=sun.security.provider.Sun
security.provider.2=sun.security.rsa.SunRsaSign
security.provider.3=com.sun.net.ssl.internal.ssl.Provider
security.provider.4=com.sun.crypto.provider.SunJCE
security.provider.5=sun.security.jgss.SunProvider
security.provider.6=com.sun.security.sasl.Provider
# Select the source of seed data for SecureRandom. By default an
# attempt is made to use the entropy gathering device specified by
# the securerandom.source property. If an exception occurs when
# accessing the URL then the traditional system/thread activity
# algorithm is used.
# On Solaris and Linux systems, if file:/dev/urandom is specified and it
# exists, a special SecureRandom implementation is activated by default.
# This "NativePRNG" reads random bytes directly from /dev/urandom.
# On Windows systems, the URLs file:/dev/random and file:/dev/urandom
# enables use of the Microsoft CryptoAPI seed functionality.
securerandom.source=file:/dev/urandom
# The entropy gathering device is described as a URL and can also
# be specified with the system property "java.security.egd". For example,
# -Djava.security.egd=file:/dev/urandom
# Specifying this system property will override the securerandom.source
# setting.
# Class to instantiate as the javax.security.auth.login.Configuration
# provider.
login.configuration.provider=com.sun.security.auth.login.ConfigFile
# Default login configuration file
login.config.url.1=C:\LMS\gsnx\core\src\conf\login.config
# Class to instantiate as the system Policy. This is the name of the class
# that will be used as the Policy object.
policy.provider=sun.security.provider.PolicyFile
# The default is to have a single system-wide policy file,
# and a policy file in the user's home directory.
policy.url.1=file:${java.home}/lib/security/java.policy
policy.url.2=file:${user.home}/.java.policy
# whether or not we expand properties in the policy file
# if this is set to false, properties (${...}) will not be expanded in policy
# files.
policy.expandProperties=true
# whether or not we allow an extra policy to be passed on the command line
# with -Djava.security.policy=somefile. Comment out this line to disable
# this feature.
policy.allowSystemProperty=true
# whether or not we look into the IdentityScope for trusted Identities
# when encountering a 1.1 signed JAR file. If the identity is found
# and is trusted, we grant it AllPermission.
policy.ignoreIdentityScope=false
# Default keystore type.
keystore.type=jks
# Class to instantiate as the system scope:
system.scope=sun.security.provider.IdentityDatabase
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageAccess unless the
# corresponding RuntimePermission ("accessClassInPackage."+package) has
# been granted.
package.access=sun.
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageDefinition unless the
# corresponding RuntimePermission ("defineClassInPackage."+package) has
# been granted.
# by default, no packages are restricted for definition, and none of
# the class loaders supplied with the JDK call checkPackageDefinition.
#package.definition=
# Determines whether this properties file can be appended to
# or overridden on the command line via -Djava.security.properties
security.overridePropertiesFile=true
# Determines the default key and trust manager factory algorithms for
# the javax.net.ssl package.
ssl.KeyManagerFactory.algorithm=SunX509
ssl.TrustManagerFactory.algorithm=PKIX
# Determines the default SSLSocketFactory and SSLServerSocketFactory
# provider implementations for the javax.net.ssl package. If, due to
# export and/or import regulations, the providers are not allowed to be
# replaced, changing these values will produce non-functional
# SocketFactory or ServerSocketFactory implementations.
#ssl.SocketFactory.provider=
#ssl.ServerSocketFactory.provider=
# The Java-level namelookup cache policy for successful lookups:
# any negative value: caching forever
# any positive value: the number of seconds to cache an address for
# zero: do not cache
# default value is forever (FOREVER). For security reasons, this
# caching is made forever when a security manager is set.
# NOTE: setting this to anything other than the default value can have
# serious security implications. Do not set it unless
# you are sure you are not exposed to DNS spoofing attack.
#networkaddress.cache.ttl=-1
# The Java-level namelookup cache policy for failed lookups:
# any negative value: cache forever
# any positive value: the number of seconds to cache negative lookup results
# zero: do not cache
# In some Microsoft Windows networking environments that employ
# the WINS name service in addition to DNS, name service lookups
# that fail may take a noticeably long time to return (approx. 5 seconds).
# For this reason the default caching policy is to maintain these
# results for 10 seconds.
networkaddress.cache.negative.ttl=10
# Properties to configure OCSP for certificate revocation checking
# Enable OCSP
# By default, OCSP is not used for certificate revocation checking.
# This property enables the use of OCSP when set to the value "true".
# NOTE: SocketPermission is required to connect to an OCSP responder.
# Example,
# ocsp.enable=true
# Location of the OCSP responder
# By default, the location of the OCSP responder is determined implicitly
# from the certificate being validated. This property explicitly specifies
# the location of the OCSP responder. The property is used when the
# Authority Information Access extension (defined in RFC 3280) is absent
# from the certificate or when it requires overriding.
# Example,
# ocsp.responderURL=http://ocsp.example.net:80
# Subject name of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# distinguished name (defined in RFC 2253) which identifies a certificate in
# the set of certificates supplied during cert path validation. In cases where
# the subject name alone is not sufficient to uniquely identify the certificate
# then both the "ocsp.responderCertIssuerName" and
# "ocsp.responderCertSerialNumber" properties must be used instead. When this
# property is set then those two properties are ignored.
# Example,
# ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
# Issuer name of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# distinguished name (defined in RFC 2253) which identifies a certificate in
# the set of certificates supplied during cert path validation. When this
# property is set then the "ocsp.responderCertSerialNumber" property must also
# be set. When the "ocsp.responderCertSubjectName" property is set then this
# property is ignored.
# Example,
# ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
# Serial number of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# of hexadecimal digits (colon or space separators may be present) which
# identifies a certificate in the set of certificates supplied during cert path
# validation. When this property is set then the "ocsp.responderCertIssuerName"
# property must also be set. When the "ocsp.responderCertSubjectName" property
# is set then this property is ignored.
# Example,
# ocsp.responderCertSerialNumber=2A:FF:00

user564785 wrote:
I am trying to installl Oracle 11gR2 on VM machine with Redhat Linux 6-64bit. That is a Oracle database problem. Even though the Oracle product uses java it still represents a problem with that product (Oracle) rather than java. So you need to start with an Oracle database forum.

How to measure the baseline of a noisy, pulsed signal

Hi
I am measuring the torque exerted by a large motor on a shaft using a load cell and lever arm. The shaft runs at approx 150 rpm. I have attached a drawing that shows the output I get. This is a test rig.
I have written some code that measures the maximum peak out of a group of approx 5 peaks and writes this to a shift register. This gives me an idea of the maximum torque "spike".
I also wish to measure the baseline torque (due to the bearings in the machine). Even when highly filtered (my noise filter is set to 49Hz) the signal exhibits this noise which is probably due to vibration in the system. The signal is zeroed when the motor is not running.
Does anyone have an ideas on how to measure the "baseline" torque? The large spike in torque prevents me from doing a running average. Can anyone think of a way of averaging just the noisy part of the signal to get an average value? I aim to to subtract the average baseline torque from the peak value to get an idea of the torque due to the event which causes
the spike.
Any help would be greatly appreciated.
Many thanks.
Attachments:
drawing of torque signal.gif ‏26 KB

Thanks for the reply. I understand what you are saying. However, I might have to modify my method for measuring the peaks if I choose to implement your idea. I have taken a screenshot of my "peak finder" code and attached it.
Bascially, the reset terminal is wired to a timer which outputs a pulse every few seconds. This resets the vi (a standard NI one I think) and sets the peak magnitude back to zero. This way, I am windowing the signal and measuring the maximum peak in every window. This is what I need to do.
So I could use a logical filter to feed data to the running average only if;
the amplitude of the signal is less than a certain threshold
and if the current value has similar low peaks either side of it
How would you construct the code to delay the evaluation so that the values in front and behind of the current data point can be analysed?
thanks again
Attachments:
peak_find_screenshot.jpg ‏45 KB

Huey Pro calibrator- error message display measurement Error

i am using this huey pro calibration.. it had been a year without problem... but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please

>a nice NVidia card... Please help Adobe!
1a - what is the model nVidia card, and what is your driver version?
1b - for instance, I have a GTX 285 and driver 296.10
2a - aside from the occassional Adobe employee, this is a user to user forum, not Adobe suport
2b - how to contact Adobe...
Adobe contact information
http://www.adobe.com/support/contact
In the US - Adobe General support 800-833-6687 M-F 5am-7pm Pacific
In the US - Adobe Install Problems 800-642-3623
In the US - Adobe Activation 866-772-3623 Open 24/7

Huey Pro Calibration Error message- measurement error

i need using this huey pro calibration for year. but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please?

Hi,
Which Wireless-Card you used?
Best you use the Cisco CB21AG PCMCIA Card. I had similar problems with intel wireless chipsets
Sincerely,
Frederik

A fatal error has been detected by the Java Runtime Environment:

when i start up the eclipse, it comes out the problem.
i think it is an ordinary problem here , but i just can solve it for i tried several times...here is main the error log below:
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007f35050fcdda, pid=4191, tid=139865686824704
# JRE version: 6.0_37-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.12-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x4badda] instanceKlass::method_with_idnum(int)+0x2a
i know it's something wrong with the frame , maybe solved by manual the eclipse.ini, but how?

982103 wrote:
i think it is an ordinary problem hereA native crash is anything but an ordinary problem. Somewhere in some native module, something goes wrong. It is even likely that it is in a module that is in no way related to Java.

How to measure error on peak detect?

Similar Messages

Maybe you are looking for