plasma

Summary

WorkSpace rule for virtual Desktop too.

A clear and concise description of what you want to happen

I put some of my virtual desktops in floating mode and I wish in workspace rules there should be an option for virtual desktops too.
so that after every reboot I should not manually make that desktop floating.

A clear and concise description of any alternative solutions or f

Hi,

one could and should experiment with Interprocedural optimization (IPO) also known as link-time optimization (LTO), especially on the host side for smaller binaries and potentially faster code. It's supported by GCC, Clang, and ICC, among others, which are our typical go-to compilers in HPC.

It's very easy to implement as well

I want to check that the solar calculations are working but I can't find any logs. Where are they located? Can I run this via a terminal and see the logs there?

Need for a reduced diagnostics addition: general 2D particle histogram (think: "np.histogram2d").

• Applications: phase space, energy-emittance plots, etc.
  • Would be useful for WarpX, ImpactX, and HiPACE++
• Size: fit into local GPU memory, e.g., default 1024^2
• 3 parser functions: axis1, axis2, filter
  • All three into the kernel
  • No RNG needed
• Can be loosely on the exiting red

The boosted-frame example script (in the documentation) uses the direct laser injection.
However, when modifying parameters, users can easily be in a situation where the laser does not fit in the box.
For this reason, it might be better to use the laser antenna in the default example.

🎯 Todo

For the parsers in io.hitran, only groups 1-2 and classes 1, 4-6 are implemented.
Notably, group 6 and class 3 are missing which are needed for linear diatomic molecules.
But this is surprising to me as I never had issues with this... am I missing something?

How they should be parsed can be found in the HITRAN2004 paper:
https://hitran.org/media/refs/HITRAN-2004.pdf
tables 3 & 4

Is your feature request related to a problem? Please describe.
It can be necessary to pull out the instrument sampling rate from data. In principle this should be easy but data gaps, instrument turn on/off, etc. can potentially frustrate this determination.

Describe the solution you'd like
It may be necessary for calc_res in utils.time to support different averaging methods for da

FAIL src/generation.test.ts

  ● Test suite failed to run

    src/generation.test.ts:173:53 - error TS2345: Argument of type '{ white: string; whitePrimary: string; whiteSecondary: string; whiteTertiary: string; black: string; blackPrimary: string; blackSecondary: string; blackTertiary: string; transparent: string; ... 23 more ...; buttonFocused: string; }' is not assignable to paramet