Re: [sage-devel] A bug with modules with basis

2022-05-19 Thread Kwankyu Lee 


On Friday, May 20, 2022 at 1:38:02 AM UTC+9 dim...@gmail.com wrote:

> > which surprises me by its presence in the basic level. I looked through 
> the code, but it is not obvious where and what to fix. I suspect there is a 
> flaw in the design of modules with basis since this "order" thing is not 
> relevant with the above module. 
>
> in docs of A.submodule() one sees: 
>
> At this point, this method only works for finite dimensional 
> submodules and if matrices can be echelonized over the base ring. 
>
> So it's just not implemented.

 
I see. So I touched a weak point of Sage. Then the ticket could be used to 
soften the rough edge.

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c75ce997-ed7f-4f13-91c7-eddc18cc7861n%40googlegroups.com.

[sage-devel] Re: Sage 9.6 Release Tour moved to the Trac wiki - let's finalize it!

2022-05-19 Thread Matthias Koeppe 
On Saturday, April 16, 2022 at 3:09:02 PM UTC-7 Matthias Koeppe wrote:

> I have moved it from the old Sage wiki to 
> https://trac.sagemath.org/wiki/ReleaseTours/sage-9.6
>
> This now allows all developers to edit it -- a legacy sage-trac account is 
> not required. Please help!
>

https://doc.sagemath.org/ has been updated to Sage 9.6 (thanks, Harald). 
So descriptions of new features can now link to the updated reference 
manual.

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f5bcaa31-6f41-4319-919c-6b359798ba88n%40googlegroups.com.

Re: [sage-devel] A bug with modules with basis

2022-05-19 Thread Dima Pasechnik 
On Thu, May 19, 2022 at 3:05 PM Kwankyu Lee  wrote:
>
> Hi,
>
> I encountered this bug
>
> sage: S. = PolynomialRing(QQ)
> sage: A = S**2
> sage: A
> Ambient free module of rank 2 over the integral domain Multivariate 
> Polynomial Ring in x, y, z, w over Rational Field
> sage: A.submodule([vector([x-y,z-w]), vector([y*z, x*w])])
> ...
> TypeError: _vector_() got an unexpected keyword argument 'order'
>
> which surprises me by its presence in the basic level. I looked through the 
> code, but it is not obvious where and what to fix. I suspect there is a flaw 
> in the design of modules with basis since this "order" thing is not relevant 
> with the above module.

in docs of A.submodule() one sees:

 At this point, this method only works for finite dimensional
 submodules and if matrices can be echelonized over the base ring.

So it's just not implemented.

> Please, experts on CombinatorialFreeModule leave advices to
>
> https://trac.sagemath.org/ticket/33868
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/366f3264-d375-487e-bd47-128e89fb173dn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3LgF9xk3g0Ngh7upWGWPHkj6dsZ3_rMTxD%3D8rTu4QRFw%40mail.gmail.com.

[sage-devel] A bug with modules with basis

2022-05-19 Thread Kwankyu Lee 
Hi,

I encountered this bug

sage: S. = PolynomialRing(QQ) 
sage: A = S**2 
sage: A 
Ambient free module of rank 2 over the integral domain Multivariate 
Polynomial Ring in x, y, z, w over Rational Field 
sage: A.submodule([vector([x-y,z-w]), vector([y*z, x*w])])
...
TypeError: _vector_() got an unexpected keyword argument 'order'

which surprises me by its presence in the basic level. I looked through the 
code, but it is not obvious where and what to fix. I suspect there is a 
flaw in the design of modules with basis since this "order" thing is not 
relevant with the above module. Please, experts on CombinatorialFreeModule 
leave advices to

https://trac.sagemath.org/ticket/33868

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/366f3264-d375-487e-bd47-128e89fb173dn%40googlegroups.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

2022-05-19 Thread Vincent Delecroix 




Le 16/05/2022 à 12:35, Dima Pasechnik a écrit :

On Mon, May 16, 2022 at 8:03 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:


I would say that code with parallel computations + cypari2 should not
be merged (as cypari2 does not support it).


is it parallel multiprocessing, or parallel multithreading?


True : multiprocessing is not a problem with cypari2. Only
multithreading must be avoided.


If you need parallel + PARI then use the C library directly with the
appropriate threads locks.

If the problem comes from somewhere else, then it would better be sorted
out.

Best
Vincent

Le 16/05/2022 à 06:42, 'Travis Scrimshaw' via sage-devel a écrit :

That sure seems like it. So what should we do about the ticket? Would there
be opposition to merging this piece of code, as there doesn't seem like
there is a fix coming for the likely underlying cypari bug anytime soon?

Best,
Travis


On Sunday, May 15, 2022 at 4:14:31 PM UTC+9 vdelecroix wrote:


Probably related to https://github.com/sagemath/cypari2/issues/107 ?

Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :

Hi everyone,
On ticket #30423 , Dan, Willie,
and I have been working on a parallel-computation based implementation

for

computing F-matrices that are used in math physics. However, we have been
seeing some doctest failures sporadically that involve segfaults and
linked-list corruption from (cy)PARI. Here are the logs from testing with
the first and the last having full tracebacks.

http://sporadic.stanford.edu/badlog-match
http://sporadic.stanford.edu/badlog
http://sporadic.stanford.edu/badlog1
http://sporadic.stanford.edu/badlog2
http://sporadic.stanford.edu/badlog3

The first question would be if anyone has an idea about what is causing
this. I have this impression that PARI is thread-safe, but I am wondering
if cypari is also thread/parallel-safe or if there are any specific

things

that we should be careful about. (We’ve already had to work around a
pickling issue with polynomials IIRC.)

Second question is that because this is a Heisenbug and I suspect it is
something upstream (and so far, nobody has been able to reproducing it
during an interactive version of Sage), I was wondering what the policy
would be for merging the ticket. I recall in the past that we have merged
tickets with Heisenbugs with followup tickets noting the behavior, but I

am

not 100% sure about that (and I wouldn’t necessarily know how to find any
explicit examples). I was wondering if we could merge the ticket in an
early beta version so that many people/systems can test it to see if it
becomes more reproducible; of course this is assuming that the build bots
are not consistent in reproducing this. Should we just mark any offending
test(s) as “# known bug” and is there some general policy about this?

Thanks,
Travis








--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fd05e9f5-52b2-f2f8-bc02-c968c0a70e79%40gmail.com.




--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8a34b501-51b9-595a-b5d3-c81d63c55ced%40gmail.com.