Re: [Meep-discuss] (no subject)

[John Weiner]

Galaa

This seems to be a different problem from mine because when I have seen these 
excursions, they have not been reproducible either in position or in amplitude. 
 Have you varied the resolution of your FDTD routine or the periodicity of your 
“comb” structure?  One other suggestion:  try to make sure that your 
computational grid aligns exactly on the interface between materials…I have 
seen strange artifacts arise when the computational points straddle, say, a 
discontinuous permittivity boundary.

John

> On May 28, 2019, at 21:01, Galaa Badrakh  wrote:
> 
> Hi John
> 
> Please have a look at the attachment. I have two different duplications and 
> the defects are in the duplications. If I re-run I get the same defects at 
> the same positions. Is this the problem you are facing?  I have plotted with 
> pyplot and also with Mathematica, no difference at all. I have also tried 
> with "mp.at_beginning(mp.output_epsilon)" but changes. 
> 
> G
> 
> On Wed, 29 May 2019 at 00:45, John Weiner  > wrote:
> Hi Galaa,
> 
> I’ve seen similar things, large isolated, unphysical excursions in otherwise 
> perfectly reasonable results when plotting data from a meep output.  Are you 
> using Matplotlib/pyplot for your plotting routines?  And do the excursions 
> appear at exactly the same points and with the same amplitudes reproducibly 
> or do they vary unpredictably?  I would be quite interested to know if anyone 
> has a good explanation and a good fix.
> 
> Best regards,
> 
> John
> 
> > On May 28, 2019, at 17:33, Galaa Badrakh  > > wrote:
> > 
> > Hi All. 
> > 
> > I am new to MEEP and trying to use the "geometric_objects_duplicates" 
> > feature. After simulation complete, I extracted the dielectric spatial 
> > profile with "data=sim.get_array(center=mp.Vector3(), 
> > size=mp.Vector3(0.0,0.0,height), component=mp.Dielectric)" to double check 
> > my geometry but I see unexpected lines at some interfacing points, have a 
> > look at attached picture. Is this the artifact of subpixel smoothing? If 
> > so, how to avoid this artifact? 
> > 
> > Thanks in advance
> > 
> > G
> > ___
> > 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

Re: [Meep-discuss] (no subject)

[Galaa Badrakh]

Hi John

Please have a look at the attachment. I have two different duplications and
the defects are in the duplications. If I re-run I get the same defects at
the same positions. Is this the problem you are facing?  I have plotted
with pyplot and also with Mathematica, no difference at all. I have also
tried with "mp.at_beginning(mp.output_epsilon)" but changes.

G

On Wed, 29 May 2019 at 00:45, John Weiner  wrote:

> Hi Galaa,
>
> I’ve seen similar things, large isolated, unphysical excursions in
> otherwise perfectly reasonable results when plotting data from a meep
> output.  Are you using Matplotlib/pyplot for your plotting routines?  And
> do the excursions appear at exactly the same points and with the same
> amplitudes reproducibly or do they vary unpredictably?  I would be quite
> interested to know if anyone has a good explanation and a good fix.
>
> Best regards,
>
> John
>
> > On May 28, 2019, at 17:33, Galaa Badrakh  wrote:
> >
> > Hi All.
> >
> > I am new to MEEP and trying to use the "geometric_objects_duplicates"
> feature. After simulation complete, I extracted the dielectric spatial
> profile with "data=sim.get_array(center=mp.Vector3(),
> size=mp.Vector3(0.0,0.0,height), component=mp.Dielectric)" to double check
> my geometry but I see unexpected lines at some interfacing points, have a
> look at attached picture. Is this the artifact of subpixel smoothing? If
> so, how to avoid this artifact?
> >
> > Thanks in advance
> >
> > G
> > ___
> > 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

Re: [Meep-discuss] (no subject)

[John Weiner]

Hi Galaa,

