-
Notifications
You must be signed in to change notification settings - Fork 39
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
matplotlib markers not showing up... #1
Comments
No idea. That's really strange. |
What if you set the color, like |
With 1.4.2 and 1.4.1 I couldn't get the markers to appear - even by adding the colour letter... but with 1.4.0 everything works as in your original notebook example. Dunno what's changed in the latest releases but I'll stick with 1.4.0 for the workshop... what version did you use for the the notebook preparation? Might it be 1.4.0 also? |
Yep, I'm using 1.4.0 |
I'm having this same problem with matplotlib 1.4.2, but only if I use 'png' inline backend. If I switch to svg then the markers appear: %config InlineBackend.figure_format = 'svg' |
Discovered a lengthy thread here: mwaskom/seaborn#344 sounds like a matplotlib issue they're fixing. |
I encountered the same problem. In my case, it seems like the problem was caused by seaborn that I imported after matplotlib. without importing seaborn, the markers show up just fine. |
In some over zealous pre-workshop preparation I cloned the repo and attempted a quick run through of some of the code... when I use plt.plot(x, y, 'o') or similar the 'o' doesn't appear in the resulting plot... nor do other 'x', '.', ',' etc. If I leave it out altogether I get a line plot. I'm in a venv with the following installed:
stroML==0.2
astropy==0.4.2
emcee==2.1.0
ipython==2.3.0
matplotlib==1.4.2
numpy==1.9.0
pandas==0.15.0
scikit-learn==0.15.2
scipy==0.14.0
seaborn==0.4.0
Python 2.7.8... any ideas? Looking forward to a busy week of learning.
J.
P.S. the semicolon at the end of the plt.plot(); ... brilliant! Been looking for that for months...
The text was updated successfully, but these errors were encountered: