Re: [sage-combinat-devel] Sage-combinat won't run with #12940 applied
Sorry, I was traveling and missed this. The file name has been changed to 'affine_permtation.py' as recommended, which should remove the headaches mentioned. On Thursday, January 24, 2013 1:14:01 PM UTC+3, Andrew Mathas wrote: > > > > On Thursday, 24 January 2013 20:31:36 UTC+11, Anne Schilling wrote: >> >> Perhaps it should be disabled since *everyone* will have to remove those >> files (which is annoying). I am not sure. >> >> > Following Hugh's hint, I found that > sage -sync-build > took care of the problem. > > A > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Partition and tableau options in #13605
Hi Travis,
>This would change the import statements from `sage.combinat.partition` to
> `sage.combinat.partitions.partition`, thus I would think we would need some
> sort of deprecation for this for a user's .sage
> files. For the deprecation, I think what we would need to do is import all of
> the module level classes/functions and have them as deprecated aliases in
> `sage.combinat.partition.py`. However the UI
> would not change.
Wouldn't it suffice to have a deprecation for sage.combinat.partition in
/combinat/partition.py and have an alias there to
sage.combinat.partition.partition.
That would hopefully not be too much deprecation work at all since the UI does
not change.
>On creating a new directory/ies, instead of a partitions and tableaux
> directory, should we just have one directory for all partition-like objects
> (I guess we could call it the slight misnomer of
> partitions)?
I would have separate directories for partitions and tableaux.
> In a few papers (and the last version of the k-Schur book I saw) called it
> "French notation" and "English convention" and I followed that.
But I would think both are subsumed under "convention".
>I originally followed Stanley and used weakly increasing of the base (i.e.
> 1^2, 2, 3^2, 4^2). (See bottom of page 287 in EC II.) Though in long-hand,
> Stanley would write the partition as (4, 4, 3,
> 3, 2, 1, 1)...
For the usual partition notation we definitely want to keep the weakly
decreasing convention! For the exponential display, if Stanley uses increasing
convention, I would stick with that. I guess it is more useful when one
does not know the largest part, since one can just write
1^{a_1} 2^{a_2} with dots rather than \ell^{a_\ell} (\ell-1)^{a_{\ell-1}}
...
where \ell is sufficiently large.
Best,
Anne
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Lazify WeylGroup
I'm looking into changing matrix groups to libgap and it would be nice if all groups were lazily imported. You don't want to add libgap startup to the startuptime for every Sage session. Have you ever tried to clean that up? Right now WeylGroup is imported all over the place... -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] import_statements and #12543
On Sat, Jan 26, 2013 at 04:22:27PM +0100, Nicolas M. Thiery wrote: > On Sat, Jan 26, 2013 at 02:13:10PM +0100, Vincent Delecroix wrote: > > It is now a long time since the import_statements is in the queue > > (last discussion was [1] in May 2012) and I would like to move my > > patch (import_statements-vd.patch) to the trac server. Does anybody > > encounter some problems or have further suggestions ? Anne you own the > > ticket #12543 (opened in February 2012) and it seems that it is a good > > ticket to put the patch in. What do you think ? > > It's been working great for me. Let's get it in Sage! +1 Florent -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] import_statements and #12543
Hi Vincent, Sure, by all means, put your patch there and try to get it into Sage! Best, Anne On 1/26/13 5:13 AM, Vincent Delecroix wrote: > Hi all, > > It is now a long time since the import_statements is in the queue > (last discussion was [1] in May 2012) and I would like to move my > patch (import_statements-vd.patch) to the trac server. Does anybody > encounter some problems or have further suggestions ? Anne you own the > ticket #12543 (opened in February 2012) and it seems that it is a good > ticket to put the patch in. What do you think ? > > Best, > Vincent > > [1] > http://groups.google.com/group/sage-combinat-devel/browse_thread/thread/bfa63a8a39747c53/da08bfb8714ef869 -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] import_statements and #12543
On Sat, Jan 26, 2013 at 02:13:10PM +0100, Vincent Delecroix wrote: > It is now a long time since the import_statements is in the queue > (last discussion was [1] in May 2012) and I would like to move my > patch (import_statements-vd.patch) to the trac server. Does anybody > encounter some problems or have further suggestions ? Anne you own the > ticket #12543 (opened in February 2012) and it seems that it is a good > ticket to put the patch in. What do you think ? It's been working great for me. Let's get it in Sage! Cheers, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: AIM/ICMS Workshop on Online Databases in Edinburgh
> We got a lot done > It was a huge success indeed. Not to mention that we have now prepared the basis of a potential opportunity to foster the creation of a future and long-term plan to let all researchers contribute meaningfully to their communities by clicking on stuff. Nathann -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] import_statements and #12543
Hi all, It is now a long time since the import_statements is in the queue (last discussion was [1] in May 2012) and I would like to move my patch (import_statements-vd.patch) to the trac server. Does anybody encounter some problems or have further suggestions ? Anne you own the ticket #12543 (opened in February 2012) and it seems that it is a good ticket to put the patch in. What do you think ? Best, Vincent [1] http://groups.google.com/group/sage-combinat-devel/browse_thread/thread/bfa63a8a39747c53/da08bfb8714ef869 -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] AIM/ICMS Workshop on Online Databases in Edinburgh
Dear Sage-Combinat devs, The workshop "Online databases: from number theory to combinatorics" finished yesterday after a week full of discussions, action, and a bit of emotion :-). I'd like to take the occasion to thank all the participants for coming and trying hard to contribute to the overall goals of the project: - For combinat people to explore their potential needs for databases and web interfaces and get insight from the LMFDB and tools like cubic web. - For the LMFDB people to develop the LMFDB further and get insight from the combinat people on community development and high semantic implementation. - For everybody to explore venues for collaborations grounded on common needs, and learn more about databases and views thereupon from specialists of other fields like astronomy (Virtual Observatory) and professional programmers (logilab & cubic web) I have started throwing in some thoughts for the report. It aims to be a formal report for AIM and the NSF, but also at making a synthesis of the many discussions we had and the conclusions of the experiments we made [1]. It would be great if all participants to the workshop could have a look and add a quick description of the projects they worked on, the conclusions they draw out of it general impressions and future plans and dreams. For various reasons, including snow, unusual setting and insufficient skills from the organizers (i.e. me), the program was a bit messy. We got a lot done, but I was hopping for more collaborative work toward the main goals of the workshop. In particular, there are many topics of discussions that were not brought up, and it would be great if the report included things like an good overview of our potential needs in combinatorics. Please anyone use the occasion to speak up! Let me conclude by thanking again the participants, my coorganizer Paul-Olivier, our supporters David and Brian, and the AIM and ICMS staff. Cheers, Nicolas Paul: please forward/edit for the non Sage-Combinat participants. [1] http://combinat.sagemath.org/misc/file/tip/grants/2011-11-01-AIM-workshop/report.tex Anyone with trac/sage-combinat queue access can edit the file after cloning the misc repository: hg clone http://combinat.sagemath.org/misc/ -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Free Group Algebra bonanza
Hi Volker,
On Fri, Jan 25, 2013 at 09:48:18AM -0800, Volker Braun wrote:
> sage: F. = FreeGroup()
> sage: F.algebra(ZZ)
> Group algebra of Free Group on generators {a, b} over Integer Ring
> sage: GroupAlgebra(F, ZZ)
> Group algebra of group "Free Group on generators {a, b}" over base ring
> Integer Ring
Thanks for the report, and sorry for leaving this behind.
The second one (GroupAlgebra) should disappear or become an alias for
the first one, once all missing features (if any) are ported over to
F.algebra(ZZ).
The point of F.algebra(ZZ) is that it's a functorial construction: the
more structure you have on F (Magma, Monoid, Semigroup, Group,
FiniteGroup, RootLatticeRealization, ...) the more structure you have
on the its algebra, and that without code duplication.
I can't promise to work on it anytime soon, so please anyone go for
it if you feel like it.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil"
http://Nicolas.Thiery.name/
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
