Macaulay2 / Macaulay2/M2

a new problem: notice the "bad prompt":

Open
#1,858 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Interpreter
Dominant language
Macaulay2
Stars
435
Forks
297
Avg merge
4d 20h
Merged PRs (30d)
11

Description

Nope, but here is a new problem: notice the "bad prompt":

Macaulay2, version 1.17.1.1
with packages: ConwayPolynomials, Elimination, IntegralClosure, InverseSystems, LLLBases,
               MinimalPrimes, PrimaryDecomposition, ReesAlgebra, Saturation, TangentCone

i1 : input "~/src/M2/M2.git/M2/alarm-bug.m2"

ii2 : needsPackage "Matroids"

oo2 = Matroids

oo2 : Package

ii3 : M0 = matroid graph({{a,b},{b,c},{c,d},{d,e},{e,f},{f,g},{f,h},{c,h},{c,f},{a,g},{d,g}})

oo3 = a matroid of rank 7 on 11 elements

oo3 : Matroid

ii4 : M1 = matroid graph({{a,b},{b,c},{c,d},{d,e},{e,f},{f,g},{f,h},{c,h},{c,f},{a,g},{a,h}})

oo4 = a matroid of rank 7 on 11 elements

oo4 : Matroid

ii5 : T = ZZ[x,y]

oo5 = T

oo5 : PolynomialRing

ii6 : assert(isWellDefined M0 and isWellDefined M1)

ii7 : assert(tuttePolynomial(M0, T) === tuttePolynomial(M1, T))

ii8 : F1 = set{0,1,2,3,7}

oo8 = set {0, 1, 2, 3, 7}

oo8 : Set

ii9 : F2 = F1 + set{5,8}

oo9 = set {0, 1, 2, 3, 5, 7, 8}

oo9 : Set

ii10 : assert(areIsomorphic(uniformMatroid(2,2), minor(M0, F1, M0.groundSet - F2)))

ii11 : assert(areIsomorphic(M0, matroid graph edges graph M0_*))

ii12 : 

i13 : 
<--bad prompt--> : 55

o13 = 55

Originally posted by @DanGrayson in https://github.com/Macaulay2/M2/issues/1392#issuecomment-765553097

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the transcript with the referenced M2/alarm-bug.m2 input and compare the behavior with the original issue 1392 discussion. Trace why the interactive session emits <--bad prompt--> after the final assertion; done means the reproduction no longer shows the bad prompt and the behavior has regression coverage.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.