[Meep-discuss] configure error on Cygwin

2006-10-18 Thread Guo, Shy-Hauh
Title: [Meep-discuss] configure error on Cygwin






Hi, all;


I encounter fundamental problems at the configure step in installation of meep. If anyone could help, it will be highly appreciated. 

Environment: CYGWIN_NT-5.1

Error message: "C++ complier cannot create executables" 


I have Visual studio installed on the same computer, and it should be included in PATH (as shown below), so there should be C++ complier available on my computer.

(cut & paste from config.log file)

PATH: /cygdrive/c/Program Files/Microsoft Visual Studio/Common/Tools/WinNT

PATH: /cygdrive/c/Program Files/Microsoft Visual Studio/Common/MSDev98/Bin

PATH: /cygdrive/c/Program Files/Microsoft Visual Studio/Common/Tools

PATH: /cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin

~~~


(cut & paste from config.log file)

configure: failed program was:

| /* confdefs.h.  */

| 

| #define PACKAGE_NAME "meep"

| #define PACKAGE_TARNAME "meep"

| #define PACKAGE_VERSION "0.10"

| #define PACKAGE_STRING "meep 0.10"

| #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]"

| #define PACKAGE "meep"

| #define VERSION "0.10"

| /* end confdefs.h.  */

| 

| int

| main ()

| {

| 

|   ;

|   return 0;

| }

configure:2231: error: C++ compiler cannot create executables

See `config.log' for more details.


Sherman



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

Re: [Meep-discuss] metallic boundaries, and metals

2006-10-18 Thread Steven G. Johnson

On Wed, 18 Oct 2006, matt wrote:
Is there a way to set metal boundaries using the ctl interface, other than by 
explicitly placing metal blocks?


Yes, you need to call a lower-level function (meep::fields::set_boundary)

e.g.

(init-fields)
(meep-fields-set-boundary fields Low X Metallic)
(meep-fields-set-boundary fields High X Magnetic)

sets the boundary in the +x direction to be a perfect electric conductor 
and the boundary in the +y direction to be a perfect magnetic conductor.
(Perfect electric conduction boundaries are the default unless you use a 
k-point, which makes periodic the default.)


With the C++ interface, how does one specify metals, or more specifically, 
metallo-dielectric structures?


Perfect metals can be specified just by making epsilon very large and 
negative (e.g. -1e20).  To get realistic metals you need to use dispersive 
materials.


Steven

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


[Meep-discuss] metallic boundaries, and metals

2006-10-18 Thread matt



Is there a way to set metal boundaries using the ctl interface, other 
than by explicitly placing metal blocks?


With the C++ interface, how does one specify metals, or more 
specifically, metallo-dielectric structures?


Kind Regards,
Matt


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


Re: [Meep-discuss] epsilon function (c vs. libctl)

2006-10-18 Thread matt



Hi Steven,

Yes, you're correct.  For completeness, here are the results for the 
coarser resolution.  Indeed, it seems that a higher resolution reduces 
the epsilon discrepancies.


20ppw [C++ finds one duplicate for a total of 12 points, libctl got 11 
points.  Duplicate was manually removed]


  libctl  C++   Pct Diff
  a   b abs(a-b)/a*100%
  0.46600 0.46937   0.722231
  0.63847 0.63490   0.558944
  0.70052 0.69812   0.343073
  0.70365 0.70135   0.327254
  0.81999 0.81604   0.481117
  0.86852 0.86694   0.181721
  0.89094 0.89110   0.017461
  0.94510 0.94228   0.298920
  0.98007 0.97293   0.728422
  0.98870 0.98235   0.641928
  0.99296 0.99775   0.482598


80ppw (from previous email)
  libctl  C++   Pct Diff
  a   b abs(a-b)/a*100%
  0.46864 0.46867   0.0080870
  0.63829 0.64327   0.7806107
  0.64429 0.64847   0.6479023
  0.70878 0.70899   0.0293657
  0.83324 0.71024  14.7610847
  0.83853 0.83288   0.6739258
  0.88855 0.88819   0.0403651
  0.91237 0.91270   0.0363838
  0.95640 0.95648   0.0079315
  0.96689 0.96746   0.0589339
  0.99507 0.99884   0.3790904


Perhaps a better way to check this is to examine the number of epsilon 
discrepancies using h5diff. (eg., 'h5diff ctl.20.h5 cpp.20.h5 -d .1')


for 20ppw, the data set is 20x240 = 4800 points.
for 80ppw, the data set is 80x960 = 76800 points.

   20ppw%age of 480080ppw   %age of 76800
no -d  192   4 %784  1.02%
-d .1   80   1.67%  348  0.45%
-d 124   0.5%68  0.09%

For this particular example, increasing the resolution by a factor of 
four reduced the normalized discrepancy count between the cpp and ctl 
versions approximately by a factor of four.


Best Regards,
Matt



On Tue, 17 Oct 2006, Steven G. Johnson wrote:


On Tue, 17 Oct 2006, matt wrote:

 Increasing the resolution should minimize the errors you describe, so
 let's try changing the resolution of the example from 20 to 80.


Note that the comparison you posted was incomplete, because you didn't show 
the differences for a resolution of 20 to see whether 80 was indeed smaller.


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




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