ianalyze-AppStart report: How long it took to show the login screen
After the user double-clicks the IMPAX Client executable, the user is presented with the login window, which produces the AppStart->Begin and AppStart->End log entries in client_performance.log file. ianalyze locates the entries, calculates the time difference between the two entries, and writes the information to the ianalyze-AppStart.txt report. For example:
TUID,EventType,StartTime,EndTime,ElapsedTime,NumberOfWorklists 2219125152-4C926C3A-1,AppStart,2010-09-16 15:12:58.276,2010-09-16 15:13:00.112,1836,-1
In the above example, it took 1836 milliseconds to show the login screen. As the NumberOfWorklists is not relevant when starting the IMPAX Client, the result is shown as -1.
 | Note: If the Client is started multiple times, multiple AppStart->Begin and AppStart->End entries appear in the Client performance log, resulting in multiple AppStart calculations in the ianalyze-AppStart.txt report. ianalyze determines which AppStart->Begin entry belongs to which AppStart->End entry by matching the two log entries’ Transaction UIDs. |
ianalyze-Cycle report: How long it took to Cycle one or more Reports
The time the user started to cycle reports, to the time the reports have completed to cycle, produces the Cycle->Begin and Cycle->End entries in the client_performance.log file. ianalyze locates the entries, calculates the time difference between the two entries, determines if reports are being cycled, and writes the information to the ianalyze-Cycle.txt report. For example:
DateTimeStart,DateTimeEnd,CycleType,TUID,TimeElapsed 2010-09-28 15:12:14.331,2010-09-28 15:12:15.684,Reports,1AA029B848-4CA23DEA-18,1353
In the above example, it took 1353 milliseconds to cycle the reports.
ianalyze-Generic report: Time to populate all Image Area widgets
The elapsed time from when the user double-clicks a study in List area (or opens studies using other methods) until all images are received for all widgets on all screens, produces the Generic->Begin, Generic->End, and Generic->Step entries in the client_performance.log file. ianalyze locates the entries, calculates the time difference between the Generic->Begin and Generic->End entries, extracts information from various fields, and writes the information to the ianalyze-Generic.txt report. For example:
DateTimeStart,TUID,DateTimeLastStep,TimeElapsed,InfoFields,Type
2010-10-22 11:46:55.719,2219125152-4CC1B159-7,2010-10-22 11:47:01.477,5758,elapsed(ms)=5758;patientID=A;firstStudyModality=MG;CRMevent=Event{class[CRM_changed_post_screen_refresh_event_class]:NAV[nav_type_Set]:Mode[]:RMT[]},user_action_DisplayPatient
In the above example, it took 5758 milliseconds to display a patient