> You are giving all of your distance in units of meters, which is fine. > But then your resolution is 10, which means 10 pixels per meter (i.e. > pixel = 0.1m), which is far too small: it means your wavelength is > less than 1 pixel, and also that your block is less than 1 pixel in > size.
Thanks for the feedback Steven. I tried a few things over the weekend. Resolution = 1e8 should give me 1e8 pixels per meter, or 1 pixel = 1e-8 meters which would sufficiently resolve the 18 micron thick copper plate. Setting the resolution to 1e8 gives the error: meep: Cannot split -638795776 grid points into 1 parts Reducing the resolution to 1e6 gives the following error: terminate called after throwing an instance of 'std::bad_alloc' what(): St9bad_alloc Aborted Resolution = 1e6 would not have been the best anyways, but 1e8 should have done the trick. St9bad_alloc is usually thrown when there are memory allocation issues. I have a computer with 4 GB of RAM. Is MEEP using that much memory? Why then does the error message change when the resolution is increased? I thought a higher resolution meant more memory consumption, ceteris paribus. I reduced the computational volume from 11*lambda x 30*lambda to just lambda x lambda, but that doesn't solve the problem. Again, the code can be seen at: http://pastebin.us/8034 Gracias. Ashifi. _______________________________________________ meep-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