I’ve seen similar things, large isolated, unphysical excursions in otherwise 
perfectly reasonable results when plotting data from a meep output.  Are you 
using Matplotlib/pyplot for your plotting routines?  And do the excursions 
appear at exactly the same points and with the same amplitudes reproducibly or 
do they vary unpredictably?  I would be quite interested to know if anyone has 
a good explanation and a good fix.

Best regards,

John

> On May 28, 2019, at 17:33, Galaa Badrakh  wrote:
> 
> Hi All. 
> 
> I am new to MEEP and trying to use the "geometric_objects_duplicates" 
> feature. After simulation complete, I extracted the dielectric spatial 
> profile with "data=sim.get_array(center=mp.Vector3(), 
> size=mp.Vector3(0.0,0.0,height), component=mp.Dielectric)" to double check my 
> geometry but I see unexpected lines at some interfacing points, have a look 
> at attached picture. Is this the artifact of subpixel smoothing? If so, how 
> to avoid this artifact? 
> 
> Thanks in advance
> 
> G
> ___
> 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

Re: [Meep-discuss] (no subject)

[Filip Dominec]

Dear Shampy,
this topic has been discussed many times. Generally you can not force
a complex value of permittivity in FDTD. You can however define a
high-frequency oscillator that introduces losses.

More on this topic is at
http://ab-initio.mit.edu/wiki/index.php/Dielectric_materials_in_Meep
or search the mailing list.

I tried to make a list of some realistic material models at
http://fzu.cz/~dominecf/misc/eps/; the data used can be fed to MEEP.

Finally I would like to ask you to stick to the "netiquette" and write
your name as "Shampy Mansha", not "#SHAMPY MANSHA#". The capitals look
like shouting, and the hashmarks look like something as banging your
fist on the table before and after saying it...

Regards,
Filip Dominec


2014-06-12 18:01 GMT+02:00, #SHAMPY MANSHA# :
> Dear Steven and other Meep users,
>
> I am doing a simulation in which I require to use a complex dielectric
> constant of the form(say for example):
>
> epsilon = 1 + 0.01i
>
> For my simulation the frequency isn't fixed, instead I have to use a
> gaussian source with some finite width.
> And in the whole simulation I wish to use the same epsilon(epsilon =
> 1+0.01i).
>
> Is there a way to do this kind of simulation?
>
> Thanks,
> Shampy Mansha
> NTU,Singapore
>

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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Apr 18, 2014, at 10:12 AM, ISAAC MATERE  wrote:

> hallo meep users
> can coupling  two
> straight waveguides and a microdisc be done in meep, 

Yes.

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

Re: [Meep-discuss] (no subject)

[Filip Dominec]

Dear Farhad,
from what I recall from tinkering the sources, you will probably want
to edit the polarizability.cpp. First of all, there already _is_ a
model that includes some random fluctuations; it might suit your
needs. If not, modifying the code that implements constitutive
relations is the best access point to add new physics, anyway.

Beware the MEEP code is optimized for speed, i. e. it is a bit hard to
read and many lines are found when one searches for 'yucky'...

I believe all other physics can be incorporated into the
aforementioned custom routine for polarisation update. Maybe the MEEP
authors can give more detailed info...
Filip


