Re: [sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

[ph h]

Hi there,

> Are you asking whether a shell script can handle complex arithmetic? What
does that have to do with Sage?
Maybe it's just wishful thinking. One day, SageMath may have it's own shell
(smiley)

> If that's not what you're asking, please clarify.

Maybe just another wishful thinking, how to make [ 1 = 1+0i ] evaluate to
'true' with a tiny bit (0) of imaginary part (smiley)
Thank you for your help, it is much appreciated.

All the best,

phiho



On Thu, May 26, 2022 at 12:46 AM John H Palmieri 
wrote:

> Are you asking whether a shell script can handle complex arithmetic? What
> does that have to do with Sage?
>
> If that's not what you're asking, please clarify.
>
> On Wednesday, May 25, 2022 at 5:38:43 AM UTC-7 hohoa...@gmail.com wrote:
>
>> P.S: Sorry, there was a typo here:
>> *# at configuration time.*
>>
>> should read
>>
>> *# at validating time.*
>>
>>
>> On Tue, May 24, 2022 at 10:14 PM ph h  wrote:
>>
>>> Dear All,
>>>
>>> Is this feasible [ 1 = 1+0i  ] <=> [ 1 = 1 ] ?
>>>
>>> Regards,
>>>
>>> phiho
>>>
>>> **
>>> if [ 1 = 1+0i ]; then
>>> # Make sure that SAGE_ROOT is either an absolute physical directory name
>>> # or empty.
>>> *# An absolute physical directory name has already been embedded and
>>> exported*
>>>
>>>
>>>
>>>
>>>
>>> *# at configuration time.#if [ -n "$SAGE_ROOT" ]; then#export
>>> SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)#fi#if [ -d "$SAGE_ROOT"
>>> ]; then*
>>> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
>>> export SAGE_SRC="$SAGE_ROOT/src"
>>> export SAGE_DOC_SRC="$SAGE_SRC/doc"
>>> export PATH="$SAGE_ROOT/build/bin:$PATH"
>>> if [ -z "$SAGE_DISTFILES" ]; then
>>> SAGE_DISTFILES="$SAGE_ROOT/upstream"
>>> export SAGE_DISTFILES
>>> fi
>>> if [ -z "$CCACHE_BASEDIR" ]; then
>>> export CCACHE_BASEDIR="$SAGE_ROOT"
>>> fi
>>> *#fi*
>>> fi# [ 1 = 1+0i ]
>>>
>>> **
>>>
>>> **
>>> if [ 1 = 1 ]; then
>>> # Make sure that SAGE_ROOT is either an absolute physical directory name
>>> # or empty.
>>> if [ -n "$SAGE_ROOT" ]; then
>>> export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)
>>> fi
>>> [...]
>>> if [ -d "$SAGE_ROOT" ]; then
>>> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
>>> export SAGE_SRC="$SAGE_ROOT/src"
>>> fi
>>> [...]
>>> if [ -n "$SAGE_SRC" ]; then
>>> export SAGE_DOC_SRC="$SAGE_SRC/doc"
>>> fi
>>> [...]
>>> if [ -d "$SAGE_ROOT" ]; then
>>> export PATH="$SAGE_ROOT/build/bin:$PATH"
>>> fi
>>> [...]
>>> if [ -d "$SAGE_ROOT" ]; then
>>> if [ -z "$SAGE_DISTFILES" ]; then
>>> SAGE_DISTFILES="$SAGE_ROOT/upstream"
>>> export SAGE_DISTFILES
>>> fi
>>> fi
>>> [...]
>>> if [ -d "$SAGE_ROOT" -a -z "$CCACHE_BASEDIR" ]; then
>>> export CCACHE_BASEDIR="$SAGE_ROOT"
>>> fi
>>> fi  # [ 1 = 1 ]
>>>
>>> if [ 1 = 2 ]; then
>>> echo "The following enviroment variables can be set by the user"
>>> echo "AR  The archiver (e.g. ar, /usr/ccs/bin/ar or
>>> /usr/bin/ar)"
>>> echo "AS  The assembler (e.g. as, /usr/ccs/bin/as or
>>> /usr/bin/as)"
>>> echo "CC  The C compiler (e.g cc, /opt/SUNWspro/bin/cc or
>>> /usr/bin/gcc)"
>>> echo "CFLAGS  Flag(s) for the C compiler (e.g.  -g -Wall -O2)"
>>> echo "(You are advised to a some optimisation flag(s),
>>> such as -O2 or -xO2 to CFLAGS)"
>>> echo "CXX The C++ compiler (e.g g++, /opt/SUNWspro/bin/CC or
>>> /usr/local/bin/g++)"
>>> echo "CXXFLAGSFlag(s) for the C++ compiler (e.g. -fast
>>> -fsimple=1 -x04)"
>>> echo "LD  The linker (e.g. ld, /usr/ccs/bin/ld or
>>> /usr/bin/ld)"
>>> echo "LDFLAGS Linker flag(s) (e.g. -D token)"
>>> echo "LN  Used to make links (e.g. ln, /usr/xpg4/bin/ln or
>>> /usr/bin/ln)"
>>> echo "MAKEThe make program (e.g. make, /usr/bin/make or
>>> /usr/local/bin/gmake)"
>>> echo "MAKEFLAGS   Flag(s) to make (e.g. -j4)."
>>> echo "RANLIB  Archiver ranlib (e.g. ranlib, /usr/ccs/bin/ranlib
>>> etc)"
>>> echo "SHAREDFLAGS Flag(s) necessary for building a shared library
>>> (e.g. -fPIC or -xcode=pic32)"
>>> echo "We attempt to set this to sensible values, but check below to"
>>> echo "ensure they are OK. If you wish to override any then please
>>> use:"
>>> echo "setenv NAME_OF_ENVIROMENT_VARIABLE
>>> value_of_enviroment_variable"
>>> echo "(if you use tcsh, csh or a similar shell) or"
>>> echo "NAME_OF_ENVIROMENT_VARIABLE value_of_enviroment_variable"
>>> echo "export NAME_OF_ENVIROMENT_VARIABLE"
>>> echo "if you use sh, bash or a similar shell"
>>> fi
>>> **
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/0e5b5d21-9dda-492a-b427-ea0d7104505an%40googlegroups.com

