|
Size: 2712
Comment:
|
Size: 3086
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| * There were many changes to libSingular as part of the refactoring effort. The Sage interface needs to be adapted to these. This should be a matter of renaming the functions that are called in Sage and adding the current ring as an argument (modulo bugs in libpolys). | There were many changes to libSingular as part of the refactoring effort. The Sage interface needs to be adapted to these. This should be a matter of renaming the functions that are called in Sage and adding the current ring as an argument (modulo bugs in libpolys). * create spkg for refactored Singular * search/replace calls to libSingular in the Sage library to get the interface to compile & link |
| Line 20: | Line 23: |
| Instructions for building latest experimental code: http://github.com/Singular2/singular2.github.com/wiki/New-TODOs | Bug hunt through Singular kernel code. An adventure no hacker can resist. |
| Line 22: | Line 25: |
| * Bug hunt through Singular kernel code. An adventure no hacker can resist. | * build refactored Singular: http://github.com/Singular2/singular2.github.com/wiki/New-TODOs * run test suite with debug version of Singular which dumps stack traces on error. (kernel/cntrl.cc should be modified to define `DEBUG_STOP` instead of `INTERACTIVE`) === Compiler warnings === '''People:''' There are lots of compiler warnings... |
Sage/Singular Days Projects
Contents
- Sage/Singular Days Projects
Update Singular spkg
People: Simon, Burcin (hopefully Martin as well)
Update the Singular interface to work with libpolys
People: Burcin, Oleksandr
- There were many changes to libSingular as part of the refactoring effort. The Sage interface needs to be adapted to these. This should be a matter of renaming the functions that are called in Sage and adding the current ring as an argument (modulo bugs in libpolys).
- create spkg for refactored Singular
search/replace calls to libSingular in the Sage library to get the interface to compile & link
Refactored Singular should pass it's test suite
People: Burcin, Oleksandr, Hans
Bug hunt through Singular kernel code. An adventure no hacker can resist.
build refactored Singular: http://github.com/Singular2/singular2.github.com/wiki/New-TODOs
run test suite with debug version of Singular which dumps stack traces on error. (kernel/cntrl.cc should be modified to define DEBUG_STOP instead of INTERACTIVE)
Compiler warnings
People:
There are lots of compiler warnings...
Plural/SCA
People: Oleksandr
- Bug hunt at PLURAL/SCA kernel code: (left) std etc...
Try out some dynamic modules
People: Oleksandr
Try building & using dynamic modules
Blackbox objects
People: Oleksandr
Try building & using blackbox objects, e.g. coefficient domain as a wrapper for coeffs
Interface to Singular's modules
People: Hiep, Burcin
- This shouldn't be so hard since libSingular uses the same type for polynomials and module elements
Review Simon's letterplace patches
People:
Plural interface
People: Burcin
Rebase the patch at #4539 plural wrapper to 11068 implementation of one and two sided ideals of noncommutative rings
Use libpolys for function field arithmetic
People: Burcin
- libpolys has better function field arithmetic now, we should wrap that in Sage.
This is also relevant #9054 create a class for basic function field arithmetic
FLINT integration
People: Fredrik
- Add missing utility and conversion functions to FLINT
- Use FLINT in Singular
Beginner tickets
to practice preparing and submitting patches, for people new to the Sage development process:
#8857 lcm over Q[x] broken (not any more)
.intersect() method of ideals should allow multiple arguments.
add an alias primary_decomposition_complete() -> complete_primary_decomposition() in the ideal class