2014/1/6, FARHAD KAZEMI :
> Dear Fillip,
>
> thank you so much for your answer. Actually, briefly , fluctuational
> electrodynamics indicates that, the electromagnetic wave generated by a
> surface with finite T>0 of temperature is because of the fluctuation of
> charges or dipoles inside the material. It studied this phenomenon
> statistically. this kind of fluctuations caus two types of thermal radiation
> namely far-field and near-field radiation. far-field radiation is well-known
> case which can be predicted easily by some simple radiative heat transfer
> equations. However, for the case of near-field we need to apply such concept
> ( fluctuational electrodynamics) in our calculations in order to reveal the
> near-field radiative heat transfer enhancement occurred between two plates
> separated by a nano-distance gap. This phenomenon can be explained due to
> the existence of surface polaritons on the interface between surfaces of the
> plates. There is a paper describing the application of FDTD for such problem
> and
>  I am trying to recalculate the same thing using MEEP and of course
> manipulate some parameters later.
> Specifically, can we manipulate the existence code of the MEEP to solve some
> other equations (in this case  fluctuational electrodynamics) parallely with
> Maxwell ewuations?
> Additionally, do you have any idea about how can I include the effects of
> temperature on the emission of the EM wave from a surface with a finite
> temperature?
>
> Thank you again. sorry if my message is long.
>
> Farhad
>
>
>
> On Monday, January 6, 2014 5:50 PM, Filip Dominec 
> wrote:
>
> Dear Farhad,
> I am not an expert nor I have thoroughly read the referred
>  article,
> but I believe the non-radiative fields should be exactly modelled by
> MEEP as long as they are a solution of the (source-free) Maxwell
> equations. You may, for example, define a metallic
>  capacitor and a
> metallic inductor, connect them and you should obtain the realistic
> oscillation frequency of this LC circuit.
>
> You might, however, find out it would be necessary to newly implement
> thermal emission and absorption. Maybe even some quantum phenomena
> would involve - but, for instance, the Casimir forces have been
> implemented in MEEP successfully so even this can be done.
>
> The article touches a quite interesting topic, by the way.
>
> Best wishes,
> Filip Dominec
>
>
> 2014/1/6, FARHAD KAZEMI :
>>
>  Dear all,
>>
>> I would
>  like to model the radiation transfer between two plates
>> separated by nano-gap in which we have to bring near-field radiation
>> effects into account using fluctuational electrodynamics.
>> Does MEEP is capable of solve such problems? or we need to
>> manipulate the source C++ codes to introduce near-field equations?
>> In fact, I am trying to reproduce the results of the following paper.
>>
>> Mathieu Francoeur, M. Pinar Menguc, Role of fluctuational electrodynamics
>> in
>> near-field radiative heat transfer, Journal of Quantitative Spectroscopy &
>> Radiative Transfer 109 (2008) 280–293
>>
>> Thanks®ards Farha

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

Re: [Meep-discuss] (no subject)

[FARHAD KAZEMI]

Dear Fillip,

thank you so much for your answer. Actually, briefly , fluctuational 
electrodynamics indicates that, the electromagnetic wave generated by a surface 
with finite T>0 of temperature is because of the fluctuation of charges or 
dipoles inside the material. It studied this phenomenon statistically. this 
kind of fluctuations caus two types of thermal radiation namely far-field and 
near-field radiation. far-field radiation is well-known case which can be 
predicted easily by some simple radiative heat transfer equations. However, for 
the case of near-field we need to apply such concept ( fluctuational 
electrodynamics) in our calculations in order to reveal the near-field 
radiative heat transfer enhancement occurred between two plates separated by a 
nano-distance gap. This phenomenon can be explained due to the existence of 
surface polaritons on the interface between surfaces of the plates. There is a 
paper describing the application of FDTD for such problem and
 I am trying to recalculate the same thing using MEEP and of course manipulate 
some parameters later. 
Specifically, can we manipulate the existence code of the MEEP to solve some 
other equations (in this case  fluctuational electrodynamics) parallely with 
Maxwell ewuations?
Additionally, do you have any idea about how can I include the effects of 
temperature on the emission of the EM wave from a surface with a finite 
temperature?

Thank you again. sorry if my message is long.

Farhad



On Monday, January 6, 2014 5:50 PM, Filip Dominec  
wrote:
 
Dear Farhad,
I am not an expert nor I have thoroughly read the referred
 article,
but I believe the non-radiative fields should be exactly modelled by
MEEP as long as they are a solution of the (source-free) Maxwell
equations. You may, for example, define a metallic
 capacitor and a
metallic inductor, connect them and you should obtain the realistic
oscillation frequency of this LC circuit.

