Making use of LightningDataModule and simplification of data loading

This merge request adds LightningDataModule to better organize the code and make better use of lightning's features. This centralizes common tasks such as DataLoader creation and application of transforms into a base class to be inherited from.

Data loading was also simplified by removing custom Sample classes and maker functions, and the addition of RuntimeDataset and CachedDataset.

Remaining tasks:

• (@dcarron) Create a common/default DataModule for the shenzhen dataset that takes protocols and transforms as parameters to avoid copying code for each protocol configuration
• (@dcarron) Add typehints to ShenzenDataModule
• (@dcarron) Investigate issue where training a new model with ElasticDeformation as a transform converges more slowly if the data is not cached.
• (@andre.anjos) Update documentation on ShenzenDataModule
• (@biosignal) Update all datasets, using Shenzhen as a reference
  • (@mdelitroz) Montgomery
  • (@mdelitroz) Hivtb
  • (@andre.anjos) Indian
  • (@andre.anjos) Padchest
  • (@mdelitroz) Tbpoc
  • (@andre.anjos) tbx11_simplified -> renamed as tbx11k, protocol v1 (uses original dataset organisation)
  • (@andre.anjos) tbx11_simplified_v2 -> renamed as tbx11k, protocol v2 (uses original dataset organisation)
  • (@andre.anjos) mc_ch -> renamed as montgomery-shenzhen
  • (@andre.anjos) mc_ch_in -> renamed as montgomery-shenzhen-indian
  • (@andre.anjos) mc_ch_in_11k -> renamed as montgomery-shenzhen-indian-tbx11k-v1
  • (@andre.anjos) mc_ch_in_11k_v2 -> renamed as montgomery-shenzhen-indian-tbx11k-v2
  • (@andre.anjos) mc_ch_in_pc -> renamed as montgomery-shenzhen-indian-padchest
  • (@andre.anjos) nih_cxr14_re -> renamed as nih-cxr14 (n.b.: multi-class dataset, radiological findings)
  • (@andre.anjos) nih_cxr14_re_pc -> renamed as nih-cxr14-padchest
• (@dcarron) Update models
• (@dcarron) Update evaluation scripts
• (@dcarron) Update support for extra_validation datasets
• (@biosignal) Update full documentation
• (@biosignal) Update unit tests

Addresses the following issues:

• Closes #14 (closed)
• Closes #18 (closed)
• Closes #19 (closed)
• Closes #21 (closed)
• Closes #29 (closed)

src/ptbench/utils/resources.py

@@ -100,7 +100,7 @@ def gpu_constants():
     """
     return run_nvidia_smi(
         ("gpu_name", "driver_version", "memory.total"),
-        ("gpu_name", "gpu_driver_version", "gpu_memory_total"),
+        ("gpu_name", "gpu_driver_version", "gpu_memory_total_GB"),
     )
 
 
@@ -135,10 +135,10 @@ def gpu_log():
             "utilization.gpu",
         ),
         (
-            "gpu_memory_total",
-            "gpu_memory_used",
-            "gpu_memory_free",
-            "gpu_percent",
+            "gpu_memory_total_GB",
+            "gpu_memory_used_GB",
+            "gpu_memory_free_percent",
+            "gpu_usage_percent",
         ),
     )
 
@@ -165,7 +165,7 @@ def cpu_constants():
         1. ``cpu_count`` (:py:class:`int`): number of logical CPUs available
     """
     return (
-        ("cpu_memory_total", psutil.virtual_memory().total / GB),
+        ("cpu_memory_total_GB", psutil.virtual_memory().total / GB),
         ("cpu_count", psutil.cpu_count(logical=True)),
     )
 
@@ -245,9 +245,9 @@ class CPULogger:
                 # at this point, but ensures to update counts later on
                 gone.add(k)
         return (
-            ("cpu_memory_used", psutil.virtual_memory().used / GB),
-            ("cpu_rss", sum([k.rss for k in memory_info]) / GB),
-            ("cpu_vms", sum([k.vms for k in memory_info]) / GB),
+            ("cpu_memory_used_GB", psutil.virtual_memory().used / GB),
+            ("cpu_rss_GB", sum([k.rss for k in memory_info]) / GB),
+            ("cpu_vms_GB", sum([k.vms for k in memory_info]) / GB),
             ("cpu_percent", sum(cpu_percent)),
             ("cpu_processes", len(self.cluster) - len(gone)),
             ("cpu_open_files", sum(open_files)),