Opened 22 months ago

Last modified 3 months ago

#28316 needs_work enhancement

Making an is_dynamical_belyi_map() function

Reported by: bthompson Owned by:
Priority: minor Milestone: sage-9.4
Component: dynamics Keywords: dynamics, SI2019, sagedays103, sd104
Cc: Merged in:
Authors: Bianca Thompson, John Doyle, Adam Towsley Reviewers: Bella Tobin, Jamie Juul
Report Upstream: N/A Work issues:
Branch: u/bellatobin/Belyi (Commits, GitHub, GitLab) Commit: 7eddc1d98f4ae21a4608161ba25c51eb2ab69901
Dependencies: Stopgaps:

Status badges

Description

We define a dynamical Belyi map to be a dynamical system f:P^1->P1 where the branch points are contained in {0,1,infinity} and the post critical set is contained in {0,1,infinity}. This checks if a dynamical system is conjugate to a dynamical Belyi map.

Change History (16)

comment:1 Changed 22 months ago by bthompson

  • Branch set to u/bthompson/Belyi
  • Commit set to 95ea5f39d99a911f564d8dcd5e7c184cd2be72e2

comment:2 Changed 22 months ago by bthompson

  • Status changed from new to needs_review

comment:3 Changed 21 months ago by git

  • Commit changed from 95ea5f39d99a911f564d8dcd5e7c184cd2be72e2 to da74345df78b7e863265ae7c3bffae2c497cc201

Branch pushed to git repo; I updated commit sha1. New commits:

da74345Added is_dynamical_belyi() function to arithemetic dynamics files.

comment:4 Changed 18 months ago by git

  • Commit changed from da74345df78b7e863265ae7c3bffae2c497cc201 to 6cb6d405c8fe49c7326f82c004d17c930069f88c

Branch pushed to git repo; I updated commit sha1. New commits:

fd7ad4bMerge branch 'u/bthompson/Belyi' of git://trac.sagemath.org/sage into belyi
6cb6d40Created dynamical belyi map check with documentation

comment:5 Changed 18 months ago by git

  • Commit changed from 6cb6d405c8fe49c7326f82c004d17c930069f88c to b3a1db1bc3f19ab83ea8dc9229cf612a5e090adb

Branch pushed to git repo; I updated commit sha1. New commits:

b3a1db1Created dynamical belyi map check with documentation

comment:6 Changed 18 months ago by git

  • Commit changed from b3a1db1bc3f19ab83ea8dc9229cf612a5e090adb to a510f8e91f47f6c37e948eca8aa1bf65ab76cc7d

Branch pushed to git repo; I updated commit sha1. New commits:

a510f8efixed documentation error.

comment:7 Changed 18 months ago by bthompson

  • Keywords sd104 added

comment:8 Changed 18 months ago by bellatobin

  • Branch changed from u/bthompson/Belyi to u/bellatobin/Belyi

comment:9 Changed 18 months ago by bellatobin

  • Commit changed from a510f8e91f47f6c37e948eca8aa1bf65ab76cc7d to 7eddc1d98f4ae21a4608161ba25c51eb2ab69901
  • Status changed from needs_review to positive_review

New commits:

7eddc1dchanged description and example

comment:10 Changed 18 months ago by chapoton

  • Milestone changed from sage-8.9 to sage-9.0

reviewer name missing

comment:11 Changed 18 months ago by bthompson

  • Reviewers set to Bella Tobin, Jamie Juul

comment:12 Changed 18 months ago by vbraun

  • Status changed from positive_review to needs_work

Merge conflict

You also have a .BUILDSTART and git-trac-command subrepo checked in, please remove that

comment:13 Changed 16 months ago by embray

  • Milestone changed from sage-9.0 to sage-9.1

Ticket retargeted after milestone closed

comment:14 Changed 13 months ago by mkoeppe

  • Milestone changed from sage-9.1 to sage-9.2

Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date.

comment:15 Changed 8 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:16 Changed 3 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

Note: See TracTickets for help on using tickets.