STYLE: Remove all trailing whitespaces

Updates were done leveraging the `end-of-file-fixer`, `mixed-line-ending`
and `trailing-whitespace` pre-commit hooks.

Content of the corresponding `.pre-commit-config.yaml`:

```
repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: "v5.0.0"
    hooks:
      - id: check-case-conflict
      - id: check-merge-conflict
      - id: check-symlinks
      - id: check-yaml
      - id: end-of-file-fixer
        exclude: "\\.(svg)$"
      - id: mixed-line-ending
        exclude: "\\.(svg)$"
      - id: trailing-whitespace
        exclude: "\\.(svg)$"
```

.github/ISSUE_TEMPLATE/project.yml

@@ -14,7 +14,7 @@ body:
     description: Select whether the project is ready to be created once this issue is submitted.
     options:
       - Ready - team will start page creating immediately
-      - Draft - team will hold off on page creation  
+      - Draft - team will hold off on page creation
   validations:
     required: true
 

.github/ISSUE_TEMPLATE/proposal.yml

@@ -12,4 +12,3 @@ body:
     description: Please provide a brief overview of the project, including the problem it aims to solve, and any expected outcomes.
   validations:
     required: true
-

.github/advanced-issue-labeler.yml

@@ -6,4 +6,4 @@ policy:
           - name: 'draft'
             keys: ['Draft - team will hold off on page creation']
           - name: 'ready'
-            keys: ['Ready - team will start page creating immediately']
+            keys: ['Ready - team will start page creating immediately']

.github/workflows/draft-to-ready.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       issues: write
-    
+
     steps:
       - name: Add "ready" label
         uses: actions/github-script@v6
@@ -23,4 +23,4 @@ jobs:
               owner: context.repo.owner,
               repo: context.repo.repo,
               labels: ["ready"]
-            })
+            })

.github/workflows/issue-labeler.yml

@@ -33,4 +33,4 @@ jobs:
           block-list: |
             None
             Other
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/project-page-pull-request.yml

@@ -75,7 +75,7 @@ jobs:
         echo "directory_name [$directory_name]"
 
         echo "name=$directory_name" >> $GITHUB_OUTPUT
-        
+
     - name: Check if project already exists
       id: check_project_exists
       run: |
@@ -96,13 +96,13 @@ jobs:
           ## Project Page Pull Request Creation
           :stop_sign: **STOPPED**: Project already exists
         edit-mode: replace
-    
+
     - name: Create project directory
       run: |
         event_name=${{ steps.event_info.outputs.name }}
         directory_name=${{ steps.project_directory.outputs.name }}
         mkdir $event_name/Projects/$directory_name
-    
+
     - name: Bulk issue body
       id: bulk
       env:
@@ -124,7 +124,7 @@ jobs:
           '/^### Progress and Next Steps/' \
           '/^### Illustrations/' \
           '/^### Background and References/' \
-          -f ${{ runner.temp }}/project_pull_request_part_ -b "%02d.md"    
+          -f ${{ runner.temp }}/project_pull_request_part_ -b "%02d.md"
 
     - name: Cleanup files
       run: |
@@ -136,18 +136,18 @@ jobs:
         cat ${{ runner.temp }}/project_pull_request_part_06.md | sed "1 d" > ${{ runner.temp }}/background.md
 
     - name: Display clean files
-      run: | 
-        echo "Description:"       
+      run: |
+        echo "Description:"
         cat ${{ runner.temp }}/description.md
-        echo "Objective:"       
+        echo "Objective:"
         cat ${{ runner.temp }}/objective.md
-        echo "Approach:"       
+        echo "Approach:"
         cat ${{ runner.temp }}/approach.md
-        echo "Progress:"       
+        echo "Progress:"
         cat ${{ runner.temp }}/progress.md
-        echo "Illustrations:"       
+        echo "Illustrations:"
         cat ${{ runner.temp }}/illustrations.md
-        echo "Background:"       
+        echo "Background:"
         cat ${{ runner.temp }}/background.md
 
 
@@ -263,4 +263,3 @@ jobs:
             repo: context.repo.repo,
             name: ["project:create"]
           })
-

.gitignore

