Generalize twtstight for arbitrary beta0 and code refactoring

include/picongpu/fields/background/templates/twtstight/BField.hpp

@@ -38,7 +38,7 @@ namespace picongpu
             class BField
             {
             public:
-                using float_T = float_64;
+                using float_T = float_X;
 
                 /** Center of simulation volume in number of cells */
                 PMACC_ALIGN(halfSimSize, DataSpace<simDim>);

include/picongpu/fields/background/templates/twtstight/EField.hpp

@@ -38,7 +38,7 @@ namespace picongpu
             class EField
             {
             public:
-                using float_T = float_64;
+                using float_T = float_X;
 
                 /** Center of simulation volume in number of cells */
                 PMACC_ALIGN(halfSimSize, DataSpace<simDim>);

include/picongpu/fields/background/templates/twtstight/twtstight.hpp

@@ -68,10 +68,10 @@ namespace picongpu
             /** To avoid underflows in computation, numsigmas controls where a zero cutoff is made.
              *  The fields thus are set to zero at a position (numSigmas * tauG * cspeed) ahead
              *  and behind the respective TWTS pulse envelope.
-             *  Developer note: In case the float_T-type is set to float_X instead of float_64,
-             *  numSigma needs to be adjusted to numSigmas = 6 to avoid numerical issues.
+             *  Developer note: In case the float_T-type is set to float_64 instead of float_X,
+             *  numSigma can be increased to numSigmas = 10 without running into numerical issues.
              */
-            constexpr uint32_t numSigmas = 10;
+            constexpr uint32_t numSigmas = 6;
         } // namespace twtstight
     } // namespace templates
 } // namespace picongpu

share/picongpu/benchmarks/TWEAC-FOM/cmakeFlags

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Copyright 2013-2023 Axel Huebl, Rene Widera, Sergei Bastrakov
+# Copyright 2013-2024 Axel Huebl, Rene Widera, Sergei Bastrakov, Alexander Debus
 #
 # This file is part of PIConGPU.
 #
@@ -29,17 +29,17 @@
 #   - start with zero index
 #   - increase by 1, no gaps
 
-# use field background for laser generation (will not use incident field)
-flags[0]="-DPARAM_OVERWRITES:LIST='-DPARAM_FIELD_BACKGROUND=1'"
+# use incident field for laser generation (will not use field background and should be faster)
+# use componentwise field calculation (may be faster?)
+flags[0]="-DPARAM_OVERWRITES:LIST='-DPARAM_FIELD_BACKGROUND=0;-DPARAM_COMPONENTWISE=1'"
 
 # limit examles if we run CI tests
 if [ -z  "$PIC_CI_MAINLINE" ] ; then
   # use incident field for laser generation (will not use field background and should be faster)
   # use full field calculation
   flags[1]="-DPARAM_OVERWRITES:LIST='-DPARAM_FIELD_BACKGROUND=0;-DPARAM_COMPONENTWISE=0'"
-  # use incident field for laser generation (will not use field background and should be faster)
-  # use componentwise field calculation (may be faster?)
-  flags[2]="-DPARAM_OVERWRITES:LIST='-DPARAM_FIELD_BACKGROUND=0;-DPARAM_COMPONENTWISE=1'"
+  # use field background for laser generation (will not use incident field)
+  flags[2]="-DPARAM_OVERWRITES:LIST='-DPARAM_FIELD_BACKGROUND=1'"
 fi
 
 ################################################################################

share/picongpu/benchmarks/TWEAC-FOM/include/picongpu/param/incidentField.param

@@ -262,11 +262,29 @@ namespace picongpu
             using ZMin = MyProfile;
             using ZMax = MyProfile;
 
-            // These values are chosen to match the background, have to be changed for higher order field solvers
+            /** Position in cells of the Huygens surface relative to start of the total domain
+             *
+             * The position is set as an offset, in cells, counted from the start of the total domain.
+             * For the max boundaries, negative position values are allowed.
+             * These negative values are treated as position at (global_domain_size[d] + POSITION[d][1]).
+             * It is also possible to specify the position explicitly as a positive number.
+             * Then it is on a user to make sure the position is correctly calculated wrt the grid size.
+             *
+             * Except moving window simulations, the position must be inside the global domain.
+             * The distance between the Huygens surface and each global domain boundary must be at least
+             * absorber_thickness + (FDTD_spatial_order / 2 - 1). However beware of setting position = direction *
+             * (absorber_thickness + const), as then changing absorber parameters will affect laser positioning.
+             * When all used profiles are None, the check for POSITION validity is skipped.
+             *
+             * For moving window simulations, POSITION for the YMax side can be located outside the initially
+             * simulated volume. In this case, parts of the generation surface outside of the currently simulated
+             * volume is are treated as if they had zero incident field and it is user's responsibility to apply a
+             * source matching such a case.
+             */
             constexpr int32_t POSITION[3][2] = {
-                {1, -1}, // x direction [negative, positive]
-                {1, -1}, // y direction [negative, positive]
-                {1, -1} // z direction [negative, positive]
+                {16, -16}, // x direction [negative, positive]
+                {16, -16}, // y direction [negative, positive]
+                {16, -16} // z direction [negative, positive]
             };
 
         } // namespace incidentField