Hello, I have followed the steps to install macports on my mac and it seems to be working. However when I went to port in demeter it start and fails rather quickly giving this error message. Error: org.macports.archivefetch for port libcxx returned: archivefetch failed for libcxx @3.7.1_0+universal What do I need to do in macports to get it to properly fetch libcxx? Thanks, Justin
Hi Justin,
Hmm, I'm not sure. Are you certain that all of Macports actually installed
correctly. Can you give a more complete set of commands and any error
messages?
On Nov 2, 2016 3:02 PM, "justin park"
Hello,
I have followed the steps to install macports on my mac and it seems to be working. However when I went to port in demeter it start and fails rather quickly giving this error message.
Error: org.macports.archivefetch for port libcxx returned: archivefetch failed for libcxx @3.7.1_0+universal
What do I need to do in macports to get it to properly fetch libcxx?
Thanks, Justin
_______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit Unsubscribe: http://millenia.cars.aps.anl.gov/mailman/options/ifeffit
Dear Matt, I’ve been fitting with Larch and found a few issues with some of the functions from code based on the example: examples/fitting/doc_example2a.lar. It’s for fitting two gaussians and an error function. Briefly, the two issues are related to fitting parameters for erf() and asymmetrical distribution functions like lognormal() or breit_wigner() not outputting results. 1. When trying to define parameters for the error function erf() in the params Group I get the following error: ufunc 'erf' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe’’. It appears to originate when minimizing and using the defined function. However if I simply define erf_cen=531 (explicit definition) and leave other definitions for erf_amp and erf_wid alone, minimize() appears to work but obviously does not fit for centering of the error function. That’s my current workaround. Any comments on this or a better solution would be appreciated. You can find the particular section of code on line 139 of the attached script where I redefine params so it “works". The attached data-set is also included so you can also see my fit. 2. When trying to use any built-in line shape functions other than gaussian, lorentzian, or pvoigt I do not get a functioning fit. The minimization proceeds (e.g. with lognormal() or breit_wigner() ) without error but no results are plotted. I am interested to use the asymmetric functions in an effort to better fit the first feature in my data where spectra after the first 25 start to not agree by ~0.5 eV. You can try switching out different plotting functions in lines 79, 80, and 81 of my code to replicate this. I was going to start digging into the function definitions themselves in comparison to the working ones but wanted to bring this to your attention now. I am working on macOS Sierra 10.12.1 with a mid 2015 MacBook Pro Retina using Python 2.7. Kind Regards, Sean Sean Fackler, PhD Joint Center for Artificial Photosynthesis Lawrence Berkeley National Lab 1 Cyclotron Rd Mail Stop 30R0205 Berkeley CA, 94720 Mobile: 609-613-8734
Hi Sean,
On Fri, Nov 18, 2016 at 6:09 PM, Sean Fackler
Dear Matt,
I’ve been fitting with Larch and found a few issues with some of the functions from code based on the example: examples/fitting/doc_example2a.lar. It’s for fitting two gaussians and an error function. Briefly, the two issues are related to fitting parameters for erf() and asymmetrical distribution functions like lognormal() or breit_wigner() not outputting results.
1. When trying to define parameters for the error function erf() in the params Group I get the following error:
ufunc 'erf' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe’’.
It appears to originate when minimizing and using the defined function. However if I simply define erf_cen=531 (explicit definition) and leave other definitions for erf_amp and erf_wid alone, minimize() appears to work but obviously does not fit for centering of the error function. That’s my current workaround. Any comments on this or a better solution would be appreciated. You can find the particular section of code on line 139 of the attached script where I redefine params so it “works". The attached data-set is also included so you can also see my fit.
When reporting a problem, please try to isolate the actual problem as much as possible. Your script is too long and complex to easily read and try to debug. It also runs for a long time. So, I would say "your script worked" -- it ran for a while without error before I killed it. It took me a while to figure out what precisely you were saying was not working. I suspect that the problem is with some of the magic that makes p1 = pars.amp1 * gaussian(data.e, pars.cen1, pars.wid1) p2 = pars.amp2 * gaussian(data.e, pars.cen2, pars.wid2) p3 = pars.amp3 * gaussian(data.e, pars.cen3, pars.wid3) e1 = pars.off + pars.erf_amp * erf(pars.erf_wid * (data.e - pars.erf_cen)) when 'pars.erf_wid' is a Parameter object and 'data.e' is a Pandas.Series --neither of these are precisely numeric objects, and though coercion to a number works most of the time, it looks like it is not working inside the erf() function call. I believe that if you explicitly use the 'value' attribute of the parameters, this will work better: e1 = pars.off + pars.erf_amp * erf(pars.erf_wid.value * (data.e - pars.erf_cen.value)) FWIW, it works for gaussian() because each function argument is really a numpy array, pandas Series, or a Parameter, but with erf() the argument is a pandas.Series (or numpy array) of object type. I believe these coercion issues are fixed in lmfit (which started as a side-project of Larch, has taken on a life of its own). In fact, the basic fitting and lineshapes thing in Larch should just be replaced with lmfit. More people are using this so it's gotten far ahead of Larch especially for fitting data to sums of lineshapes. The Peak Fitting GUI I'm working on uses Larch for much of the processing, but lmfit for the actual fitting -- I'm hoping to get a first-release of this out soon. You might find lmfit somewhat easier to work with than Larch fitting too... Anyway, the short answer is: try using "pars.PAR.value" instead of "pars.PAR" if you run into trouble -- that will really be a float, not some Parameter object that tries to act like a float. --Matt Newville <newville at cars.uchicago.edu> 630-252-0431
Hi. I would appreciate hints about how to treat multiple domains in Athena. The simplest system would be one with only twofold rotational symmetry, but present in two domains rotated by 90°. Somehow equivalent to the case of unpolarized x-rays. I am fairly new to using Athena and i may have simply missed the answer in the documentation. Michael.
Michael, On Sun, Nov 20, 2016 at 5:41 AM, Karl-Michael Schindler < karl-michael.schindler@physik.uni-halle.de> wrote:
Hi.
I would appreciate hints about how to treat multiple domains in Athena. The simplest system would be one with only twofold rotational symmetry, but present in two domains rotated by 90°. Somehow equivalent to the case of unpolarized x-rays.
I am fairly new to using Athena and i may have simply missed the answer in the documentation.
Michael.
X-ray absorption averages over the atoms in the volume illuminated by the beam. As the beam is attenuated by the sample, fewer X-rays make it to portions of that volume at depth. If you have multiple local structures in your sample, the XAFS signal is a simple average of those local structures, weighted by the probability that an atom with a particular structure absorbs an X-ray. For a uniform sample with a mixture of sites, that weighting is the simply the fraction of atoms with each structure. If the sample is not uniform, it can be more complicated. In particular, heterogeneity that is a function of depth (say, a layered material) is more complicated, because atoms near the surface are more likely to absorb the X-ray than samples at depth. Hope that helps, --Matt
Hi Justin,
It should be "sudo port install libcxx."
After libcxx is installed, try installing demeter again.
I had to install almost all of the packages that demeter uses one-by-one. I
have no idea why, but it worked.
Sincerely,
Wayne
On Wed, Nov 2, 2016 at 12:49 PM, justin park
Hello,
I have followed the steps to install macports on my mac and it seems to be working. However when I went to port in demeter it start and fails rather quickly giving this error message.
Error: org.macports.archivefetch for port libcxx returned: archivefetch failed for libcxx @3.7.1_0+universal
What do I need to do in macports to get it to properly fetch libcxx?
Thanks, Justin
_______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit Unsubscribe: http://millenia.cars.aps.anl.gov/mailman/options/ifeffit
-- Wayne Lukens Staff Scientist Lawrence Berkeley National Lab
participants (6)
-
justin park
-
Karl-Michael Schindler
-
Matt Newville
-
Matthew Newville
-
Sean Fackler
-
Wayne Lukens