#16723: beta-adic
-------------------------------------+-------------------------------------
Reporter: mercatp | Owner: mercatp
Type: PLEASE CHANGE | Status: new
Priority: minor | Milestone: sage-feature
Component: PLEASE CHANGE | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: u/mercatp/beta- | Commit:
adic | 827d9524f01fc485a274afca6101422e13e6341b
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by mercatp):
* priority: major => minor
* owner: => mercatp
* milestone: sage-6.4 => sage-feature
Old description:
New description:
This ticket gives a implementation of beta-adic monoids, as described in
the article http://www.latp.univ-mrs.fr/~paul.mercat/Publis/Semi-
groupes%20fortement%20automatiques.pdf
It permit to compute the beta-adic monoid corresponding to a WordMorphism,
to draw limit sets of beta-adic monoid, to compute relations automaton and
reduced words automaton (defined in the article). For that I re-
implemented the Automata.
This ticket is too big to be included directly into sage : I forsee to cut
it in small parts that I will try to include in sage when it will be
completly implemented, documented and well tested.
--
Comment:
Replying to [comment:4 kcrisman]:
> This is pretty cryptic until you start reading the code. Could you put
a brief description of what you are implementing in the "Description" area
of the ticket so new people coming to it know what beta-adics are and why
they should be in Sage? Otherwise it means searching a bit more through
the proposed branch than necessary :(
>
Sorry to be cryptic. I've writted a description.
I think that these tools can be useful for others people (mainly
researcher on beta-expansion, rauzy fractals, quasi-cristals etc...)
> Also, I am having a hard time finding any reference to these objects
other than in your own papers. But I do find other references to beta-
adic which seem to mean something else (though with "adic" of course they
are somehow related).
There are several names for that : beta-adic, beta-expansions, non-
standard numeration systems, etc...
I don't know what is the better name for that, so I choosed the name I
used (in french) in my article.
> I don't know what our policy is on that; Purple Sage used to exist for
that context but I think it may be defunct.
I did'nt know Purple Sage. If it was not defunct, you're right, it would
be more appropriate. But the last version has the date oct-2010...
> Don't take this as criticism, but rather request for clarification;
these files are large enough that it would be helpful to know that others
will be interested in using them; especially if the name may be fluid it
would be unfortunate to lock ourselves in a name, though that may be
unavoidable.
>
As I explain now in the description, I plan to cut this ticket into
smaller ones that could be inclued in sage. I would like to improve
Automaton first (because I need it), then add BetaAdicMonoid (maybe I'll
change the name if I find a better one) and then modify WordMorphism to
use BetaAdicMonoid.
> (I suppose this all applies to #15883 as well, though less so.)
The ticket #15883 is an old copy of this ticket that didn't worked with
sage-6.2.
I should combine the two tickets, but I don't know how to do it.
--
Ticket URL: <http://trac.sagemath.org/ticket/16723#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
