Recent Posts

Pages: [1] 2 3 ... 10
Ito ay isang forum. Tindahan ng Kaalaman Hindi ko alam kung saan hahanapin ito.
Hi Yvonne,

What this is saying is that 100% of your samples had an uncertainty greater than 1%. It would appear that the current range setting for the idle worket is set too high for the interval. Try editing the range setting for idle in the SERT GUI power analyzer options or by editing listners.xml. It should be set to the average value reported during test, or in this instance what you see on the analyzer when there is no activity on the SUT.

More information can be found at

The following is an excerpt from section 2.6:
"For compliant SPECpowerbenchmark runs, specific uncertainty requirements have to be guaranteed according to  the SPECpower  Run  and  Reporting  Rules.  The  uncertainty  of  a measured  power value depends on how well the configured volt and ampere ranges fit to this value. The formulas to calculate the uncertainty often directly include the configured volt and ampere ranges. Selecting the volt range is quite easy as the voltage depends only on the power source and does not change during the test. Selecting the ampere range is more complex, because it differs with the SUT’s power  consumption  during  the  benchmark  run.  A  large  difference  between  different  load  levels  may even require individual ampere range settings for each level. PTDaemon  has  the  ability  to  select  the  closest  range  appropriate  for  a  requested  value.    The information is maintained on a per-analyzer basis.  For example, if you specify a range of 2.2A and the analyzer  in  use  has  ranges  of  0.5,  1.0,  2.0  and  5.0A,  PTDaemon  will  set  the  analyzer  to  the  5.0A range."
SERT / NVALID: [YokogawaWT310 (power_localhost_8890_0)] Idle:Idle:idle: The power analy
« Last post by Yvonne on February 25, 2020, 01:29:22 AM »
My test result got a problem, it's show"INVALID: [YokogawaWT310 (power_localhost_8890_0)] Idle:Idle:idle: The power analyzer had 100.0% samples with uncertainty of more than 1%, exceeding the threshold of 5.0%" , can you give me some suggestion , thanks so much.
Your knowledge allows me to move on, no matter how much trouble.
Hi Greg,

I figured out that by saving the new client configurations file to the original location as the default one solves the problem. Thanks for the help.

  <xi:include href="C:\Users\Administrator\Desktop\Sert2 data\client-configurations-2_4.xml"/>
  <xi:include href="C:\Users\Administrator\SERT-2.0.2\client-configurations-2_4.xml"/>
I'm not quite sure what's happening.  It could be a file permissions issue but that's just a wild guess. 

I'd recommend submitting a SERT support ticket at
Make sure you attach the output of the collectlogfiles script from the controller system to the ticket; that gives us a large amount of debug information that should help to resolve the issue.

SERT / Re: Question about SERT use for EU 2019/424
« Last post by Mike Petrich on February 12, 2020, 11:31:52 AM »
Hi Mark,

You can read more on the metrics difference between SERT1 and SERT2 here: Ultimately it is up to the regulatory body on which data they accept.
SERT / Re: Error / Invalid / Signature validation failed
« Last post by Mike Petrich on February 12, 2020, 09:37:28 AM »
I believe this was resolved via a support ticket and was the result of a SERT version mismatch between the director and SUT. Please let me know if you require further assistance. Thanks!
SERT / Re: CPU Transactions per second numerical instability for SERT
« Last post by Mike Petrich on February 12, 2020, 09:33:34 AM »
Hi Greg

SERT 2.0.1
CPU Intel(R) Xeon(R) Silver 4209T CPU 6g@ 2.20GHz  x 2pcs
Memorry Samsung,K4A8G085WB,DDR4,21300(2666MHz),8GB,Register,Montage,19,by 8,1 rank,MP, NA,NA,NA  x 16pcs
SSD Samsung MZ7LM960HCHP-000AZ SSD,SATAIII,960GB,SATAIII,2.5 - 7mm,6Gb/s,NA_1,NA_1,NA_1, 960G x 2pcs

Hi Ian, I'm sorry you're having issues running SERT. My initial suggestion would be to try to recreate on the latest version on SERT. Instructions for updating SERT2 can be found here:

If this doesn't resolve your issue, it might be beneficial to open a support ticket including some debug data via the collectlogfiles script. Details on this process can be found here:
Hi Greg,

Thanks for the understanding

I'm running a "Full Test Suite", but this issue appear in "Range Discovery" run as well

not sure what you mean by local file, basically I downloaded the latest client configuration by using "Download latest with browser"button, saved it as "client-configurations-2_4.xml" on my local desktop and then loaded it one using "load local file" (see image attached)

Below is what in "xi:inlude" info in config-all.xml
         <xi:include href="C:\Users\Administrator\Desktop\Sert2 data\client-configurations-2_4.xml"/>
               <xi:include href="custom-configurations.xml"/>
Pages: [1] 2 3 ... 10