Re: [sage-devel] Re: Run the actual Sage script

[ph h]

Hi,

> Well, https://trac.sagemath.org/ticket/33852 (needs review) removes this
code from src/doc/bootstrap.

Thank you so much. This is certainly a much better solution.
Hopefully, this trac will get positive reviews soon.

All the best.

phiho


On Thu, May 26, 2022 at 2:46 PM Matthias Koeppe 
wrote:

> Well, https://trac.sagemath.org/ticket/33852 (needs review) removes this
> code from src/doc/bootstrap.
>
>
> On Wednesday, May 25, 2022 at 10:13:38 PM UTC-7 hohoa...@gmail.com wrote:
>
>> Hi,
>>
>> """
>> We change the bootstrap scripts so that they invoke
>> build/bin/sage-package directly instead of going through the
>> SAGE_ROOT/sage script.
>> """
>>
>> It would be nice if usage_advanced() and sage_version() could be
>> factored out of src/bin/sage so that the src/doc/bootstrap can be
>> completely independent of SAGE_ROOT/sage:
>>
>> # ./sage -advanced> "$OUTPUT"
>>
>> SAGE_ROOT="$(pwd)"
>> . "src/bin/sage-version"
>> . "src/bin/sage-usage_advanced"  > "$OUTPUT"
>>
>> Is there a better way to achieve this?
>>
>> Thank you for your help.
>>
>> Regards,
>>
>> phiho
>>
>>
>> On Mon, May 16, 2022 at 1:31 PM ph h  wrote:
>>
>>> Hi,
>>>
>>> """
>>> We change the bootstrap scripts so that they invoke
>>> build/bin/sage-package directly instead of going through the
>>> SAGE_ROOT/sage script.
>>> """
>>>
>>> This is great news, a big time saver. Thank you so much.
>>> Until then,  this hitchhiker needs to restore the original
>>> '$SAGE_ROOT/sage' before she can 'make configure' ('bootstrap' requires
>>> that original 'sage') while testing 'configure.ac'
>>>
>>> Best regards,
>>>
>>> phiho
>>>
>>>
>>> On Mon, May 16, 2022 at 12:24 PM Matthias Koeppe 
>>> wrote:
>>>
 On Monday, May 16, 2022 at 1:35:37 AM UTC-7 hohoa...@gmail.com wrote:

