We would just like to ask regarding the computation of the Weighting Factor (which is AvgElapsed/AvgTrigger), why is it that the AvgElapsed is in milliseconds and the AvgTrigger is in seconds.
Hi Sean! You did interpret that correctly, after revising the code and the Excel Formulas, there is an error within this lab. As you have pointed out there AvgElapsed is in milliseconds and the AvgTrigger is in seconds. However this is technically correct, the units of the “WeightingFactor” don’t matter at all since it is only intended as a metric to be compared to other values in the “WeightingFactor” column. We’re dividing execution time by time between executions, so shorter intervals between executions results in a higher weighting factor.
Hi Sean! From the Optimizing Asset Analytics - Analysis of Performance Statistics class we see that the PowerShell creates this excel document using all milliseconds. Theoretically, both AvgElapsed and AvgTrigger are usually observed in milliseconds however it could be possible for those to be visualized in seconds. Does your code match what is seen on page 10 section 5 of the student manual?
Hi Jeff! Thank you for the reply
We noticed that the AvgTrigger (which is computed by dividing DataDuration and Execution count) is in millisecond and the AvgElapesed is in seconds from the PowerShell script
Did we interpret this correctly?
Understood Jeff! Thank you for your time and clarifications on this matter!Have a great week
Retrieving data ...