The process of opening a report in the application involves a great deal of calculations in order to aggregate all the entries and then generate the display of the report. Most of the statistical bar graphs and tables are quick to generate, but the composited pain maps will generally take some time to process and display. The composited body maps are very helpful in showing where you experienced the most pain over the course of the report, but they are also computationally expensive and take some time to process.
Users running Chronic Pain Tracker on older devices may prefer to adjust how these images are created. We offer two options for adjusting the composite image generation process.
First, you can turn off the automatic generation of these images. By default, the compositing process will begin whenever a report summary page is viewed. By changing the automatic generation to OFF, reports will defer the compositing process. Instead of the composited images, the summary page will show the \"Generate Composite Images\" icon shown below. You can now flip through your reports as needed. If you want to generate the composite image pain map, simply tap the icon and the images will be generated.

Additionally, you can adjust the quality level of the composited images. The preference for this option allows you to select Low, Medium, or High settings for the composited images. Older devices should use the Low setting, while users with newer devices can experiment and see which option provides the best balance between quality and speed of generation.
\r\n
Finally, v2.5.2 of Chronic Pain Tracker introduced an image caching feature which improves performance when viewing reports multiple times. Basically, this feature will cache the generated composite images for any reports you've viewed. Then, if you come back and view those same reports, the cached image can be displayed, rather than having to regenerate the composite from scratch. This feature functions automatically, so there's nothing required to activate it. The image cache is emptied whenever you restart the application or when the pain entry data is modified.