John Omotani

Results 88 issues of John Omotani

Add documentation for parallel boundary conditions. Fixes #2531. Add documentation for 'aligned transform' variant of shifted metric parallel derivatives (as used by STORM, Hermes). 'Aligned transform' is the version that...

documentation

We do not seem to have any documentation on how to set parallel boundary conditions when using `ShiftedMetric` or `FCI` parallel transforms. I have not used methods requiring `yup`/`ydown` fields...

bug
documentation

The docs on boundary conditions (https://bout-dev.readthedocs.io/en/latest/user_docs/boundary_options.html#boundary-conditions) are missing descriptions of quite a few options (`dirichlet_o*`, `neumann_o*`, `free_o3`, possibly others). Hat tip to Theo Gheorghiu for pointing this out!

documentation

`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...

enhance request
good first issue

Apologies if I've missed it by skimming too quickly, but should we have a section linking to the main BOUT++ papers in the manual where users will find it easily?...

documentation

The images on https://hub.docker.com/u/boutproject/ are out of date. This may cause problems (https://github.com/boutproject/xBOUT/issues/178). Do we intend to provide these images? If so it would be nice to have one for...

I implemented a timestep monitor for STORM. The only way I could think to enable the output I wanted was to have a global object that could be accessed by...

feature

It would be nice to have equation numbers shown in the manual on readthedocs.io, in particular for the 'Field-aligned coordinates' section. I'm not a reStructuredText expert does anyone know if...

documentation

There are command line flags like `--verbose` and `--quiet` that it might be nice to be able to set in a `BOUT.inp` file as an alternative. I don't think this...

enhance request

If a 3d Laplace solver (`LaplacePetsc3dAmg`, or `LaplaceHypre3d` once that gets merged) is used in a simulation that does not calculate parallel slices, it will not apply any parallel boundary...

possible bug