You might, however, find out it would be necessary to newly implement
thermal emission and absorption. Maybe even some quantum phenomena
would involve - but, for instance, the Casimir forces have been
implemented in MEEP successfully so even this can be done.

The article touches a quite interesting topic, by the way.

Best wishes,
Filip Dominec


2014/1/6, FARHAD KAZEMI :
>
 Dear all,
>
> I would
 like to model the radiation transfer between two plates
> separated by nano-gap in which we have to bring near-field radiation
> effects into account using fluctuational electrodynamics.
> Does MEEP is capable of solve such problems? or we need to
> manipulate the source C++ codes to introduce near-field equations?
> In fact, I am trying to reproduce the results of the following paper.
>
> Mathieu Francoeur, M. Pinar Menguc, Role of fluctuational electrodynamics in
> near-field radiative heat transfer, Journal of Quantitative Spectroscopy &
> Radiative Transfer 109 (2008) 280–293
>
> Thanks®ards Farha___
meep-discuss mailing list
meep-discuss@ab-initio.mit.edu
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss

Re: [Meep-discuss] (no subject)

[Filip Dominec]

Dear Farhad,
I am not an expert nor I have thoroughly read the referred article,
but I believe the non-radiative fields should be exactly modelled by
MEEP as long as they are a solution of the (source-free) Maxwell
equations. You may, for example, define a metallic capacitor and a
metallic inductor, connect them and you should obtain the realistic
oscillation frequency of this LC circuit.

You might, however, find out it would be necessary to newly implement
thermal emission and absorption. Maybe even some quantum phenomena
would involve - but, for instance, the Casimir forces have been
implemented in MEEP successfully so even this can be done.

The article touches a quite interesting topic, by the way.

Best wishes,
Filip Dominec

2014/1/6, FARHAD KAZEMI :
> Dear all,
>
> I would like to model the radiation transfer between two plates
> separated by nano-gap in which we have to bring near-field radiation
> effects into account using fluctuational electrodynamics.
> Does MEEP is capable of solve such problems? or we need to
> manipulate the source C++ codes to introduce near-field equations?
> In fact, I am trying to reproduce the results of the following paper.
>
> Mathieu Francoeur, M. Pinar Menguc, Role of fluctuational electrodynamics in
> near-field radiative heat transfer, Journal of Quantitative Spectroscopy &
> Radiative Transfer 109 (2008) 280–293
>
> Thanks®ards Farha

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

Re: [Meep-discuss] (no subject)

[Wu Chuanren]

Hi,

you can scale the four maxwell equations and let c = 1  ^_^
There are a lot of (infinite) possibilities to scale it.

Best regards




2013/10/28 LErmeng 

> **
> Hi,
> I have two problems with meep:
>
> 1. How could I convert the electric/magnetic component (Hz, Ez ...) to
> real word electric/magnetic component which unit is SI ?
> 2. For example, there is a vertical magnetic-dipole on the ground ,and
> pass continuous electric-charge current with fixed frequency, which
> component is Hz. Is the real world continuous-src act like that? Just creat
> the Hz.
>
> Could you help me please?
>
> thanks
> --
> LErmeng
>
> ___
> 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

Re: [Meep-discuss] (no subject)

[Filip Dominec]

Hi,
this is purely a mathematical question related to diffraction.
Generally, if your source is ten times the wavelength, the output
radiation divergence may be estimated to be one tenth of radian. So
you have to make the source plane as big as possible.
Another approach giving a precise plane wave, is to use the Bloch
periodic boundaries.
Regards,
F.

2013/4/8, a g :
> Hello,
>
> How can I define a short laser pulse with a very small solid angle
> (obviously) in MEEP? When I am using a gaussian source I get the source,
> that is shining in all directions and not in one direction.
>
>
>
> ___
> 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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Sep 12, 2010, at 10:28 AM, mahdiyeh tajabady wrote:
I am trying to simulate transmission or reflection flux of solar  
spectrum AM1.5 from a multilayer mirror. does anyone know how can I  
simulate solar spectrum?


