On Thu, 12 Oct 2006, [EMAIL PROTECTED] wrote:
Is there some inbuilt debugging info that I could get out of meep. For example: the number of grid points being simulated in each direction, the time_step and grid_size being used, the amount of system memory being used etc. I tried to scan the discussion list as well as the manual to see if there was some discussion on the same but could not find it.
Yes, all of that info (with the exception of the system memory, which I guess you could get with getrusage or some similar system call) is available as part of the field and structure data structures. You can access this from Scheme by the corresponding access functions.
For example, the time step is meep::fields::dt, which you can get in Scheme via (meep-fields-dt-get fields), where "fields" is the predefined global variable storing the default meep::fields data structure in the scheme interface (which is initialized by calling run, or you can call init-fields manually).
As a separate question is there a way for the user to specify an override for the time_step being used by the simulation; as in something that overrides what meep figures out from the Courant condition?
Yes, you can just set the Courant constant to a different value. (See the Courant input variable in the Scheme interface). This is documented in the reference manual.
_______________________________________________ meep-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
