[sage-devel] Re: Final call for GitHub user names
Hi, There seems to be a lone instance of "aghitza" that's orphaned. The corresponding trac username is "AlexGhitza", and the github username is "aghitza". Best, Alex On Thursday, January 19, 2023 at 1:14:16 PM UTC+11 Kwankyu Lee wrote: > Dear readers, > > Attached unmapped_users.pdf is the list of usernames encountered in the > preparation of the migration from Trac to GitHub, *with no corresponding > GitHub user name*. We are planning to create mannequin GitHub ids > (connected with no real GitHub user) for the usernames in the list. > > *Check the list and if you are the owner of the username or know the > owner, then please inform us here about the owner (full name or Trac > username) and, if known, his/her GitHub user name.* > > - username: possibly misspelled or non-human > - known on trac: True if username belongs to a valid Trac account; False > otherwise > - mention:: True if username is mentioned in a ticket comment > - mention: False if username is found as reporter, owner, author, or in cc > of a ticket > - mannequin: planned mannequin id > - frequency: number of appearance times in Trac > > For more information, visit > https://github.com/sagemath/trac-to-github/issues/77 > -- 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/09a128d2-5ce7-4e1f-a9a2-6b2504009be7n%40googlegroups.com.
[sage-devel] Re: manual memory management for GAP?
As far as I can tell the actionable part of that thread is Dima's
suggestion to use the function set_gap_memory_pool_size() from
interfaces/gap.py but as I pointed out above, that function has disappeared
from sage-9.5 onwards.
Best,
Alex
On Tuesday, June 21, 2022 at 1:06:15 PM UTC+10 Nils Bruin wrote:
> Perhaps this message (see the thread it's in for context) applies to your
> situation?
>
> https://groups.google.com/g/sage-devel/c/ntuqDmruI8w/m/vJOv6mgqCgAJ
>
> On Monday, 20 June 2022 at 19:30:04 UTC-6 AlexGhitza wrote:
>
>> Thanks, John.
>>
>> But, I should have mentioned that we tried that and it does not seem to
>> work (unless I'm missing something):
>>
>> ┌┐
>> │ SageMath version 9.6, Release Date: 2022-05-15 │
>> │ Using Python 3.10.3. Type "help()" for help. │
>> └┘
>> sage: gap("GAPInfo.CommandLineOptions;")
>> rec(
>> [... redacted ...]
>> o := "2g",
>> [... redacted ...]
>> )
>> sage: sage.interfaces.gap.gap_cmd = 'gap -r -o 128G'
>> sage: gap("GAPInfo.CommandLineOptions;")
>> rec(
>> [... redacted ...]
>> o := "2g",
>> [... redacted ...]
>> )
>> On Tuesday, June 21, 2022 at 10:59:38 AM UTC+10 John H Palmieri wrote:
>>
>>> According to
>>> https://ask.sagemath.org/question/61829/how-to-deal-with-gaperror-error-reached-the-pre-set-memory-limit/,
>>>
>>> try "sage.interfaces.gap.gap_cmd = 'gap -r -o 4G '".
>>>
>>> On Monday, June 20, 2022 at 5:12:27 PM UTC-7 AlexGhitza wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm trying to help out a friend who is computing automorphism groups of
>>>> lattices in Sage (using GAP under the hood). The computation is fairly
>>>> long and memory-intensive and eventually results in
>>>>
>>>> sage.libs.gap.util.GAPError: Error, reached the pre-set memory limit
>>>> (change it with the -o command line option)
>>>>
>>>> Apparently, until late last year, achieving the desired -o command line
>>>> option effect from within Sage was possible via something like
>>>>
>>>> from sage.interfaces.gap import get_gap_memory_pool_size,
>>>> set_gap_memory_pool_size
>>>> memory_gap = get_gap_memory_pool_size()
>>>> set_gap_memory_pool_size(9048*memory_gap)
>>>>
>>>> Now these functions are not available anymore, due to
>>>> https://trac.sagemath.org/ticket/32656
>>>>
>>>> Is it possible to achieve the same effect via some alternative method?
>>>>
>>>> Best,
>>>> Alex
>>>>
>>>
--
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/13a958af-1b17-4b4c-90de-aae2f543166en%40googlegroups.com.
[sage-devel] Re: manual memory management for GAP?
Thanks, John.
But, I should have mentioned that we tried that and it does not seem to
work (unless I'm missing something):
┌┐
│ SageMath version 9.6, Release Date: 2022-05-15 │
│ Using Python 3.10.3. Type "help()" for help. │
└┘
sage: gap("GAPInfo.CommandLineOptions;")
rec(
[... redacted ...]
o := "2g",
[... redacted ...]
)
sage: sage.interfaces.gap.gap_cmd = 'gap -r -o 128G'
sage: gap("GAPInfo.CommandLineOptions;")
rec(
[... redacted ...]
o := "2g",
[... redacted ...]
)
On Tuesday, June 21, 2022 at 10:59:38 AM UTC+10 John H Palmieri wrote:
> According to
> https://ask.sagemath.org/question/61829/how-to-deal-with-gaperror-error-reached-the-pre-set-memory-limit/,
>
> try "sage.interfaces.gap.gap_cmd = 'gap -r -o 4G '".
>
> On Monday, June 20, 2022 at 5:12:27 PM UTC-7 AlexGhitza wrote:
>
>> Hi,
>>
>> I'm trying to help out a friend who is computing automorphism groups of
>> lattices in Sage (using GAP under the hood). The computation is fairly
>> long and memory-intensive and eventually results in
>>
>> sage.libs.gap.util.GAPError: Error, reached the pre-set memory limit
>> (change it with the -o command line option)
>>
>> Apparently, until late last year, achieving the desired -o command line
>> option effect from within Sage was possible via something like
>>
>> from sage.interfaces.gap import get_gap_memory_pool_size,
>> set_gap_memory_pool_size
>> memory_gap = get_gap_memory_pool_size()
>> set_gap_memory_pool_size(9048*memory_gap)
>>
>> Now these functions are not available anymore, due to
>> https://trac.sagemath.org/ticket/32656
>>
>> Is it possible to achieve the same effect via some alternative method?
>>
>> Best,
>> Alex
>>
>
--
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/409c5f36-bfb6-4dae-8601-5f47da621cccn%40googlegroups.com.
[sage-devel] manual memory management for GAP?
Hi, I'm trying to help out a friend who is computing automorphism groups of lattices in Sage (using GAP under the hood). The computation is fairly long and memory-intensive and eventually results in sage.libs.gap.util.GAPError: Error, reached the pre-set memory limit (change it with the -o command line option) Apparently, until late last year, achieving the desired -o command line option effect from within Sage was possible via something like from sage.interfaces.gap import get_gap_memory_pool_size, set_gap_memory_pool_size memory_gap = get_gap_memory_pool_size() set_gap_memory_pool_size(9048*memory_gap) Now these functions are not available anymore, due to https://trac.sagemath.org/ticket/32656 Is it possible to achieve the same effect via some alternative method? Best, Alex -- 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/09b50ba3-7cd9-405f-86bd-e6db9e622213n%40googlegroups.com.
Re: [sage-devel] bug in matrix solve over inexact coefficients?
Hi, On Saturday, May 23, 2020 at 3:55:06 AM UTC+10, Michael Orlitzky wrote: > > > This was changed to "do what MATLAB does" because of the numerical > issues inherent to inexact rings. While > > m = matrix(SR, [0]) > > is singular and the system `m*x == [1]` has no solutions, with > > m = matrix(SR, [0.01]), > > the system is easily solvable and we can't tell the difference between > the two. I think the real surprise here is that SR is an inexact ring. > It's not surprising that SR is inexact, since it has embedded inexact rings: sage: SR.has_coerce_map_from(RR) True sage: SR.has_coerce_map_from(RDF) True However, it has a mechanism for detecting whether a given element is exact: sage: SR(0).is_exact() True sage: SR(0.0).is_exact() False So one could envision checking whether the coefficient matrix of the system consists solely of exact elements, in which case Sage could do the right thing as opposed to "whatever MATLAB does". I would also argue that, despite the validity of the arguments regarding inexact rings, this is a change in behavior that would have benefited from a deprecation warning for a short while. Another user-friendlier way of doing this (making the check argument irrelevant in the inexact case) would have been to display a warning when the user asks for check=True in the inexact case, rather than simply ignoring it. Best, Alex -- 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/31bff932-3517-49c7-93ed-30e58383ba37%40googlegroups.com.
[sage-devel] bug in matrix solve over inexact coefficients?
Hi, I'm observing the following with version 9.1 (but not with 9.0 where the behavior is correct): sage: m = matrix(SR, [0]) sage: b = vector([1]) sage: m.solve_right(b) (0) This should of course raise ValueError: matrix equation has no solutions It seems to be specific to inexact coefficients (the same problem occurs for RR and CC, but not for QQ). Best, Alex -- 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/c1222f10-74e3-44f1-b141-c39c8ebdf12b%40googlegroups.com.
[sage-devel] trac authentication failures
Hi, I tried logging into trac today after a long time away, and failed. Thinking that I had just forgotten my password, I asked for a password reset, and then retried with the automatically generated password that trac emailed me. Still getting an authentication failure. Thoughts? Best, Alex -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] categories and element classes
Hello sage-devel, (I sent this from my email a couple of hours ago but it hasn't appeared on the list yet. I am trying again from within Google Groups. Apologies if it ends up being a duplicate post.) Schemes and their points are not yet properly embedded in the category framework. One of the trac tickets listing the issues is http://trac.sagemath.org/sage_trac/ticket/7946 which mentions that Volker Braun had resolved some of the issues but some related to elements still remain. Here is what seems to be the root of the problem: sage: A = AffineSpace(2, ZZ) sage: p = A(0, 0) sage: p.parent().category().element_class sage: type(p) Compare this with sage: type(QQ(0)) sage: QQ(0).parent().category().element_class In the latter case (elements of QQ), things are set up so that Sage knows that Rational is a subtype of QuotientFields.element_class. But for schemes, Sage does not know that SchemeMorphism_point_affine is a subtype of Schemes_abstract.HomCategory.element_class. So how do I fix this? I have tried to locate how this is done for QQ, but I haven't succeeded. Can anyone point me to this? -- Best, Alex Alex Ghitza -- http://aghitza.org/ Lecturer in Mathematics -- The University of Melbourne -- Australia -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: how to make tut and ref
John,
I just ran into this problem and, while searching for a solution,
found this post. I don't know if you eventually got it to work, but
it turns out that the solution (under Ubuntu) is to install the
package texlive-lang-cyrillic (probably because of Sha).
Not quite Klingon, but almost :)
Alex
On Jul 31, 12:16 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> I've been told (cf #3708) that to rebuild the tutorial and ref manual
> one should able to go into $SAGE_ROOT/devel/doc and type "make tut" or
> "make ref". But when I do this I get the following error:
>
> [EMAIL PROTECTED] ref
...
> No file OT2cmr.fd.
>
> ! LaTeX Error: This NFSS system isn't set up properly.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H for immediate help.
> ...
>
> l.28 \begin{document}
>
> ?
> ! Emergency stop.
> ...
>
> l.28 \begin{document}
>
> No pages of output.
> Transcript written on ref.log.
> *** Session transcript and error messages are in
> /home/john/sage-3.0.4/devel/doc-main/html/ref/ref.how.
> *** Exited with status 1.
> make: *** [html/ref/ref.html] Error 1
>
> ---
>
> My system's latex installation normally works fine. What am I doing wrong?
>
> John
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
