block and generic scanner geometry

.appveyor.yml

@@ -30,6 +30,6 @@ build_script:
 
 test_script:
   - cd C:\projects\stir\build
-  - ctest -VV -C %CONFIGURATION%
+  - ctest --output-on-failure  -C %CONFIGURATION%
   - cd ..\recon_test_pack
   - run_tests --nointbp "C:\projects\stir\install\bin\"

documentation/release_5.0.htm

@@ -80,9 +80,15 @@ <h3>Changes breaking backwards compatibility from a user-perspective</h3>
     STIR usages of these methods (OSSPS and SqrtHessianRowSum) have been updated to see no effective change in functionality.
     However, calling the Hessian vector product methods, via python etc., will result in a change in functionality as the sign of the output voxel values has changed.
 </li>
+
+<li> Python/MATLAB wrappers no longer have <code>ProjDataInfo::ProjDataInfoCTI</code>, use <code>ProjDataInfo::construct_proj_data_info</code> instead.
+  However, this now returns an object of the appropriate (derived) type as opposed to just
+  <code>ProjDataInfo</code>. This should be transparant, except apparently for testing equality of objects.
+</li>
 </ul>
 
 
+
 <h3>Bug fixes</h3>
 <ul>
 <li>
@@ -278,7 +284,13 @@ <h3>Backward incompatibities</h3>
     <li>Poisson log-likelihood hierarchy has changed for gradient methods to now use <tt>actual_compute_subset_gradient_without_penalty</tt>
 	in the derived classes (which has an extra argument <tt>add_sensitivity</tt>). Therefore developers that created their own derived class will need to
 	adjust their class accordingly. The <tt>public</tt> class interface is identical though.
-    </li>    
+    </li>
+    <li><code>DetectorCoordinateMapFromfile</code> (used by SAFIR listmode files) has been renamed to <code>DetectorCoordinateMap</code> and moved from <tt>listmode</tt> to <tt>buildblock</tt>.</li>
+    <li><code>Scanner</code> now has a <code>set_up()</code> function. This needs to be called after
+      using any of the <code>set_*()</code> functions (except <code>set_params</code>). For the blocks/generic
+      scanners, this will fill in the detector maps etc.
+      You will get a run-time exception if you forgot to do this.
+    </li>
 </ul>
 
 <h3>New functionality</h3>
@@ -308,6 +320,8 @@ <h3>New functionality</h3>
 </li>
 <li><code>KeyParser::parameter_info()</code> now outputs vectorised keys as well
 </li>
+<li><code>DetectionPosition</code> now has all comparison operators.
+</li>
 <li><code>LOR</code> classes now no longer require phi at input to be between 0 and pi,
   nor psi to be between 0 and 2 pi. They will standardise the input automatically.
   </li>

examples/PET_simulation/generate_input_data.sh

@@ -40,6 +40,7 @@ echo "===  create template sinogram (DSTE in 3D with max ring diff 1 to save tim
 template_sino=my_DSTE_3D_rd1_template.hs
 cat > my_input.txt <<EOF
 Discovery STE
+
 1
 n
 

examples/SAFIR_genericScanner/.gitignore

@@ -0,0 +1,4 @@
+test_generic_implementation*
+test_forward*
+test_*.*v
+sens_*.*v