Hi John,
You have an extra `ms.output_epsilon()` call in the `run` function.
`output_epsilon` isn't a band function, so you can only call it before or
after `run`.
Chris
On Mon, Jan 21, 2019 at 2:35 PM John Weiner wrote:
> Hi again Chris,
>
> Sorry to bother you again, but I’m still having som
Hi again Chris,
Sorry to bother you again, but I’m still having some trouble (not the same
trouble).
Here is what I do to output epsilon.h5 when running the ModeSolver in
pythonmpb.
Import meep.mpb as mpb
…
ms = mpb.ModeSolver(num_bands=num_bands,
k_points=k_points,
Thanks Chris, much obliged.
John
Envoyé de mon iPhone
> Le 21 janv. 2019 à 14:25, Christopher Hogan a écrit :
>
> Hi John,
>
> Outputting epsilon.h5 used to be the default for Python, but that was changed
> in PR #401 (https://github.com/NanoComp/meep/pull/401) as a response to issue
> 387
Hi John,
Outputting epsilon.h5 used to be the default for Python, but that was
changed in PR #401 (https://github.com/NanoComp/meep/pull/401) as a
response to issue 387 (https://github.com/NanoComp/meep/issues/387). It
looks like the documentation was never updated. I'll take care of that.
To out
Meep and MPB Users and Developers,
I have been experimenting with the python version of MPB and found in the Run
Functions section of the MPB Documentation on readthedocs the following
statement under ModeSolver.run(*band_func)
This runs the simulation described by the input parameters (see abo
5 matches
Mail list logo