> [...]  $SAGE_ROOT/sage [...]
>

 The positively reviewed tickets https://trac.sagemath.org/ticket/33786
 and https://trac.sagemath.org/ticket/33787 make changes to this
 script. You may find these changes and the discussion on the ticket
 interesting.

 https://trac.sagemath.org/ticket/33852 makes other changes related to
 the script. It needs review.

 --
 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+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%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/c6e0145b-5512-4f98-a477-cd4b48d0f9e2n%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/CALZQg1aLrf2W8hEKHo2FeS5UMQ95OSgfesKt-4dV%2BhBw%2BfkYnQ%40mail.gmail.com.

Re: [sage-devel] Re: Run the actual Sage script

[Matthias Koeppe]

Well, https://trac.sagemath.org/ticket/33852 (needs review) removes this 
code from src/doc/bootstrap.


On Wednesday, May 25, 2022 at 10:13:38 PM UTC-7 hohoa...@gmail.com wrote:

> Hi,
>
> """
> We change the bootstrap scripts so that they invoke build/bin/sage-package 
> directly 
> instead of going through the SAGE_ROOT/sage script.
> """
>
> It would be nice if usage_advanced() and sage_version() could be factored 
> out of src/bin/sage so that the src/doc/bootstrap can be completely 
> independent of SAGE_ROOT/sage:
>
> # ./sage -advanced> "$OUTPUT"
>
> SAGE_ROOT="$(pwd)"
> . "src/bin/sage-version" 
> . "src/bin/sage-usage_advanced"  > "$OUTPUT"
>
> Is there a better way to achieve this?
>
> Thank you for your help.
>
> Regards,
>
> phiho
>
>
> On Mon, May 16, 2022 at 1:31 PM ph h  wrote:
>
>> Hi,
>>
>> """
>> We change the bootstrap scripts so that they invoke 
>> build/bin/sage-package directly instead of going through the 
>> SAGE_ROOT/sage script.
>> """
>>
>> This is great news, a big time saver. Thank you so much.
>> Until then,  this hitchhiker needs to restore the original 
>> '$SAGE_ROOT/sage' before she can 'make configure' ('bootstrap' requires 
>> that original 'sage') while testing 'configure.ac'
>>
>> Best regards,
>>
>> phiho
>>
>>
>> On Mon, May 16, 2022 at 12:24 PM Matthias Koeppe  
>> wrote:
>>
>>> On Monday, May 16, 2022 at 1:35:37 AM UTC-7 hohoa...@gmail.com wrote:
>>>
 [...]  $SAGE_ROOT/sage [...]

>>>
>>> The positively reviewed tickets https://trac.sagemath.org/ticket/33786 
>>> and https://trac.sagemath.org/ticket/33787 make changes to this script. 
>>> You may find these changes and the discussion on the ticket interesting.
>>>
>>> https://trac.sagemath.org/ticket/33852 makes other changes related to 
>>> the script. It needs review.
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%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/c6e0145b-5512-4f98-a477-cd4b48d0f9e2n%40googlegroups.com.

[sage-devel] Re: Error building from source

[Utkarsh Sharma]

Never mind, I tried uninstalling the singular I had downloaded from 
homebrew and ran make again, and sage installed it as an spkg. Now Sage 
works fine on my computer.

On Wednesday, May 25, 2022 at 10:05:26 PM UTC+5:30 Utkarsh Sharma wrote:

