Hi Filip, The Meep code has been updated on the cluster, and now the program does not crash at that point. It obviously is a memory hog, though, and I am still discovering how much it needs to avoid running out.
On a different but connected topic: I would like to set up a cluster run that solves multiple cases, e.g. varying the frequency. It would be great if you could point me to an example .ctl file that executes multiple simulations, creating file names appropriately. Thanks Gib ________________________________________ From: Filip Dominec [filip.domi...@gmail.com] Sent: Thursday, 19 March 2015 12:16 p.m. To: Gib Bogle Cc: meep-discuss Subject: Re: [Meep-discuss] Frequency-domain solver Exactly, this is the trunk repository with the most fresh code. F. D. 2015-03-19 0:11 GMT+01:00, Gib Bogle <g.bo...@auckland.ac.nz>: > I don't think you were confused, but I'm wondering where I should get the > fixed code from. > Is this it? git clone https://github.com/stevengj/meep > > Gib > ________________________________________ > From: Filip Dominec [filip.domi...@gmail.com] > Sent: Thursday, 19 March 2015 12:05 p.m. > To: Gib Bogle > Cc: meep-discuss > Subject: Re: [Meep-discuss] Frequency-domain solver > > Hi, Gib, perhaps I was a bit confused. The fact is that MEEP source > has been fixed by the commit I mentioned, and it was not before April > 2014. Therefore if the release 1.2.1 comes from March, it is probably > not fixed (no matter it is currently the latest official release I am > aware of). > > I guess you need to recompile, then. I would be thankful for the > procedure that finally works for you, too. > > Regards, > Filip > > 2015-03-18 23:46 GMT+01:00, Gib Bogle <g.bo...@auckland.ac.nz>: >> Hi Filip, >> >> I see that the version I have built (with Cygwin on Windows) has source >> code >> dated 29/3/2014. I downloaded meep-1.2.1.tar.gz from >> http://ab-initio.mit.edu/wiki/index.php/Meep_download in January this >> year. >> This claims to be the latest release - is this not the case? >> >> Cheers >> Gib >> ________________________________________ >> From: Filip Dominec [filip.domi...@gmail.com] >> Sent: Thursday, 19 March 2015 11:26 a.m. >> To: Gib Bogle >> Cc: meep-discuss >> Subject: Re: [Meep-discuss] Frequency-domain solver >> >> Hi, Gib, it looks exactly like the bug that has been resolved in git >> commit >> https://github.com/stevengj/meep/commit/0640e9f6a2ccfa2a40375a89b5692ebb1fb87efb >> >> Could you check a recent version of MEEP either compiling it from >> source (blue box in http://f.dominec.eu/meep/index.html#install), or >> installing e.g. from Ubuntu 14.10 repository, where, as far as I know, >> it has been updated? >> >> Filip >> >> 2015-03-18 22:01 GMT+01:00, Gib Bogle <g.bo...@auckland.ac.nz>: >>> I am trying to use the frequency-domain solver for a 3D problem, 25x25x22 >>> with resolution=10. The output from >>> (meep-fields-solve-cw fields) >>> is: >>> Meep: using complex fields. >>> on time step 1 (time=0.05), 41.9989 s/step >>> final residual = 0 >>> Finished solve_cw after 1 steps and 0 CG iters. >>> >>> It seems that nothing is done, taking 42 sec. I think that the way to >>> see >>> the waveform at a point is: >>> (run-until 10 >>> (to-appended "ex" >>> (at-every 0.05 >>> (in-point sample_point output-efield-x) >>> ) >>> ) >>> ) >>> >>> and this gives the same result - i.e. the solution starting from 0 - as >>> if >>> I >>> had not previously invoked meep-fields-solve-cw. >>> >>> I have seen other posts on the mailing list on this subject, but I have >>> not >>> been able to find any resolution. It would be very helpful to have an >>> explanation of this apparent problem. Does the frequency-domain solver >>> work? >>> >>> Thanks >>> Gib >>> >>> >>> >> > _______________________________________________ meep-discuss mailing list meep-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
