On Sunday, May 31, 2020 at 2:52:21 PM UTC-7, Michael Jung wrote:
>
> If I understand this correctly, I'd say this is already the approach of
> how differential forms are implemented in the SageManifolds package. A
> differential form is seen as an element of the module over the scalar
> fields w
I should just mention here, that a CPU parallelization on the level of
components already takes place. However, watching the CPU usage one can see
that only single cores are demanded. I am not certain about the reason.
Am Sonntag, 31. Mai 2020 23:52:21 UTC+2 schrieb Michael Jung:
>
> If I unders
If I understand this correctly, I'd say this is already the approach of how
differential forms are implemented in the SageManifolds package. A
differential form is seen as an element of the module over the scalar
fields which is, roughly speaking, generated by the germs on parallelizable
pieces
On Sunday, May 31, 2020 at 12:41:52 PM UTC-7, Michael Jung wrote:
>
> Thanks for your reply. Actually, I consider a commutative sub-algebra
> here. What do you mean by "taking fibers of [my] sheaf"?
>
Specialize to the exterior product algebra of the cotangent space at a
point. So, at that point
I decided to make it a little stand alone library.
https://pypi.org/project/sherali-adams/
cheers
On Thursday, May 28, 2020 at 10:44:30 PM UTC-7, matthew Drescher wrote:
>
> I have written some code which runs k rounds of Sherali-Adams relaxation
> hierarchy on a system Ax >= b. It was enough
Thanks for your reply. Actually, I consider a commutative sub-algebra here.
What do you mean by "taking fibers of [my] sheaf"?
I thought that it would be a nice idea to split all operations necessary
for the determinant between different CPU cores. What about that?
Am Samstag, 30. Mai 2020 22:3
I had started with a make distclean but then by installing a few things I
thought I should start over again. Did a "make distclean" and a "make"
again with the same results.
Here is my config.log file:
http://garsia.math.yorku.ca/~zabrocki/config.log
I'm not (intentionally) doing something unu
please post the main config.log
are you trying to do something unusual, like using mpir instead of gmp?
is it a build from scratch?
(make distclean
helps most problems we see)
On Sun, 31 May 2020, 18:37 Mike Zabrocki, wrote:
> Hi,
>
> I'm trying to compile the latest stable version and it ke
Hi,
I'm trying to compile the latest stable version and it keeps getting stuck
at the pplpy package.
Can someone tell me how to get around this?
I'm installing on Mac OSX 10.15.5
Log file is at:
http://garsia.math.yorku.ca/~zabrocki/pplpy-0.8.4.log
Thanks,
-Mike
**
Thanks for the reply.
Then something is wrong with my setup. Even without changing anything a run
of sage -b takes more than 4 min for me. I'd now run multiple builds `sage
-b` directly without any changes in between and all apps closed etc. The
output is attached below. Maybe the reason is tha
On Sun, May 31, 2020 at 1:59 PM Eric Gourgoulhon wrote:
>
> Hi Tobias,
>
> Le dimanche 31 mai 2020 14:49:46 UTC+2, Tobias Diez a écrit :
>>
>>
>> For now I came up with the following workaround, which works but feels like
>> a huge hack: Create a file `/src/sage/test.py` with the following conten
Hi Tobias,
Le dimanche 31 mai 2020 14:49:46 UTC+2, Tobias Diez a écrit :
>
>
> For now I came up with the following workaround, which works but feels
> like a huge hack: Create a file `/src/sage/test.py` with the following
> content. You can then run this file using the local python (e.g.
> ./l
Hi everybody,
(disclaimer: everything I say comes from a few days of playing around with
sage's code - so I might make some wrong statements that are obvious to
more experienced sage devs)
currently `./sage -b` rebuilds the python interpreter part of sage (i.e.
special syntax support etc) as w
13 matches
Mail list logo