Re: [Meep-discuss] Error in delete-meep-volume
On 04/27/2017 03:16 PM, Nicolas Bachelard wrote: I am facing the same error as the one I was facing previously and that is posted here: https://www.mail-archive.com/meep-discuss-PRp5c+3HitNr39w1BFAQ+4dd74u8MsAO@public.gmane.org/msg05683.html The solution then was to downgrade my guile package from guilde-2.0.13 to guile -2.0.11. Unfortunately, I recently moved to fedora 25 that does not support this old version of guile. Does anyone have an idea of how I can solve this issue? Unfortunately, this is a bug in SWIG which doesn't yet support Guile 2.2. libctl and MPB have been patched. We are working on something similar for Meep but it is not yet ready. ___ meep-discuss mailing list meep-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
Re: [Meep-discuss] Error in delete-meep-volume
Hi Miquel, Thank you very much, it seems to work. I hope the next guile version will be meep-compatible. Just in case it happens to others individuals, I simply did sudo dnf downgrade guile* Best regards 2016-10-27 0:50 GMT-07:00 Miquel Garriga : > Hi, > > I had the same problem. A workaround for it is to downgrade to > guile-2.0.11 (I'm guessing you have guile-2.0.13) > Guile version 2.0.12 [1] introduced new functions to interact with > automatic SMOB finalization. > I guess the swig wrapper code for meep (meep.i, meep_wrap.patch) has to be > adapted to this new functions. > Unfortunately, I am not fluent enough in scheme and swig to fix the bug. > > Best regards, > Miquel > > [1] https://lists.gnu.org/archive/html/guile-user/2016-07/msg00036.html > > On Tue, 25 Oct 2016 09:27:54 -0700 > Nicolas Bachelard wrote: > > > Dear Meep users, > > > > I am using meep for many of my codes and everything was working fine so > far. > > For a couple of days I do face a weird problem when I execute any of my > > codes. > > For instance when I execute the example ring.ctl > > > > >> meep ring.ctl > > > > --- > > Initializing structure... > > Working in 2D dimensions. > > Computational cell is 16 x 16 x 0 with resolution 10 > > cylinder, center = (0,0,0) > > radius 2, height 1e+20, axis (0, 0, 1) > > dielectric constant epsilon diagonal = (11.56,11.56,11.56) > > cylinder, center = (0,0,0) > > radius 1, height 1e+20, axis (0, 0, 1) > > dielectric constant epsilon diagonal = (1,1,1) > > Halving computational cell along direction y > > time for set_epsilon = 0.0344498 s > > --- > > creating output file "./ring-eps-00.00.h5"... > > Backtrace: > > In ice-9/boot-9.scm: > > 160: 12 [catch #t # ...] > > In unknown file: > >?: 11 [apply-smob/1 #] > > In ice-9/eval.scm: > > 432: 10 [eval # #] > > 432: 9 [eval # #] > > In unknown file: > >?: 8 [primitive-load "ring.ctl"] > > In ice-9/eval.scm: > > 432: 7 [eval # #] > > In ice-9/boot-9.scm: > > 705: 6 [map # #] > > In ice-9/eval.scm: > > 399: 5 Exception thrown while printing backtrace: > > ERROR: In procedure delete-meep-volume: Wrong type argument in position > 1: > > # > > > > ERROR: In procedure %run-finalizers: > > ERROR: In procedure delete-meep-volume: Wrong type argument in position > 1: > > # > > > > Some deprecated features have been used. Set the environment > > variable GUILE_WARN_DEPRECATED to "detailed" and rerun the > > program to get more information. Set it to "no" to suppress > > this message. > > > > > > > > I am strongly suspecting that I did something wrong, but unfortunately I > > don't have any idea of what it could be. > > Does someone has any idea of what is going on? > > > > > > Best regards > > > > Nicolas > > > > > > > > -- > > > > -- > > Nicolas Bachelard, PhD > > NSF Nanoscale Science and Engineering Center (NSEC), > > University of California, Berkeley 3112 Etcheverry Hall, > > UC Berkeley, California 94720, USA > > ___ > meep-discuss mailing list > meep-discuss@ab-initio.mit.edu > http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss -- -- Nicolas Bachelard, PhD NSF Nanoscale Science and Engineering Center (NSEC), University of California, Berkeley 3112 Etcheverry Hall, UC Berkeley, California 94720, USA ___ meep-discuss mailing list meep-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
Re: [Meep-discuss] Error in delete-meep-volume
Hi, I had the same problem. A workaround for it is to downgrade to guile-2.0.11 (I'm guessing you have guile-2.0.13) Guile version 2.0.12 [1] introduced new functions to interact with automatic SMOB finalization. I guess the swig wrapper code for meep (meep.i, meep_wrap.patch) has to be adapted to this new functions. Unfortunately, I am not fluent enough in scheme and swig to fix the bug. Best regards, Miquel [1] https://lists.gnu.org/archive/html/guile-user/2016-07/msg00036.html On Tue, 25 Oct 2016 09:27:54 -0700 Nicolas Bachelard wrote: > Dear Meep users, > > I am using meep for many of my codes and everything was working fine so far. > For a couple of days I do face a weird problem when I execute any of my > codes. > For instance when I execute the example ring.ctl > > >> meep ring.ctl > > --- > Initializing structure... > Working in 2D dimensions. > Computational cell is 16 x 16 x 0 with resolution 10 > cylinder, center = (0,0,0) > radius 2, height 1e+20, axis (0, 0, 1) > dielectric constant epsilon diagonal = (11.56,11.56,11.56) > cylinder, center = (0,0,0) > radius 1, height 1e+20, axis (0, 0, 1) > dielectric constant epsilon diagonal = (1,1,1) > Halving computational cell along direction y > time for set_epsilon = 0.0344498 s > --- > creating output file "./ring-eps-00.00.h5"... > Backtrace: > In ice-9/boot-9.scm: > 160: 12 [catch #t # ...] > In unknown file: >?: 11 [apply-smob/1 #] > In ice-9/eval.scm: > 432: 10 [eval # #] > 432: 9 [eval # #] > In unknown file: >?: 8 [primitive-load "ring.ctl"] > In ice-9/eval.scm: > 432: 7 [eval # #] > In ice-9/boot-9.scm: > 705: 6 [map # #] > In ice-9/eval.scm: > 399: 5 Exception thrown while printing backtrace: > ERROR: In procedure delete-meep-volume: Wrong type argument in position 1: > # > > ERROR: In procedure %run-finalizers: > ERROR: In procedure delete-meep-volume: Wrong type argument in position 1: > # > > Some deprecated features have been used. Set the environment > variable GUILE_WARN_DEPRECATED to "detailed" and rerun the > program to get more information. Set it to "no" to suppress > this message. > > > > I am strongly suspecting that I did something wrong, but unfortunately I > don't have any idea of what it could be. > Does someone has any idea of what is going on? > > > Best regards > > Nicolas > > > > -- > > -- > Nicolas Bachelard, PhD > NSF Nanoscale Science and Engineering Center (NSEC), > University of California, Berkeley 3112 Etcheverry Hall, > UC Berkeley, California 94720, USA ___ meep-discuss mailing list meep-discuss@ab-initio.mit.edu http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
