32-bit limitation and how to deal with it
1. A short explanation
The requirement for coDiagnostiX to run is a 64-bit processor running a 64-bit Windows operating system, yet coDiagnostiX is still in parts a 32-bit program. This comes with certain drawbacks. Most notable, the amount of main memory (RAM) that can be addressed and used. Due to this technical design limitation, the amount of main memory that can effectively be used is just above 2 GB. When dealing with high-resolution image data and 3D models, this limitation can be reached, leading to crashes during the DICOM import and more often during guide creation.
The average PC these days is equipped with much more RAM (16-32 GB) but coDiagnostiX currently cannot take advantage of that due to the 32-bit limitation.
We are working on a full 64-bit transition with high priority, but it is still some time off as of early 2024.
Here are two examples of error messages, often but not exclusively associated with the 32-bit memory restriction.
Please note, the first warning message can be misleading, as the reason can be that there is truly not enough main memory available in the system or, as discussed, the 32-bit memory limitation has been reached. This can be assessed by a look into Windows Task Manager.
2. During DICOM import
If the DICOM data you like to use is too high resolution, coDiagnostiX can crash. As a workaround, please try to reduce the data by excluding slices that are not necessary for the planning.
This can be accomplished by narrowing the range of the scan. You can do so by excluding all slices falling outside the range.
Or by removing every other slice within the range, which will effectively double the spacing between slices. So please make sure the dataset input requirements are still met. (A scan’s slice and pixel spacing values MUST be between 0.05 mm and 0.5 mm.)
To do this before the import in coDiagnostiX, please use a DICOM viewer of your choice.
3. During guide creation
During guide creation, the 32-bit memory related crashes can occur more often. The following steps can help to get around the issues. They are best used in combination when dealing with very complex cases.
a) Restart coDiagnostiX and go straight to the case you would like to work with. This is often enough to stay below the memory limit. Especially if you have previously switched between cases, when the crash occurred.
b) Create a plan copy and delete for the current guide design unnecessary 3D models. Only leave in the plan what is absolutely necessary to accomplish the intended guide design.
c) Create a plan copy and reduce the mesh of the 3D models necessary for the guide
design.
Select “Edit Mesh…” to go to the mesh editor
The red numbers for point and triangle count are an indicator for a very complex 3D model
With the “Reduce” function, the mesh can easily be reduced to a more manageable complexity