Differences

This shows you the differences between two versions of the page.

--- electronrt:userguide:userguide [2022/06/03 15:40] – [Application Usage] dpatenaude
+++ electronrt:userguide:userguide [2023/03/09 20:59] (current) – [General] dpatenaude
@@ Line 101: / Line 101: @@
 |  3  | All                          | Random Application Crashes:<WRAP>
   * If the [[electronrt:instructions_for_use:instructions_for_use#network_local_data_cache|local or network disk cache]] becomes corrupted the application may crash at seemingly random places while calculations are computing. Clearing the [[electronrt:userguide:tutorials:all_tutorials#local_disk_cache|local disk cache]] within the application settings may help resolve unreproducible application crashes during calculations running.
+</WRAP>|
+|  4  | All                          | Network patient database:<WRAP>
+  * If the application is set to use a [[electronrt:instructions_for_use:instructions_for_use#patient_database_file_storage|network patient directory]] shared with multiple users there may be a risk for 'database is locked' errors. This is due to the application using SQLite as it's database engine, which does not robustly support concurrent database users and reading/writing. While normal usage between one or two users may not pose a problem with this, having a significant number of users simultaneously accessing the network database or the following scenarios can cause the database to lock and throw this error:
+    * The application crashes or a network connection is interrupted during a SQL commit that allows the 'unlock' step to be missed OR
+    * The file is locked due to other network usage (e.g.: the file is in use by an external service such as an Antivirus scan, backup, etc) OR
+    * Multiple simultaneous users are attempting to read/write to the database at the same time
+  * If you receive the error "database is locked" you'll have to wait and try again once the database is unlocked
+</WRAP>|
+|  5  | All                          | Application fails to load computed data: Under the following scenario, the application request and state handling has a known bug that results in computed data not loading within the application until a application close and re-open is performed:<WRAP>
+  * A patient/plan is opened and a user interface or task is opened
+  * Data begins computing (e.g.: a dose, beam, or device)
+  * While the data is computing the user navigates to another user interface within the application
+  * If the data finishes computing for the first user interface while the user is navigated to a new user interface and then the user navigates back to the first user interface, the application may not know the data is computed to display or use the results.
 </WRAP>|
 ==== DICOM Import ====
@@ Line 106: / Line 119: @@
 ^ ID  ^ Affected Version(s)  ^  Description   ^
 | 1 | All                  | Closing the application immediately after importing a DICOM patient and before the job 'copy_imported_dicom_files_to_course' completes will cause an incomplete CT Image Set when exporting DICOM later in the application. |
-| 2 | 0.9.0+               | Only plan files with a valid bolus in at least one beam will import properly. |
+| 2 | 0.9.0                | Only plan files with a valid bolus in at least one beam will import properly. |
 ==== DICOM Export ====