@@ -5,4 +5,4 @@ Gemfile.lock
 .DS_Store
 
 .idea/
-.vscode/
+.vscode/

CNAME

@@ -1 +1 @@
-projectweek.na-mic.org
+projectweek.na-mic.org

MAINTAINERS.md

@@ -1,6 +1,6 @@
 # Creating the main page for a new project week
 
-Use changes in these commits as guides: 
+Use changes in these commits as guides:
 - https://github.com/NA-MIC/ProjectWeek/commit/9fb0d047ad1ca9a7692edcfe7ac9903b646ec15c
 - https://github.com/NA-MIC/ProjectWeek/commit/f9163343e86c4cb8ea51801c27244f2045568a1a
 

PW26_2017_London_Canada/README.md

@@ -1,24 +1,24 @@
 ![PW26](PW26.png)
 ## Welcome to the web page for the 26th Project Week!
 
-It is a pleasure to announce that the Western Slicer Project Week will be held in London, Ontario, Canada on July 17-21, 2017. This is the first extension Slicer project week that grew organically from a proposed visit of Dr. Nobuhiko Hata to Western. Enough interest existed to propose a small Slicer hackfest, which quickly grew into a full blown project week. With the expansion of the hackfest into a full project week, an additional meeting was arranged in conjunction with SPWW to discuss and develop image-guided therapy specific goals. Thus, this is also the inaugural Slicer IGT Project Week. 
+It is a pleasure to announce that the Western Slicer Project Week will be held in London, Ontario, Canada on July 17-21, 2017. This is the first extension Slicer project week that grew organically from a proposed visit of Dr. Nobuhiko Hata to Western. Enough interest existed to propose a small Slicer hackfest, which quickly grew into a full blown project week. With the expansion of the hackfest into a full project week, an additional meeting was arranged in conjunction with SPWW to discuss and develop image-guided therapy specific goals. Thus, this is also the inaugural Slicer IGT Project Week.
 This project week is an event endorsed by the MICCAI Society.
 
 ![GroupShot](GroupShot.jpg)
 
 ## Local Organizing Committee
