-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Larix/feff fitting] plot each path not working under Windows (Larch 0.9.78) #515
Comments
@nams-549 well, that probably depends on what the problem is. What operating system are you using? What you did to install, update, or try to run the program? Were there any error messages? One possibility (though maybe not the best one) would be to delete the installation folder completely and reinstall from the installer. |
@newville I got a couple of reports from Windows users (with Larch 0.9.78) about an error xraylarch/larch/wxxas/feffit_panel.py Line 1279 in 570630f
I have only the following trace from a user:
But I cannot reproduce it under Linux and latest master version. Any further idea? |
@maurov @nams-549 Yes, this is fixed in the master branch. A warning about that though: I have been playing with the ability to plot a sum of paths (and individual paths) without data. I believe this is now working, but I changed a lot of code in this area (in feffit_panel.py). I have tested it on some real examples but feel like I should probably test it more before all of that is released again. |
@newville Hi, Newville, may I ask how to get this bug fixed? I installed Larch from conda-forge. Should I just wait for another release? Thanks |
You can do a pip install of the nightly builds, as described in the documentation. |
I'm having this issue in Linux too. Just installed the most recent version. |
@josephzsombor Yeah, sorry. This is fixed in the nightly build. See https://xraypy.github.io/xraylarch/installation.html#installing-the-development-version |
I updated larch and now larix isn't working. How do I resolve?
The text was updated successfully, but these errors were encountered: