Skip to content

Documentation refresh - Atlanta workshop (rebased)#4345

Draft
aalmousa wants to merge 94 commits into
Macaulay2:developmentfrom
aalmousa:doc-updates-rebased
Draft

Documentation refresh - Atlanta workshop (rebased)#4345
aalmousa wants to merge 94 commits into
Macaulay2:developmentfrom
aalmousa:doc-updates-rebased

Conversation

@aalmousa
Copy link
Copy Markdown
Member

@aalmousa aalmousa commented May 21, 2026

This draft PR supersedes #4341 without rewriting the shared aalmousa:doc-updates branch.

Changes from the original cleanup pass:

  • rebased the documentation refresh branch onto current development
  • preserved the shared original branch by publishing the rebased result on doc-updates-rebased
  • restored the legacy doc-node form for map(GaloisField,GaloisField) so Style documentation checks no longer fail during package installation

Please use this PR for review instead of #4341 while the shared branch remains in place.

eisenbud and others added 30 commits September 26, 2023 09:30
aalmousa and others added 9 commits May 21, 2026 15:11
Enrich the Macaulay2 debugging docs (ov_debugging.m2) with a detailed, step-by-step example session: load a demo file, show available symbols (listUserSymbols), display function source (code), trigger the debugger and inspect locals (listLocalSymbols), and demonstrate debugger commands (step, break, end) and the errorDepth setting. Also documents non-interactive error handling using try and trap and includes illustrative REPL output to make debugging workflows clearer for users.
Replace Kisun Lee's contact email in NumericalCertification.m2 package metadata from kil004@ucsd.edu to kisunl@clemson.edu to reflect the author's updated contact information.
Add TO entries for the debugging commands 'continue' and 'trap' in M2/Macaulay2/packages/Macaulay2Doc/ov_debugging.m2 so they appear in the module's exported TO list.
Add a trailing space after "deeper." in M2/Macaulay2/packages/Macaulay2Doc/ov_debugging.m2 to ensure correct spacing when the documentation strings are concatenated/printed. This is a minor whitespace-only formatting fix to improve output readability.
Example
R = ZZ/101[s,t];
C = res ideal(t);
isVirtual(ideal(s,t), C, Strategy=>"Determinantal")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is a single graded resolution, it seems not in the spirit of Mike Loper's paper. I believe this node doesn't have an example because this option already has an example about 20 lines above, so I suggest just merging this node into the node above.

If it's easier for you, I can do this in a separate PR later or can push directly to your branch if you prefer.

PARA{}, "Here are some examples illustrating some uses of this
package.",
EXAMPLE {
"R = matrix(QQ, {{1,0},{0,1}})",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Making this slightly more interesting:

Suggested change
"R = matrix(QQ, {{1,0},{0,1}})",
"R = matrix(QQ, {{1,0},{-2,1}})",

Comment on lines +177 to +178
--document { Key => {(gin,Ideal)}, }
--document { Key => {(gin,QuotientRing)}, }
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big deal but feel free to just remove these lines.

SUBSECTION "Combinatorial properties of the Kunz cone",
UL{
TO coneEquations,
TO coneEquations,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what happened with the indentation here (and about 30 lines below) but would be good to avoid this. Again, not a huge deal in a 4000-line PR.

Headline => "Methods for virtual resolutions on products of projective spaces",
Authors =>{
{Name => "Ayah Almousa", Email => "aka66@cornell.edu", HomePage => "http://pi.math.cornell.edu/~aalmousa "},
{Name => "Ayah Almousa", Email => "aalmousa@uky.edu", HomePage => "http://pi.math.cornell.edu/~aalmousa "},
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you want to update your website too?

Comment on lines +1 to +5
newPackage ("Tutorials",
Version => version#"VERSION",
Headline => "tutorials and teaching materials for Macaulay2",
HomePage => "https://macaulay2.com/",
Authors => { -* see the contributors listed on the main page *- },
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to:

  1. add a date or version to indicate last update
  2. list at least one person as maintainer and reference for who should be contacted for updates.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this file meant to be committed? The wiki might be more appropriate for it, or at least in the packages/Macaulay2Doc/ subdirectory rather than here.

Comment thread README.md
Comment on lines +34 to +36
This fork may still be used to stage documentation-refresh work through
`aalmousa/M2` issues and project items, but upstream contributions land through
`Macaulay2/M2:development`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand this PR is still a draft, just leaving a comment here so we don't forget to remove this when it's ready.

Subnodes => {
"T-spread managing",
TO "tLastMon",
Key => {TSpreadIdeals},
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to fix the indentation as you edit. Perhaps at some point we will have a proper linter to fix this problem.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The helpers isVectScalar and convertScalarVect should not be exported, so this documentation likely will be removed once I update the package.

quotient(Ideal, RingElement) := Ideal => opts -> (I, f) -> quotient(I, ideal f, opts)
Ideal : Ideal := Ideal => (I, J) -> quotient(I, J)
Ideal : Number :=
Ideal : Number := Ideal => opts -> (I, f) -> quotient(I, ideal f, opts)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to break as Ideal : Number can't accept options. The other change above is also unnecessary, so I suggest reverting changes to this file.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect this will conflict with @joel-dodge's pending PR.

Copy link
Copy Markdown
Contributor

@joel-dodge joel-dodge May 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ty for calling this out. It's fine with me for this monster to be merged before mine and I'll deal with resolving conflicts in my PR.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would probably be easy to revert the changes to this one file and leave it to you to fix it in your PR, but up to you. If you're okay with waiting, it would be good to mark yours as draft so it doesn't get accidentally merged.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

excellent ty i am going to push a PR targeting this branch to do this.

TT "SubringLimit => n", " -- an option for ", TO "kernel", " which
causes the computation of the kernel of a ring map to stop after ", TT "n", "
elements have been discovered."
Key => {(kernel,Matrix),
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what happened here but this indentation seems strange. It would be preferable to translate to SimpleDoc form if every line of this node is being edited.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 ack this makes sense. i will switch to simple doc format.

Comment on lines +3 to +4
(wedgeProduct, ZZ, ZZ, Module)
wedgeProduct
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: the order of the keys determines which one is the "PrimaryKey", which in turn results in the choice of url, e.g. in this case it'll be .../_wedge__Product_lp__Z__Z_cm__Z__Z_cm__Module_rp.html. I tend to put the main method above to simplify this link.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

excellent. will update to switch the order.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume the changes here will conflict with pending documentation changes from the debugging team.

Copy link
Copy Markdown
Member

@mahrud mahrud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments to hopefully help with the final push before this PR is ready. Let me know if you have trouble with getting the builds to succeed, I can take a look.

@mahrud
Copy link
Copy Markdown
Member

mahrud commented May 22, 2026

Oh, also, AI disclosure, if applicable, would be appreciated :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants