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

Need to change the location of the log file which is automatically generated when an error occurs in Konsave. The new location would be: ~/.config/konsave/logs/<date of creation>.txt.

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?

🎯 Describe what you'd like

The possibility to plot any variable (radiance, absorbance...) on a double x-axis plot would be really convenient!

💡 Possible implementations

In spectrum.plot the argument wunit could be used.
For exam

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.

Solver::addMonitor() has a MonitorPosition pos argument that allows the user to control whether a new monitor is added to the beginning (front) or end (back) of the list of output monitors.
https://github.com/boutproject/BOUT-dev/blob/efb92e9672a3c380209420512e4e1ee94e91624a/include/bout/solver.hxx#L221

It would be nice to have a similar argument for Solver::addTimestepMonitor().
https:

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