John Omotani

Results 77 issues of John Omotani

Allows plotting on a non-rectangular grid, at least with PyPlot backend. For example: ```julia using Plots pyplot() nx = 10 ny = 11 x = zeros(ny, nx) y = zeros(ny,...

PyPlot

Adds a new member/argument `ignore_unrecognized_opts` to `ArgParseSettings`. When this is set to true (default is false, which keeps the existing behaviour), instead of throwing an error for unrecognized options, just...

At the moment the `Coordinates::Coordinates()` constructor (plus some utility methods/functions) does a lot of interpolation, extrapolation and checking. This was useful to support new features, but has become more complicated...

discussion
proposal

Using flags to set many of the options for Laplacian solvers is cryptic, and not consistent with the way options are handled everywhere else. Could we replace them with something...

enhance request
proposal

Can we remove `bool Mesh::IncIntShear` and `Field2D Mesh::IntShiftTorsion`? If I understand right, it's a very early version of correcting radial derivatives, which `ShiftedMetric` now deals with in a better way....

It would probably be good for the 'Getting started' section to document how to build the examples when using CMake, i.e. (I think this is the recommended process - @ZedThree?):...

documentation

Previously, the `Solver` implementations passed the loop counter to the `iter` argument of `call_monitors`, but since the iteration has already been completed when the monitors are called, this results in...

discussion
merge-conflicts

The 'getting started' section of the documentation currently the configurations we suggest would end up with builds with a fair amount of debugging enabled - `CHECK=2` for autotools or `-DCMAKE_RELEASE_TYPE=Debug`...

bug
documentation

I just tried running the Hasegawa-Wakatani example with `periodicX = true` (also using `hw:modified=false`, but I don't think that's relevant here). It did run, but very badly until I also...

bug

Setting 'backgrounds' for `Field3D` variables has been disabled/deprecated, see #430, #448. Should the private member `Field3D.background` be removed completely now, along with the related code in `applyBoundary()`? There was some...

discussion