> Hi! I'm new to open source and wanted to contribute to Sage, so I tried 
> building Sage from source code. However, whenever I run make, it throws 
> this error at me saying that it's unable to build singular-4.2.1p3 and I 
> have no idea what's causing it. I'm using macOS 12.3.1 on my M1 MacBook. 
> Also, when I run ./configure, it tells me that it could not find an 
> equivalent system package for singular, but when I brew install singular it 
> says I already have it. I even tried reinstalling it, but ./configure still 
> tells me to install it.
> It would be nice if I could get some help with this. Here's the error and 
> the corresponding log files:
>
>  [singular-4.2.1p3] error installing, exit status 1. End of log file:
>
>   [singular-4.2.1p3] ^
>
>   [singular-4.2.1p3]   fatal error: too many errors emitted, stopping now 
> [-ferror-limit=]
>
>   [singular-4.2.1p3]   fatal error: too many errors emitted, stopping now 
> [-ferror-limit=]
>
>   [singular-4.2.1p3]   ../../libpolys/polys/monomials/p_polys.h:1525:39: 
> error: unknown type name 'int64'
>
>   [singular-4.2.1p3]   static inline void p_SetExpVL(poly p, int64 *ev, 
> const ring r)
>
>   [singular-4.2.1p3] ^
>
>   [singular-4.2.1p3]   fatal error: too many errors emitted, stopping now 
> [-ferror-limit=]
>
>   [singular-4.2.1p3]   20 errors generated.
>
>   [singular-4.2.1p3]   make[8]: *** [mpr_inout.lo] Error 1
>
>   [singular-4.2.1p3]   make[8]: *** Waiting for unfinished jobs
>
>   [singular-4.2.1p3]   20 errors generated.
>
>   [singular-4.2.1p3]   make[8]: *** [mpr_base.lo] Error 1
>
>   [singular-4.2.1p3]   20 errors generated.
>
>   [singular-4.2.1p3]   make[8]: *** [mpr_numeric.lo] Error 1
>
>   [singular-4.2.1p3]   make[7]: *** [all-recursive] Error 1
>
>   [singular-4.2.1p3]   make[6]: *** [all-recursive] Error 1
>
>   [singular-4.2.1p3]   make[5]: *** [all] Error 2
>
>   [singular-4.2.1p3]   
> 
>
>   [singular-4.2.1p3]   Error building singular-4.2.1p3
>
>   [singular-4.2.1p3]   
> 
>
>   [singular-4.2.1p3]   
>
>   [singular-4.2.1p3]   real2m3.631s
>
>   [singular-4.2.1p3]   user3m7.473s
>
>   [singular-4.2.1p3]   sys0m33.206s
>
>   [singular-4.2.1p3]   
> 
>
>   [singular-4.2.1p3]   Error installing package singular-4.2.1p3
>
>   [singular-4.2.1p3]   
> 
>

-- 
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/9533f8e3-0717-4c46-976d-95961619be43n%40googlegroups.com.

Re: [sage-devel] Virtual Sage Days June 1–3: Preliminary program, Registration

[François Bissey]

I’d seriously watch your talk (The way to a fully modularized Sage library 
10.0) live and chat but I’ll be driving kids to school at that time :)
I’ll have to enjoy the replay later in the day.

François

> On 26/05/2022, at 18:57, Matthias Koeppe  wrote:
> 
> Preliminary program:
> https://researchseminars.org/seminar/SageDays112358
> 
> Please register:
> https://sagemath.zulipchat.com/#narrow/stream/321245-sd112.2E358/topic/Registration
> 
> It is still possible to contribute talks, tutorials, coding sprints, and 
> other activities
> 
> -- 
> 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/b94af80d-9ece-42f7-9f26-9b847f9af9a7n%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/8B732490-62F1-4131-BA9E-8BEA289956B1%40gmail.com.

[sage-devel] Re: Finite dimensional algebra generated by matrices

[Yingdong Li]

Dear all,

I have put my code in GitHub(with some explanation of it) so that you can 
clearly see it. 

Here's a link of my code in GitHub(see the code called "Finite generated 
algebra as a ring")
Dongulas/Dongulas: Config files for my GitHub profile. 


Best wishes,
Li Yingdong

在2022年5月17日星期二 UTC+8 21:37:06 写道：

> Dear Travis,
>
> Thanks for your advice! The finite dimensional algebra code in Sage need a 
> multiplication table, so the second part of our code is used to find the 
> multiplication table with the basis of the algebra. And the first part of 
> our code is used to find the basis with the generators of the algebra(along 
> with a ideal of the polynomial ring). Our aim is to find the ring structure 
> of the algebra generated by a list of commuting matrices.
>
> Best wishes,
> Li Yingdong
>
> 在2022年5月15日星期日 UTC+8 11:16:24 写道：
>
>> I would advise against having it as an external package if you plan to 
>> integrate it into Sage. It further fragments the code and makes it more 
>> likely to bitrot from what I have seen. I would instead create a ticket and 
>> upload the code to that.
>>
>> Is this a finite dimensional commutative algebra? We already have finite 
>> dimensional algebras (with no assumptions, e.g., associativity) in Sage. 
>> How does your code compare with this code? Could they be combined?
>>
>> Best,
>> Travis
>>
>>
>> On Thursday, May 12, 2022 at 9:55:55 PM UTC+9 davida...@gmail.com wrote:
>>
>>> Hello,
>>>
>>> Most of the SageMath developpment is explained in this guide:
>>>
>>>   https://doc.sagemath.org/html/en/developer/index.html
>>>
>>> Also, I don't know exactly what is the scale of your code, but I would 
>>> advise you to first upload your code to Github (if it isn't already done) 
>>> as an external package. Github is very convenient for sharing code, so it 
>>> would be easier to share it with the community. Next, I think to contribute 
>>> to SageMath it is better to start with small contribution. For example, 
>>> review some tickets or fix some bugs. Then, it becomes easier to contribute 
>>> to bigger projects. 
>>>
>>> Anyway, welcome to the community and good job on your research project!
>>>
>>> David Ayotte
>>>
>>> Le jeudi 12 mai 2022 à 05:45:53 UTC-4, Yingdong Li a écrit :
>>>
 Dear all,

 I have written some codes in Sage to compute the finite-dimensional 
 algebra by a list of commuting matrices and I want to contribute it to 
 Sage. Here is the idea of my codes.

 1. We can construct the algebra as a quotient of a polynomial ring(by 
 using the homomorphism which sends each x_i to t_i, where t_1,...,t_n is 
 the n matrices generate the algebra), we can also get the basis by doing 
 this.

 2. With the basis of the algebra, we can also compute the 
 multiplication table then use the finite-dimensional algebra command in 
 Sage to get a description to this algebra.

 Once we have done with these things above, we can get the ring 
 structure of the algebra. This is very useful in dealing with some 
 problems 
 about modular forms since we can further study the prime ideals or maximal 
 ideals of Hecke algebra by using its ring structure.

 I'm an undergraduate student and this is part of my research project. I 
 was wondering how I can contribute the codes to Sage. Could anyone give me 
 some help me with this(since I'm not so familiar about the Sage trac and 
 I'm not sure where I can share my codes)? Thanks in advance!

 Moreover, if you have some questions or comments on this, we can 
 discuss about it here.

 Best wishes,
 Li Yingdong






-- 
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/749863a8-ae9e-4b4b-a704-9eeb274cb4b3n%40googlegroups.com.

[sage-devel] Virtual Sage Days June 1–3: Preliminary program, Registration

[Matthias Koeppe]

Preliminary program:
https://researchseminars.org/seminar/SageDays112358

Please register:
https://sagemath.zulipchat.com/#narrow/stream/321245-sd112.2E358/topic/Registration

It is still possible to contribute talks, tutorials, coding sprints, and 
other activities

-- 
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/b94af80d-9ece-42f7-9f26-9b847f9af9a7n%40googlegroups.com.