Richard Pausch

Results 73 issues of Richard Pausch

The current implementation of the `unitSI` and `unitDimension` of the complex amplitude in the radiation plugin code is not correct. Due to the previous use of libSplash, fractional units were...

component: plugin
component: tools

If loading the python module `EnergyHistogramData`, shipped with picongpu, via: ```python from picongpu.plugins.data import EnergyHistogramData ``` the module `imageio` (perhaps also `pandas`?) is required. Since this is only a data...

bug
component: plugin
component: tools

As suggested in the tests of #3227, we should test KHI growth rates in PIConGPU again. Currently it looks like the current `dev` produces slightly too low growth rates. This...

question
component: examples
affects latest release
component: tests

This issue was generated during a simulation by @finnolec on taurus/ZIH/TU Dresden. If you take the png output, it appears that there are regions with lower than expected density. ![grafik](https://user-images.githubusercontent.com/5121158/144050750-78415d2f-5d97-45b9-bf2f-5d7347996bfc.png)...

bug
question
component: plugin
affects latest release

Currently the transition radiation plugin introduces with #3003 produces NaNs for example in the LWFA simulations for @OmidZar. This is most likely caused by a division by zero as documented...

question
component: plugin

With the doc-string adjustments in #3143, it turned out that adjusting the doc-string of the derived class also changed the doc-string of the base class. I better solution is needed....

documentation
component: tools

When using `tbg` with the current `dev` on hemera, I get the following warning/error: ```bash ../picongpu4/bin/tbg: line 178: [: ==: unary operator expected ../picongpu4/bin/tbg: line 178: [: ==: unary operator...

component: tools
component: examples

I installed a minimal setup of xeus-cling and jupyter on macOS 10.15.7 via conda `4.10.3` via ```bash conda env create -f setup_cling.yml ``` using the following yml file ```yml name:...

**Performed steps** I freshly installed openPMD-api via conda as follows ```commandline conda create -n openpmd2 -c conda-forge openpmd-api conda activate openpmd2 conda install -c conda-forge jupyter ``` This worked without...

install
frontend: Python3

The introduction text states "We've defaulted to 300 wpm" - but apparently the default startup is the lowest option and uses only 180 wpm. This is either a bug in...