Hello, I installed the precompiled version of Meep using apt-get. 1. I noticed that the codes without material-function are running normally without requiring additional time. 2. It is the codes which use material-function which have become very slow. 3. Both guile and hdf5 are the latest versions. 4. I also configured Meep from the source file; the make check test runs without any errors before installation. After installation I have the error "meep not complied with hdf5" just before the Hdf5 output. Still the time taken for the initialization and run have not reduced. Regards, Jisha
Ardavan Oskooi Thu, 01 Sep 2016 23:30:53 -0700 On 09/01/2016 12:48 AM, Jisha C P wrote: Did you install Meep from source and if so, have you verified using "make check" that all tests passed? One possibility is that you are using a material-function or reading from a file to set up the geometry since the slow down persists with or without subpixel averaging. This may be related to the Guile or HDF5 libraries which likely changed during the upgrade; for consistency, make sure that these packages are the same version or newer than the ones used previously. -------------------- So this is puzzling; I have no clue except for a true bug in the code. Perhaps you could try some profiler to find out which part of the MEEP codes is responsible for the long time. Hopefully somebody from the MEEP developers will add their view. Filip
_______________________________________________ meep-discuss mailing list meep-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss