Units were (and still are) a stumbling block for me as well, so I think
a list of guidelines to supplement the documentation would be useful.
I'm not aware of a list of error explanations, but I'm also unaware of
any error messages which are so obscure that you can't deduce what the
problem was. For example, now that you know you had a gridding problem,
the text of your last error wasn't all that obscure. That said, maybe
it would be useful to add a page on the wiki regarding error messages,
starting with the one you got. You can't do this yourself for spam
prevention reasons, but you could start a write-up and email it to the
list.
Line numbers:
If you're using the c++ libraries, your compiler should spit out the
line number and an error for any undeclared variables.
I don't think this is possible with the libctl interface, but meep will
at least tell you the name of the unbound variable, which you can then
search for in your script.
Best,
Matt
On Sun, 5 Nov 2006, Ashifi wrote:
Thanks for the tip, Matt. I based my code on that thread and a host of
suggestions in the mailing list archives. I'm trying to come up with a
list of newbie guidelines for MEEP simulations, but they have to work
for me first. Let me play around with the script a bit, and If I don't
get good results I will post a detailed email with the guidelines I
picked up.
For debugging, is there a list of errors and possible causes somewhere
that I could access? How about turning on line numbers in "unbound
variable" errors?
Ashifi
_______________________________________________
meep-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
