Troubleshooting - mwgeurts/viewray_fielduniformity GitHub Wiki

The following content provides information to help users troubleshoot issues with this application as well as known resolutions to common problems. If you continue to experience difficulties, contact the author or submit your question or bug to the Issues Tracker.

Contents

Submodule Does Not Exist

This application uses git submodules during execution. If a submodule is not present, the application will throw an error similar to the following. This commonly occurs if the application was installed by downloading the git archive or executing git clone without the --recursive flag. To resolve this issue, reinstall the application according to the Installation and Use instructions.

The CalcGamma submodule does not exist in the search path. Use  git 
clone --recursive or git submodule init followed by git submodule 
update to fetch all submodules

Toolbox Cannot be Found

This application requires several MATLAB Toolboxes (see Software Compatibility for a list of all required Toolboxes) and will throw an error similar to the following if not found. To resolve this error, the prerequisite toolboxes must be installed and the application restarted.

The Statistics and Machine Learning Toolbox cannot be found and is 
required by this function.

Undefined Function 'corr'

In prior versions of this application, if the Statistics Toolbox was not installed, the application would fail when loading data with the following error. To resolve this error, the Statistics Toolbox must be installed and the application restarted.

Undefined function 'corr' for input arguments of type 'double'.

Error Using dicominfo

If the application cannot find the reference data, the dicominfo function will fail an error similar to the following. To resolve this error, copy the referenced file into the reference folder and restart the application.

Error using dicominfo>getFileDetails (line 394)
File "AP_27P3X27P3_PlaneDose_Vertical_Isocenter.dcm" not found.

Application Log

This application records key input parameters and results to a log.txt file using the Event() function. The log is the most important route to troubleshooting errors encountered by this application. Each new event is appended to this file. The log is formatted as three tab-separated columns; the first contains the local date and time (YYYY-MM-DD hh:mm:ss format), the second is the event type, and the third is the event text. The event types are listed in the following table:

Event Description
INIT The first event logged when the application is first initialized. Includes the application name, version, author, operating system, MATLAB version, Java version, and GPU card information (if available)
INFO Most events are informative events, which occur during regular execution of the application code.
WARN Warning events log unexpected but recoverable actions that occur during application execution.
ERROR Error events are accompanied with a MATLAB exception getting thrown. The contents of an error log event typically include the file trace captured by the function call getReport(MException, 'extended', 'hyperlinks', 'off')
UNIT Unit testing events record additional information captured during automated unit testing. These events do not occur during typical application use.
CHCK Check code events are recorded when Code Analyzer Messages are identified during the checkcode() unit test.