This sounds like a linear problem.  Just simulate the transmission/ 
reflection spectrum as usual (e.g. see the tutorial examples).  Then  
to get the transmitted or reflected power, multiply the transmission  
or reflection by the solar spectrum



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

Re: [Meep-discuss] (no subject)

[Judson Ryckman]

Can't you just make a normal transmission and reflection spectrum of your
structure, and then multiply by the shape of the desired input spectrum?

Good luck!


On Sun, Sep 12, 2010 at 9:28 AM, mahdiyeh tajabady wrote:

> Dear Meep users,
>
> I am trying to simulate transmission or reflection flux of solar spectrum
> AM1.5 from a multilayer mirror. does anyone know how can I simulate solar
> spectrum?
>
> Best
> Mahdieh
>
>
> ___
> 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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Jul 8, 2009, at 10:45 PM, 刘荣鹃 wrote:

It donesn't work and shows 'ERROR: Unbound variable: mu-diag'

Is it the problem from the meep version 0.20.3 I used?


Yes, you need Meep 1.0 or later for this feature.


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

Re: [Meep-discuss] (no subject)

[matt]

Hi,

Have a look at this thread:
http://www.mail-archive.com/meep-discuss@ab-initio.mit.edu/msg00412.html

Best,
Matt



On Mon, 2 Feb 2009, Sivan, Yonatan wrote:

> Hi Meep users,
>
> I am relatively new to meep. Could anyone show me how to employ the
> perfect-electric-conductor/ perfect-magnetic-conductor/metal boundary
> condition in meep? I could not find an example in the meep-examples and
> everything I tried seems to have the wrong syntax.
>
> Thanks, Yonatan.
>
>
> ___
> 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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Nov 1, 2008, at 9:45 PM, rand mouradi wrote:
I'm having trouble whenever I run my program I'm getting this error  
"ERROR: Unbound variable: D-conductivity"


Maybe you are using an old version of Meep?  You need Meep 0.20 or  
later for this feature.  (Run meep --version to get the version number)___
meep-discuss mailing list
meep-discuss@ab-initio.mit.edu
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss

Re: [Meep-discuss] (no subject)

[Manoj Rajagopalan]

This is my best guess:

You system probably has multi-threading enabled. gcc can compile to 
exploit that. I'm guessing the -pthread flag is passed to the compiler 
to invoke some pragmas that include bookkeeping essential for threading 
using the pthreads library and/or include the relevant header-files and 
  paths.

The -lpthread obviously tells gcc to link to the pthreads library.

I'm just surprised that your pkg-config files don't include this info.

Perhaps your HDF5 got built with pthreads and your main application that 
you are linking HDF5 to must include pthreads support to complete the 
dependency chain.

cheers!
Manoj


