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
Update Coxeter Group documentation #22853
Comments
This comment has been minimized.
This comment has been minimized.
Reviewer: nthiery,tscrim |
Commit: |
Changed reviewer from nthiery,tscrim to Nicolas M. Thiéry,Travis Scrimshaw |
Changed author from aram.dermenjian to Aram Dermenjian |
Changed reviewer from Nicolas M. Thiéry,Travis Scrimshaw to none |
comment:7
Definitely something that should be done. However, perhaps we should change the width to |
comment:8
I specifically chose 500 because the 300px images were difficult to see. I tried 400 as well before settling on 500. An idea, which I couldn't find, I wanted to see if there's a way to limit the height by cropping instead of stretching. It looks like sphinx_plot always returns a square image, so when adding
or something we get a shrunk image which still has pointless whitespace. I couldn't find anything in the documentation about cropping, but if you do know of a way to crop, it'd be nice as some of the images definitely take up a lot of vertical room and would be nice to shrink them. Alternatively, I can reduce the size to 300px as is more standard with the knowledge that some images may be difficult to see. (Note the main difficulty in seeing the images was the words/symbols on the images, so I can potentially reduce the size as well if we don't care about being able to read labels on the images) |
comment:9
What is the dpi (or resolution) on your laptop? It might be hard to read because that is very high. Unfortunately I don't know enough about the |
comment:10
Just two comments for now:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
My dpi is fairly high, so I've gone ahead and reduced all the graphs to 300px. Can you look them over and see if they actually look good in the smaller size? @nthiery - sphinx seems to be lacking quite a lot when it comes to images. Hopefully they'll get to updating it in the near future so we can make plot look even more awesome. New commits:
|
comment:13
This looks good. Thank you for your work on this. |
Reviewer: Travis Scrimshaw |
comment:14
|
comment:15
I made some trivial reviewer changes that need a quick check. However, I am (still) unable to reproduce the docbuild failure Volker is getting. New commits:
|
Changed branch from u/tscrim/add_root_system_plots-22853 to u/aram.dermenjian/add_root_system_plots-22853 |
comment:34
I've gone ahead and just removed that plot. I tried cleaning my doc and making again, and as usual, everything worked well. I guess we'll need to run it through the patchbots to see if it works this time around. New commits:
|
comment:36
I didn't have too much time to investigate this, but this is probably the best way forward. IMO, it is better to send it back to the buildbots and see if Volker comes back again saying it fails since we need a specific patchbot to look at it. |
comment:37
|
comment:38
I'd appreciate it if you don't send me half-assed tickets on the vague hope that they work, I do have a lot of tickets to juggle and can't spend that much time on individual issues. |
comment:39
We would love to send you something that works, but the problem nobody other than you and one patchbot has been able to reproduce that failure. I tried asking for more information and your help (comment:17, comment:27) so we didn't have to do this back and forth. The error message that you keep posting does not contain any useful information. This seemed like the best lead from the patchbot report (comment:30), which actually had some more useful information and only seemed to apply to the now removed plot. Really what is going on is we are trying to find our way in the dark. Is there some way you can give us access to the machine where it does fail so we can experiment? If you're unwilling to help and unless somebody else has this failure, then we have to set it to positive review and give it to you to test it. |
comment:40
The error is still the
Jan Groenewald can get you access to the buildbots |
comment:41
Thank you. I will be e-mail Jan about the buildbot access and get to this in a few days (I will be traveling tomorrow from the US to South Korea). Which buildbot(s) does the failure occur on? Feel free to send me an e-mail directly about it. |
Changed branch from u/aram.dermenjian/add_root_system_plots-22853 to u/tscrim/add_root_system_plots-22853 |
comment:42
The problem is this test/plot:
I also now know why it fails and can reproduce it in a Sage session:
There is no Sage preprocessor run, so the bounding box gets evaluated to 0, which in turn, creates an empty
This is now #23200. This is not a dependency as the correct picture should be plotted, which means the bounding box should be a rational number, meaning we never get the empty That does not quite explain why we could not reproduce this failure locally, but it does explain everything else. I'm not going to bother with this last detail. New commits:
|
comment:43
Tested on my machine and everything seems to work correctly. Here's to hoping this time we have it. |
Changed branch from u/tscrim/add_root_system_plots-22853 to |
Changed commit from |
comment:45
Yeah! |
Update the documentation in combinat/root_system/plot with visual examples of the examples found in the current documentation.
Additionally, add categories/complex_reflection_or_generalized_coxeter_groups to the documentation as it seems to be missing altogether.
CC: @nthiery @tscrim @jm58660 @fchapoton
Component: documentation
Keywords: sagedays86
Author: Aram Dermenjian
Branch:
c083d5c
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/22853
The text was updated successfully, but these errors were encountered: