I am running a simple 2d simulation using the latest de8571e commit code
on Arch Linux. The python file is named gaussian_beam.py and output is
by the output_png instruction:

sim.run(mp.at_beginning(mp.output_epsilon), mp.at_every(0.1,
mp.output_png(mp.Ez, '-c bluered -Z')), until=t)

If I do: "python gaussian_beam.py" or "mpirun -N 1 python
gaussian_beam.py", all is well. But if I use "mpirun -N 2 python
gaussian_beam.py", I see a huge sequence of errors, beginning:

creating output file "./gaussian_beam-eps-000000.00.h5"...
creating output file "./gaussian_beam-ez-000000.10.h5"...
HDF5-DIAG: Error detected in HDF5 (1.10.1) thread 0:
  #000: H5F.c line 586 in H5Fopen(): unable to open file
    major: File accessibilty
    minor: Unable to open file
  #001: H5Fint.c line 1305 in H5F_open(): unable to lock the file
    major: File accessibilty
    minor: Unable to open file
  #002: H5FD.c line 1839 in H5FD_lock(): driver lock request failed
    major: Virtual File Layer
    minor: Can't update object
  #003: H5FDsec2.c line 940 in H5FD_sec2_lock(): unable to lock file,
errno = 11, error message = 'Resource temporarily unavailable'
    major: File accessibilty
    minor: Bad file ID accessed
h5topng error: error opening HD5 file
creating output file "./gaussian_beam-ez-000000.20.h5"...
HDF5-DIAG: Error detected in HDF5 (1.10.1) thread 0:

All the error messages seem to come from thread 0.
If I change the step function to write to hdf5:

sim.run(mp.at_beginning(mp.output_epsilon), mp.to_appended("ez",
mp.at_every(0.1, mp.output_efield_z)), until=t)

there is no error reported.

I am not certain, whether this is a new issue with the latest commit, or
if it also affects earlier versions.

Hope that's useful to someone!

Ian

_______________________________________________
meep-discuss mailing list
meep-discuss@ab-initio.mit.edu
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss

Reply via email to