Mani Chandra wrote:
> Hey Manoj!
>  Thanks for that tip.It now works!..I thought I'd have to start 
> installing again on a clean slate but I guess I can start working 
> now.Though I still like to install everything into a directory and use 
> it from there cause I still dont have harminv etc..
> Could you tell me why adding -pthread and -lpthread worked??
> Thanks
> Mani chandra
> 
> --- On *Sun, 13/1/08, Manoj Rajagopalan /<[EMAIL PROTECTED]>/* wrote:
> 
>     From: Manoj Rajagopalan <[EMAIL PROTECTED]>
> Subject: Re: [Meep-discuss] (no subject)
> To: meep-discuss@ab-initio.mit.edu
> Date: Sunday, 13 January, 2008, 8:21 PM
> 
> Try adding the -pthread and -lpthread options to your compilation 
> command line
> 
> -- Manoj
> 
> 
> Mani Chandra wrote:
> >
>  Hi!
> > After resolving the eps() issue the pthread thing cropped up 
> > again!...Initially I thought it was because I commented out some lines 
> > but this time it's appearing even when I try to compile the full
> program...
> > 
> > #include 
> > using namespace meep;
> > double eps(const vec &p);
> > int main(int argc,char **argv)
> > {
> > initialize mpi(argc,argv);
> > double resolution=20;
> > volume v = vol2d(5,10,resolution);
> > structure s(v,eps,pml(1.0));
> > fields f(&s);
> > 
> > f.output_hdf5(Dielectric,v.surroundings());
> > 
> > double freq = 0.3,fwidth=0.1;
> > gaussian_src_time src(freq,fwidth);
> > f.add_point_source(Ey,src,vec(1.1,2.3));
> > while (f.time() < f.last_source_time())
> > {
> > f.step();
> > }
> > 
> >
>  f.output_hdf5(Hz,v.surroundings());
> >
> > return 0;
> > }
> > 
> > double eps(const vec &p)
> > {
> > if (p.x() < 2 && p.y() < 3)
> > return 12.0;
> > return 1.0;
> > }
> > 
> > [EMAIL PROTECTED] /usr/home/mc/MEEP files]# g++ `pkg-config --cflags 
> meep` 
> > test1.cpp -o test1 `pkg-config --libs meep`
> > /usr/local/lib/libhdf5.so: undefined reference to `pthread_equal'
> > /usr/local/lib/libhdf5.so: undefined reference to
> `pthread_setcancelstate'
> > 
> > Thanks for all the help:)
> > Mani chandra
> > Physics sophomore
> > IIT Kanpur
> > 
> > 
> > 
> > Save all your chat conversations. Find them online. 
> >
> 
> <http://in.rd.yahoo.com/tagline_webmessenger_3/*http://in.messenger.yahoo.com/webmessengerpromo.php>
> 
> > 
> >
>  
> > 
> > 
> > 
> > ___
> > 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
> 
> 
> 
> 5, 50, 500, 5000 - Store N number of mails in your inbox. Click here. 
> <http://in.rd.yahoo.com/tagline_mail_4/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/>
>  
> 
> 
> 
> 
> 
> ___
> 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

Re: [Meep-discuss] (no subject)

[Mani Chandra]

Hey Manoj! Thanks for that tip.It now works!..I thought I'd have to start installing again on a clean slate but I guess I can start working now.Though I still like to install everything into a directory and use it from there cause I still dont have harminv etc..Could you tell me why adding -pthread and -lpthread worked??ThanksMani chandra--- On Sun, 13/1/08, Manoj Rajagopalan <[EMAIL PROTECTED]> wrote:From: Manoj Rajagopalan <[EMAIL PROTECTED]>Subject: Re: [Meep-discuss] (no subject)To: meep-discuss@ab-initio.mit.eduDate: Sunday, 13 January, 2008, 8:21 PMTry adding the -pthread and -lpthread options to your compilation command line-- ManojMani Chandra wrote:>
 Hi!> After resolving the eps() issue the pthread thing cropped up > again!...Initially I thought it was because I commented out some lines > but this time it's appearing even when I try to compile the fullprogram...> > #include > using namespace meep;> double eps(const vec &p);> int main(int argc,char **argv)> {> initialize mpi(argc,argv);> double resolution=20;> volume v = vol2d(5,10,resolution);> structure s(v,eps,pml(1.0));> fields f(&s);> > f.output_hdf5(Dielectric,v.surroundings());> > double freq = 0.3,fwidth=0.1;> gaussian_src_time src(freq,fwidth);> f.add_point_source(Ey,src,vec(1.1,2.3));> while (f.time() < f.last_source_time())> {> f.step();> }> >
 f.output_hdf5(Hz,v.surroundings());>> return 0;> }> > double eps(const vec &p)> {> if (p.x() < 2 && p.y() < 3)> return 12.0;> return 1.0;> }> > [EMAIL PROTECTED] /usr/home/mc/MEEP files]# g++ `pkg-config --cflags meep` > test1.cpp -o test1 `pkg-config --libs meep`> /usr/local/lib/libhdf5.so: undefined reference to `pthread_equal'> /usr/local/lib/libhdf5.so: undefined reference to`pthread_setcancelstate'> > Thanks for all the help:)> Mani chandra> Physics sophomore> IIT Kanpur> > > > Save all your chat conversations. Find them online. >> >
 > > > > ___> meep-discuss mailing list> meep-discuss@ab-initio.mit.edu> http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss___meep-discuss mailing listmeep-discuss@ab-initio.mit.eduhttp://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss


   5, 50, 500, 5000 - Store N number of mails in your inbox. Click here.

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

Re: [Meep-discuss] (no subject)

[Manoj Rajagopalan]

Try adding the -pthread and -lpthread options to your compilation 
command line

-- Manoj


Mani Chandra wrote:
> Hi!
> After resolving the eps() issue the pthread thing cropped up 
> again!...Initially I thought it was because I commented out some lines 
> but this time it's appearing even when I try to compile the full program...
> 
> #include 
> using namespace meep;
> double eps(const vec &p);
> int main(int argc,char **argv)
> {
> initialize mpi(argc,argv);
> double resolution=20;
> volume v = vol2d(5,10,resolution);
> structure s(v,eps,pml(1.0));
> fields f(&s);
> 
> f.output_hdf5(Dielectric,v.surroundings());
> 
> double freq = 0.3,fwidth=0.1;
> gaussian_src_time src(freq,fwidth);
> f.add_point_source(Ey,src,vec(1.1,2.3));
> while (f.time() < f.last_source_time())
> {
> f.step();
> }
> 
> f.output_hdf5(Hz,v.surroundings());
>
> return 0;
> }
> 
> double eps(const vec &p)
> {
> if (p.x() < 2 && p.y() < 3)
> return 12.0;
> return 1.0;
> }
> 
> [EMAIL PROTECTED] /usr/home/mc/MEEP files]# g++ `pkg-config --cflags meep` 
> test1.cpp -o test1 `pkg-config --libs meep`
> /usr/local/lib/libhdf5.so: undefined reference to `pthread_equal'
> /usr/local/lib/libhdf5.so: undefined reference to `pthread_setcancelstate'
> 
> Thanks for all the help:)
> Mani chandra
> Physics sophomore
> IIT Kanpur
> 
> 
> 
> Save all your chat conversations. Find them online. 
> 
>  
> 
> 
> 
> 
> 
> ___
> 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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Thu, 19 Apr 2007, John Doe wrote:
> I want to simulate the transmission through a 3D PhC and I 'll use a 
> source with a various directions (for example (111) direction). I try 
> this guile code, but it doesn't works.

"It doesn't work" is not a useful description of your problem.

Break your problem into steps.  Try the source with no structure, and make 
sure it looks like what you intend (if you want an incident wave at an 
angle, note that you will need a spatially varying amplitude function; 
this has been discussed extensively on this list).  Once you include your 
structure, output the epsilon function and make sure it looks like what 
you intend.  Etc.

Cordially,
Steven G. Johnson

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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Tue, 20 Feb 2007, Huazhong Wang wrote:
I supposed that meep can run all commands of scheme language. but i found 
that some commands couldn't run in meep. For example, commands: when, 
string?, string-match-forward, cause running failure. I am wondering that my 
debian/meep system was installed incompletely. it needs more packages for 
supporting all scheme commands. But, So far, most meep programs, including 
all example programs of meep manual, work well in my system. who could tell 
me the reason? thanks,


Meep uses GNU Guile, which should be a more-or-less complete Scheme 
interpreter.  You should be aware, however, that there are various Scheme 
implementations floating around, such as MIT/GNU Scheme, that implement 
different extensions to the standard Scheme libraries.


If you are new to Scheme, perhaps you are just calling things incorrectly? 
Try calling them in interactive mode (run "meep" with no arguments) to 
experiment.  (Note that interactive mode supports tab-completion so you 
can easily see what Scheme functions are made available by Guile.)


For example, string? and string-match seem to work:

meep> (string? "hello")
#t
meep> (string? 21)
#f
meep> (string-match "world" "hello world")
#("hello world" (6 . 11))
meep> (string-match "blah" "hello world")
#f

There is no string-match-forward function -- I think this is provided by 
MIT/GNU Scheme but is not in the Scheme R5RS standard.


In general, Guile should provide all of the R5RS standard Scheme 
functions 
(http://www.swiss.ai.mit.edu/ftpdir/scheme-reports/r5rs-html/r5rs_toc.html) 
as well as a number of additional functions as defined in the Guile 
reference manual 
(http://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/index.html). 
However, MIT/GNU Scheme (http://www.gnu.org/software/mit-scheme/) provides 
a large number of additional functions, many of which are not provided in 
Guile by default.


If you have detailed questions on the Scheme support implemented by GNU 
Guile, you might want to ask on the Guile mailing list.


Steven

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

Re: [Meep-discuss] (no subject)

[Loic Le Guyader]

Quoting Loic Le Guyader <[EMAIL PROTECTED]>:


Hi,

I still have problem with this. I want to wait a certain time for the 
pulse to arrive
somewhere, and then wait for the decay of the field. I try this 
(important part is the definition of mystop):


(define (mystop)
(let ((decayed (stop-when-fields-decayed 20 Ey endpoint 1e-3)))
 (if (> (meep-time) tt) decayed #f)))

(run-until (mystop)
  (to-appended "ey" (at-every 0.5 output-efield-y)))


I found, it should be:
(define (mystop)
  (let ((decayed (stop-when-fields-decayed 20 Ey endpoint 1e-3)))
 (lambda ()
  (if (> (meep-time) tt) (decayed) false

Cheers.



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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Sat, 20 May 2006, G.J. Parker wrote:

(define sx (inexact->exact (/ a (sqrt 2
(define sy (inexact->exact (* sx (sqrt 3

then you avoid the error. not sure what the actual value of sx & sy meep is 
using, but i'll assume it's essentially what i specified.


No, that's not what you want to do: it rounds the size up to the next 
integer.


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

Re: [Meep-discuss] (no subject)

[G.J. Parker]

--

Steven-

thanks.

i also found a temp workaround:

if you replace

(define sx (/ a (sqrt 2)))
(define sy (* sx (sqrt 3)))

with

(define sx (inexact->exact (/ a (sqrt 2
(define sy (inexact->exact (* sx (sqrt 3

then you avoid the error. not sure what the actual value of sx & sy  
meep is using, but i'll assume it's essentially what i specified.


fyi- been running meep through test cases w/ pure dielectrics- so far  
everything is coming out as expected. bravo!


cheers,

gp

--


On May 20, 2006, at 4:09 PM, Steven G. Johnson wrote:


On Sat, 20 May 2006, G.J. Parker wrote:
believe i found a minor error, but it's probably just numerics.   
in a control file, place:


Thanks, this is a bug.  It was getting confused because if you  
specify a cell size that is not an integer number of pixels, the  
cell size gets adjusted to the nearest integer number of pixels.


I've corrected this problem for the next release (so that it won't  
complain if the source size exceeds the cell size by less than a  
pixel).


Steven

___
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

Re: [Meep-discuss] (no subject)

[Steven G. Johnson]

On Sat, 20 May 2006, G.J. Parker wrote:
believe i found a minor error, but it's probably just numerics.  in a 
control file, place:


Thanks, this is a bug.  It was getting confused because if you specify a 
cell size that is not an integer number of pixels, the cell size gets 
adjusted to the nearest integer number of pixels.


I've corrected this problem for the next release (so that it won't 
complain if the source size exceeds the cell size by less than a pixel).


Steven

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