Yay! I figured that out (and I'm not even a Real Programmer). It turns out HDF5 doesn't put links in /usr/local/bin, /usr/local/lib, and user/local/include as the other programs involved with compiling/running meep do. I just copied the files from the hdf5's include, lib and bin directories to /usr/local/bin, /usr/local/lib, and user/local/include (I hope that isn't Bad and Right) and recompiled meep. Then I had to do a similar thing to the h5utils package. Patti
PattiMichelle wrote: > Oops! I spoke too soon. Apparently meep didn't find HDF5 when I > compiled it (although HDF5 seems to be installed correctly): - is > there some flag I needed to set during meep compile? > > PattiLinuxLaptop:/home/patti # meep > meep> (set! geometry-lattice (make lattice (size 16 8 no-size))) > meep> (set! geometry (list > ... (make block (center 0 0) (size infinity 1 infinity) > ... (material (make dielectric (epsilon 12)))))) > meep> (set! sources (list > ... (make source > ... (src (make continuous-src (frequency 0.15))) > ... (component Ez) > ... (center -7 0)))) > meep> (set! pml-layers (list (make pml (thickness 1.0)))) > meep> (set! resolution 10) > meep> (run-until 200 > ... (at-beginning output-epsilon) > ... (at-end output-efield-z)) > ----------- > Initializing structure... > Working in 2D dimensions. > block, center = (0,0,0) > size (1e+20,1,1e+20) > axes (1,0,0), (0,1,0), (0,0,1) > dielectric constant epsilon = 12 > time for set_epsilon = 0.052974 s > ----------- > creating output file "./eps-000000.00.h5"... > meep: not compiled with HDF5, required for HDF5 output > > 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. > PattiLinuxLaptop:/home/patti # > > > > PattiMichelle wrote: >> I am a new user and was able to install Meep - the >> configure/make/installs for HDF5, libctl, and meep (the rest is >> native to SuSE) went well and when I ran make check in Meep, it ran a >> bunch of tests, so Meep seems installed. I noticed it only ran with >> one CPU. I thought parallel Meep was only for clusters, and would >> natively use SMP-CPUs (I have a quad-core Athalon 64 SuSE 10.3 >> installation). Is this incorrect? >> >> Thank You In Advance >> Patti >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> meep-discuss mailing list >> [email protected] >> http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss > > ------------------------------------------------------------------------ > > _______________________________________________ > meep-discuss mailing list > [email protected] > http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
_______________________________________________ meep-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
