Closed BruceWestbury closed 4 years ago
I have been unable to push my commits. I get Permission Denied. I will try again in the morning.
Branch: u/Bruce/pathtableaux
Commit: b4a14f9
Description changed:
---
+++
@@ -1 +1,2 @@
-
+This is a project to implement an abstraction of rectification, evacuation and promotion. These are conventionally defined on standard tableaux using jeu-de-taquin. The file catalan.py gives a toy implementation. The file semistandard.py gives the implementation on (dual) semistandard tableaux.
+Once I am satisfied that these are working and reproduce the existing constructions, I intend to provide other implementations.
It seems there was something about this branch causing the git merge plugin to break so I have deleted the branch for now and will investigate further later.
Changed branch from u/Bruce/pathtableaux to none
It seems the branch was just the current develop
with no new commits on it, so maybe something about that scenario broke the plugin.
Replying to @embray:
It seems the branch was just the current
develop
with no new commits on it, so maybe something about that scenario broke the plugin.
Thanks for sorting that out. I struggled to follow the instructions and no doubt got it messed up.
Branch: u/Bruce/path_tableaux
Changed branch from u/Bruce/path_tableaux to u/Bruce/pathtableaux
Branch pushed to git repo; I updated commit sha1. New commits:
7d6fef0 | Imports into semistandard.py fixed |
Replying to @BruceWestbury:
Replying to @embray:
It seems the branch was just the current
develop
with no new commits on it, so maybe something about that scenario broke the plugin.Thanks for sorting that out. I struggled to follow the instructions and no doubt got it messed up.
No problem, not your fault at all.
Branch pushed to git repo; I updated commit sha1. New commits:
e5cb861 | Rectify added |
I now have the basic functionality in the two implementations I have committed. I would appreciate some feedback before I commit other implementations. I have attempted to explain the purpose of this project but no doubt I could do better.
Author: Bruce Westbury
I strongly believe that PathTableaux
should not be a category. You should just have an abstract base class (ABC) for the *Tableau
objects (the ElementMethods
is currently playing this role, but you're using a sledgehammer in place of a ball-peen). It is something that is easy to change back if there becomes a practical use/need for the category, but I think it puts more distance between the concrete class and the ABC code, which makes it harder to maintain.
At this point, I am thinking it might be best to make a new folder in the combinat
folder called tableau
with your new code (one file for the ABC and your other two files). Then it will become the eventual home for all tableau files (but moving those should be done on separate tickets).
Some other misc comments:
#!/usr/bin/env python2
?plot
instead of draw
.drawL
and drawC
might be best as separate standalone functions in the ABC file. Otherwise if you feel that they should be methods, then make them hidden by calling them _drawL
and _drawC
.draw_partition
in drawL
as an internal helper function (in drawC
, it makes sense because of the two for
loops and avoiding code duplication).EXAMPLES:
-> EXAMPLES::
(or missing altogether) when followed by code, which should be indented by 1), and some that should be at the class level or at the top of the module.Branch pushed to git repo; I updated commit sha1. New commits:
0ae66fe | Corrected formatting of doctests |
Hi Travis, Thank you for the feedback.
"At this point, I am thinking it might be best to make a new folder in the combinat folder called tableau with your new code (one file for the ABC and your other two files). Then it will become the eventual home for all tableau files (but moving those should be done on separate tickets)."
Could you please expand on this? I understand your suggestion to use an ABC instead of a category. I am not clear on how this should be done within the trac system. I understand that I could open a new ticket, copy the files by hand, and at some point delete the existing ticket. However I suspect you may mean a different approach.
Is the first step to create a new ticket with the new folder called tableau containing just one file with the ABC?
You can keep making commits and pushing to the same branch (and set the ticket back to needs_review once you're done fixing the issues you're aware of).
Branch pushed to git repo; I updated commit sha1. New commits:
cdef4c8 | Corrections to doctests with ellipsis |
Branch pushed to git repo; I updated commit sha1. New commits:
d562246 | Files moved to new directory |
Branch pushed to git repo; I updated commit sha1. New commits:
f20a5d1 | Parent classes added |
Branch pushed to git repo; I updated commit sha1. New commits:
4adad87 | All tests passed! |
Branch pushed to git repo; I updated commit sha1. New commits:
9c0cd75 | PathTableau_partitions added and more doctests |
I have made the changes suggested by Travis, including removing the Category and using an ABC instead. I am working on missing doctests. I would appreciate further feedback.
Description changed:
---
+++
@@ -1,2 +1 @@
-This is a project to implement an abstraction of rectification, evacuation and promotion. These are conventionally defined on standard tableaux using jeu-de-taquin. The file catalan.py gives a toy implementation. The file semistandard.py gives the implementation on (dual) semistandard tableaux.
-Once I am satisfied that these are working and reproduce the existing constructions, I intend to provide other implementations.
+This is a project to implement an abstraction of rectification, evacuation and promotion. These are conventionally defined on standard tableaux using jeu-de-taquin. The file catalan.py gives a toy implementation. I intend to provide other implementations.
Branch pushed to git repo; I updated commit sha1. New commits:
800560c | Modified all.py |
This is a project to implement an abstraction of rectification, evacuation and promotion. These are conventionally defined on standard tableaux using jeu-de-taquin. The file catalan.py gives a toy implementation. I intend to provide other implementations.
CC: @sagetrac-sage-combinat @tscrim @mantepse @anneschilling @deinst @kevindilks
Component: combinatorics
Keywords: fpsac2019
Author: Bruce Westbury
Branch/Commit:
9d3a838
Reviewer: Ben Salisbury, Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/25434