- 
+
 - Host: [Terry Peters](http://www.robarts.ca/terry-peters), Robarts Scientist; Professor Medical Imaging; Medical Biophysics; Biomedical Engineering
 
 - Email Local Organizing Committee:
   - [Adam Rankin, Terry Peters, Jackie Williams](mailto:[email protected],[email protected],[email protected][email protected]&subject=ProjectWeek29)
 
 
 ## Resources
-This is a collection of resources submitted by attendees 
+This is a collection of resources submitted by attendees
 - Welcome presentation by Andras Lasso
 - Historical overview by Nobuhiko Hata
-- Python resources (thanks John Drozd!) 
+- Python resources (thanks John Drozd!)
   - http://cscircles.cemc.uwaterloo.ca/5-input/
   - https://www.jetbrains.com/pycharm/
   - http://www.datacarpentry.org/python-ecology-lesson/
@@ -77,16 +77,16 @@ Automated Segmentation of the human skull, face and airways from MRI dicom image
 
 ### Breakout sessions
 
-+ 3D Slicer introduction 
++ 3D Slicer introduction
   + 3D Slicer features overview (Andras Lasso)
-+ Segmentation 
++ Segmentation
   + Segment editor tutorials (video tutorial and slides)
   + Segment editor reference manual
-+ Slicelets 
++ Slicelets
   + Customizing 3D Slicer: slicelets/guidelets (Andras Lasso)
   + Slicer programming tutorial
   + VASST Lab Slicelet Template (Thanks Ying Li!)
-+ SlicerIGT 
++ SlicerIGT
   + PerkLab videos
 
 ## Registrants
@@ -206,5 +206,3 @@ Automated Segmentation of the human skull, face and airways from MRI dicom image
 57 John Baxter (Robarts Research Institute)
 
 58 Jean-Christophe Fillion-Robin (Kitware, Inc.)
-
-

PW27_2018_Boston/BreakoutSessions/AR-VR.md

@@ -32,7 +32,7 @@ Back to [Breakout Sessions List](../README.md#BreakoutSessions)
   - By simulating mouse interactions all the effects could be used
   - New effects
     - Surface deformation: Grow ROI on segment surface then push or pull with modification function (VR possibly makes it actually usable by allowing quick evaluation of the result while changing the input, and seeing all in real 3D with depth)
-    
+
 - **Discussion**
   - Sam Jang recommendations: Keep focus on the model, not fly around; rotate or walk around; keep actions very consistent.
   - If elbow and wrist rests on some gel pad then fine manipulation is feasible
@@ -51,7 +51,7 @@ Back to [Breakout Sessions List](../README.md#BreakoutSessions)
   - From @curtislisle:
 During the VR interaction session at the recent Project Week, we discussed interaction modes.  I was reminded of early research by some former colleagues at Univ. of Central Florida.  Here is a URL and Bibliography to some of the work that might be of interest:
 https://www.mitpressjournals.org/doi/abs/10.1162/pres.1995.4.4.403
-This is the work I described about selecting a nearby object to establish a coordinate system transformation and move the world with respect to the eyepoint instead of flying the eyepoint towards the target object.  The point was made about simulation sickness when moving the eyepoint, but our lab's work indicated this paradigm of direct manipulation of the virtual environment was effective. 
+This is the work I described about selecting a nearby object to establish a coordinate system transformation and move the world with respect to the eyepoint instead of flying the eyepoint towards the target object.  The point was made about simulation sickness when moving the eyepoint, but our lab's work indicated this paradigm of direct manipulation of the virtual environment was effective.
 Some literature search of the PRESENCE journal might help us take advantage of some of  the earlier work.    It is nice to see that rendering and VR technology is finally more widely accessible.
 
 
@@ -68,7 +68,7 @@ Some literature search of the PRESENCE journal might help us take advantage of s
   - Orientation marker
 
 ### Proposed changes
-  
+
 - Excluding VR view from main layout management: Node reference parentLayoutNodeID in view nodes
   - None by default, meaning main layout. Set to node (e.g. itself) to indicate it's standalone and should not be managed
   - Abstract layout node class

PW27_2018_Boston/BreakoutSessions/FDA-and-3D-Slicer.md

@@ -23,7 +23,7 @@ The Slicer license allows commerial use:
 > The license does not impose restrictions on the use of the software.
 > 3D Slicer is NOT FDA approved. It is the users responsibility to ensure compliance with applicable rules and regulations.
 
-Open source software can be included in the package being registered, it's helpful to isolate modules/classes that are used. Testing has to incorporate verifying the functionality of that software. 
+Open source software can be included in the package being registered, it's helpful to isolate modules/classes that are used. Testing has to incorporate verifying the functionality of that software.
 
 ### 510(k)
 
@@ -46,7 +46,7 @@ In the Software section of the 510(k) application you have to provide:
 * Requirements Specification: developed from Clinical User Needs and Design Input
 * Software Design Document
   * Includes module level descriptions for the software
-  * Includes third party libraries: 
+  * Includes third party libraries:
 
 | Name    | Description | How Used in the Software |
 | ------- | ----------- | ------------------------ |

PW27_2018_Boston/PreparatoryMeetingsNotes.md

@@ -47,7 +47,7 @@ These are notes from PW#27 Preparation Hangouts held weekly on Tuesdays at 10am
 
 * Main topic: Gran Canaria Team projects
 * Administrivia: should we use this to help people copy the template page to make their own project page? https://www.mediawiki.org/wiki/Extension:Duplicator
-* Discourse sub community? 
+* Discourse sub community?
   * Subscribe, see the welcome page below. google, github, Facebook are all supported authentication options so people can one-click use their existing accounts if they want:
   * https://discourse.slicer.org/t/welcome-to-the-3d-slicer-forum/8
   * After logging in, visit: https://discourse.slicer.org/c/community/project-week, and click the “Watching” button to enable notifications:

PW27_2018_Boston/Projects/3DPrintedProstateCancerModels/README.md

@@ -9,7 +9,7 @@ Key Investigators
 - William Huang (NYU School of Medicine)
 - Andrey Fedorov (BWH, HMS)
 - Danielle Pace (MIT) (has put together a pipeline for preparing 3d printed models before, happy to share experience)
-- Anneke Meyer (University of Magdeburg, Germany) 
+- Anneke Meyer (University of Magdeburg, Germany)
 
 
 # Project Description
@@ -34,7 +34,7 @@ urethra,and rectal wall.
 
 ## Progress and Next Steps
 
-1. Learned and tested 3D Slicer segmentation tools.  Compared surface cut tool to manual segmentation and grow from seeds.  
+1. Learned and tested 3D Slicer segmentation tools.  Compared surface cut tool to manual segmentation and grow from seeds.
 
 2. Continue to work on workflow for segmentation and printing- discuss with Danielle Pace.
 
@@ -47,5 +47,3 @@ urethra,and rectal wall.
 
 * Wake N, Chandarana H, Huang WC, Taneja SS, Rosenkrantz AB. Application of anatomically accurate, patient-specific 3D printed models from MRI data in urological oncology. Clin Radiol. 2016;71(6):610-4. http://dx.doi.org/10.1016/j.crad.2016.02.012. http://www.clinicalradiologyonline.net/article/S0009-9260(16)00087-8/fulltext
 * Wake N, Rude T, Kang SK, et al. 3D printed renal cancer models derived from MRI data: application in pre-surgical planning. Abdom Radiol (NY). 2017;42(5):1501-9. http://dx.doi.org/10.1007/s00261-016-1022-2. https://link.springer.com/article/10.1007/s00261-016-1022-2
-
-

PW27_2018_Boston/Projects/AffordableIGTSimulatorsWithSlicerIGTAndPLUS/README.md

@@ -29,7 +29,7 @@ In this project we aim at creating and integrating an Image Guided Therapy (IGT)
 ## Approach and Plan
 
 1. Define a proper ArUco optical tracker system (web camera and markers selection and distribution).
-2. Program the integration of the tracked probe in the ultrasound simulator device included in PLUS Toolkit. 
+2. Program the integration of the tracked probe in the ultrasound simulator device included in PLUS Toolkit.
 3. Implement strategies for track accuracy improvement.
 4. Replace the default model simulated in the PLUS device with a custom arm model.
 5. Test and verify the overall system.
@@ -38,12 +38,12 @@ In this project we aim at creating and integrating an Image Guided Therapy (IGT)
 
 <!--Describe progress and next steps in a few bullet points as you are making progress.-->
 
-1. The system setup (camera and trackers, probe, needle, phantom block, etc.) was tested and successfully completed. 
+1. The system setup (camera and trackers, probe, needle, phantom block, etc.) was tested and successfully completed.
 2. We confirm that the camera auto-focus is not suitable for tracking. Webcam models without this facility should be considered in the future.
 3. The pivot and spin calibrations for needle-like tools and the fiducial calibration of bodies yield an accuracy good enough  for training applications and no strategies for track accuracy improvement was needed. Without actual ultrasound images, manual calibration of probe was required.
 4. Instead of the arm model, we create a very simple one based on basic geometrical shapes. However, the proof of concept for customizing any particular case is done.
 5. Unfortunately, the calibration of the US simulator failed. The prescribed spatial model seems to mismatch with the actual and virtual scenarios. Therefore the US image does not correspond to the expected one. This should be checked and fixed in the next few days.
-   
+
 
 # Illustrations
 

PW27_2018_Boston/Projects/CHRIS-slicer/README.md

@@ -38,7 +38,7 @@ Back to [Projects List](../../README.md#ProjectsList)
 pfurl --verb POST --raw --http ${HOST_IP}:5005/api/v1/cmd \
       --httpResponseBodyParse --jsonwrapper 'payload'     \
       --msg \
-'{   
+'{
       "action": "coordinate",
             "threadAction":     true,
             "meta-store": {

PW27_2018_Boston/Projects/CIPDeepLearningLungSegmentation/README.md

@@ -8,12 +8,12 @@ Back to [Projects List](../../README.md#ProjectsList)
 - Raúl San José (BWH)
 
 # Project Description
-Integrate a lung segmentation algorithm based on Deep Learning (Keras+Tensorflow) into the Chest Imaging Platform. 
+Integrate a lung segmentation algorithm based on Deep Learning (Keras+Tensorflow) into the Chest Imaging Platform.
 The goal is to make available in Slicer this and other similar tools based on Deep Learning.
 
 ## Objective
 
-1. Integrate a Lung Segmentation algorithm based on Deep Learning in the Chest Imaging Platform. 
+1. Integrate a Lung Segmentation algorithm based on Deep Learning in the Chest Imaging Platform.
 1. Make available these and other similar tools in Slicer
 
 ## Approach and Plan

PW27_2018_Boston/Projects/CompressedVideoSaving/README.md

@@ -63,4 +63,3 @@ Next steps
 - [Ipad for image-guided neurosurgery](http://digital-library.theiet.org/content/journals/10.1049/htl.2017.0062?crawler=true&mimetype=application/pdf&tags=noindex)
 <!-- Documentation: https://link.to.docs -->
 <!-- Test data: https://link.to.test.data -->
-

PW27_2018_Boston/Projects/DICOMforQuantitativeImaging/README.md

@@ -22,7 +22,7 @@ Back to [Projects List](../../README.md#ProjectsList)
 
 ## Approach and Plan
 
-Issues to fix: 
+Issues to fix:
 * https://github.com/QIICR/QuantitativeReporting/issues/201
 * https://github.com/QIICR/QuantitativeReporting/issues/209
 * https://github.com/QIICR/QuantitativeReporting/issues/210

PW27_2018_Boston/Projects/EM_trackers_magnetics_and_algorithms/README.md

@@ -71,4 +71,3 @@ No new ones; see Background and References for old ones.
 - [traneus's breadboard 6DOF EM tracker](https://web.archive.org/web/20151002101401/http://home.comcast.net/~traneus/dry_emtrackertricoil.htm)
 - [traneus's PhD dissertation on an EM tracker](https://web.archive.org/web/20151002101400/http://home.comcast.net/~traneus/thesis.pdf)
 - [four figures in traneus's dissertation](https://web.archive.org/web/20151002101400/http://home.comcast.net/~traneus/thesifig.pdf)
-

PW27_2018_Boston/Projects/ESLD_DSS/README.md

@@ -31,7 +31,7 @@ We are using Partner's image database for a corpus of imaging data (liver diseas
 
 1. Understand standard/established clinical scores and effects/representation in medical imaging.
 1. Familiarize with the data from this study.
-1. Review and discuss current literature/ feature extraction approaches. 
+1. Review and discuss current literature/ feature extraction approaches.
 1. This is kind of a Project Kick-Off: Create a work plan how to approach this problem also beyond the scope of the project week.
 
 ## Approach and Plan
@@ -41,14 +41,14 @@ We are using Partner's image database for a corpus of imaging data (liver diseas
 
 ## Progress
 
-1. We had a first team meeting to bring together computer scientists and clinicians. 
+1. We had a first team meeting to bring together computer scientists and clinicians.
 1. Dr. Wall reviewed her progress in selecting a small set of optimal diseased and control patients. This process has been challenging because many people with liver disease have had surgery or tumor ablation that changes the liver morphology. It is also not possible to select only patients on 3T scanner before BWH began using EPIC (2015).
 1. Alireza Ziaei,  Raul San Jose, and Randy Gollub are assisting with RPDR querying and image retrieval.
 1. Jennifer worked on CITI training for IRB clearance to access the data. And talked with experts using PyRadiomics on MRI Data and their approaches on evaluating features (Michael Schwier and Joost van Griethuysen).
 
 ## Next Steps
 
-1. Lock down the image queying and retrieval pipeline.  
+1. Lock down the image queying and retrieval pipeline.
 1. Get deidentified data to University of Bremen team.
 1. Think hard about segmentation, machine learning, and analysis techniques for the data.
 

PW27_2018_Boston/Projects/ExtensionsWithCUDA/README.md

@@ -21,7 +21,7 @@ Provide an easy path for distributing extensions that use CUDA.
 
 1. Create sample CUDA extension
    1. Create simple CUDA extension "Slicer CUDA Probe"
-   1. Perform manual build, upload, and test 
+   1. Perform manual build, upload, and test
       1. https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions
       1. https://www.slicer.org/wiki/Documentation/Nightly/Developers/Build_ExtensionsIndex
 1. Set up VM that matches factory, but with CUDA installed