Demeter 0.9.24 does work for me on El Capitan (10.11.5). In fact, I did a
sudo port upgrade outdated
and many packages updated, and and Demeter still lauches and seems to run.
Yuan, you say you upgraded to 10.11. Does that mean you had Macports /
Demeter working on 10.10 and it failed to
Hi Joe,
Thanks for your reply. In my first email I forgot to mention that I did install
MacPorts-2.3.4-10.11-ElCapitan.
Yuan
On 7/21/16, 11:27 AM, "Ifeffit on behalf of Fowler, Joseph W. (Assoc)"
Dear Yuan,
Thanks for the log file, but I’m afraid I don’t know what your Mac Ports
problem is. The log file indicates a failure to fetch the archive at all. After
waiting a day, did the problem go away?
My workplace has lots of rules about how and when to upgrade to El Cap. As a
result, I
I don't think it works on el capitan
Sent from my iPhone
> On Jul 20, 2016, at 22:37, Ping, Yuan wrote:
>
> Dear all,
>
> I recently upgraded my mac to OSX El Capitan, and tried to install demeter
> following the steps at http://bruceravel.github.io/demeter/
>
> XQuartz
On 07/20/2016 06:59 PM, Neil M Schweitzer wrote:
In terms of the DWF’s in general, what value is considered too high? I
know the DWF’s have a component that relates to temperature induced
disorder in the scattering shell and a component that relates to
physical disorder in the scattering shell,
On 07/20/2016 06:59 PM, Neil M Schweitzer wrote:
I found a bug in the log files in the history window. I am running
Demeter 0.9.21 on Windows 7. When I generate a new fit, if I change the
k-range of the fit, the k-range of previous fits in the history window
will also change to the current range