Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Varieties v0.3 #3517

Draft
wants to merge 225 commits into
base: development
Choose a base branch
from
Draft

Varieties v0.3 #3517

wants to merge 225 commits into from

Conversation

mahrud
Copy link
Member

@mahrud mahrud commented Oct 15, 2024

This PR contains work throughout Spring and Summer 2024, including at the workshop at Utah. Complexes of sheaves are added, but are currently disabled until the Complexes package can be preloaded. Lots of work remains.

cc: @kellerlv @ggsmith @Devlin-Mallory @ritvikrr @johndcobb

mahrud and others added 30 commits October 15, 2024 03:37
@mahrud
Copy link
Member Author

mahrud commented Oct 15, 2024

I'm not sure if @mikestillman has forgotten about mikestillman#38, but this PR also includes those changes.

@mahrud
Copy link
Member Author

mahrud commented Oct 15, 2024

@d-torrance any idea what's happening here? I don't think this PR changes anything related to this ...

--*- compilation -*-

i1 : input "../../../../../Macaulay2/tests/normal/alarm.m2"

ii2 : -- no-check-flag (see https://github.com/Macaulay2/M2/issues/1392)
      -- test that alarms work
      
      time try ( alarm(1); while true do 1 ) else true
 -- used 1.13874s (cpu); 0.999088s (thread); 0s (gc)

oo2 = true

ii3 : 
      R = QQ[vars(0..24)]

oo3 = R

oo3 : PolynomialRing

ii4 : f = () -> (alarm 4; try res coker vars R else "ran out of time")

oo4 = f

oo4 : FunctionClosure

ii5 : time f()


 *** out of memory trying to allocate 128 bytes, exiting ***
Command exited with non-zero status 1
16.95user 4.55system 0:11.87elapsed 181%CPU (0avgtext+0avgdata 477640maxresident)k
0inputs+8outputs (0major+13659minor)pagefaults 0swaps

@d-torrance
Copy link
Member

Not sure. Apparently this test has been a problem before since we actually skip it when when running check Core (see #1867).

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.

6 participants