Bug in use of electric field and use of microelectronics Physics List?

Geometry, Fields and Transportation
1

_Geant4 Version:_11.2.2
Operating System: Linux (5.15.0-124-generic)
_Compiler/Version:_GCC-12.3.0
_CMake Version:_3.26.3

Hello, this is a follow up to an earlier post here:

I find that if I define an electric field using the GetFieldValue approach (so that I could define the field at any given point), then an electron seems to be killed after a short while. This is when using the Microelectronics Physics list. I defined a very simple electric field which simply returns a constant in the z axis - to avoid possible errors in my code. I can view the field using the /vis/scene/add/electricField 10 lightArrow command and all seems good. If I use a uniform electric field (of the same strength and direction) rather than define my own field (using G4UniformElectricField), then the electron flies correctly and is not stopped and killed.
If I change the Physics List to G4EmLivermorePhysics (for instance), then I find that both approaches work and the electron flies correctly with my own (uniform) field and a uniform field of the same strength and direction setup with G4UniformElectricField. What might be happening here? Does this mean there might be a bug associated with electric fields and the use of the Microelectronics Physics list ?
Thanks in advance
Chris

2

Not my area of expertise, but this may help: Electron trajectories at low energy in a low electric field

3

Thanks John, but actually that was my own posting from a little while ago. I had a problem with the electron flying in a uniform electric field, but that was solved. Now I find I still have a problem with a field that I have defined myself. I think I might have to resort to the solution I tried before and let another program handle the flight through the vacuum and Geant4 handle the scattering inside a material. This approach is slow and clunky though.
Chris