Re: [sage-support] Re: plot3d using real-valued real-parameter functions but involving complex numbers as intermediates

[Gary McConnell]

Dear @ppurka

thanks so much - i am now finally back at home with my trusty Macs and
hopefully will be able to do the above, eventually  :)

For me this is entering an exciting new phase! Thanks again.

Best regards

Gary


On Sat, Apr 20, 2013 at 6:00 PM, P Purkayastha  wrote:

> On 04/18/2013 03:13 AM, Gary McConnell wrote:
>
>> I am very keen to help - my problem is utter incompetence at following
>> the high-level instructions in the manual for developers. Also I am on
>> the VM and I cannot access the sage directories directly. Is there a way
>> you could send me a manual file that I could modify and send back to
>> you? Sorry :( I promise I will learn this one day ...
>>
>> the page I was referring to is
>> http://www.sagemath.org/doc/**reference/numerical/sage/**
>> numerical/optimize.html#sage.**numerical.optimize.minimize
>>
>> Also there are presumably many functions to which this syntax difference
>> applies ... how can I find them?
>>
>> Thanks!
>>
>
> I failed to notice this reply earlier.
>
> I think it is better if you can submit a patch to trac. The patch is
> generated by mercurial and it can automatically populate the author
> attribution and other information. These information is used by a patchbot
> that automatically tests the patches for validity and performs other tests.
>
> To generate the patch, you can either install the sage library code.
>
> If you don't want to install the sage from source, you can download the
> sage spkg and work with that.  This is OK since you intend to do only
> documentation changes. In this case, follow the steps below:
>
> 1. download the sage spkg from http://www.sagemath.org/**
> packages/standard/sage-5.8.**spkg
> This contains the source code.
>
> 2. Create a file in $HOME/.hgrc containing your name as mentioned here:
> http://www.sagemath.org/doc/**developer/producing_patches.**html
>
> 3. Open a ticket in trac so that you can get the ticket number. Let's say
> the number is 12345.
>
> 4. Use the inbuilt mercurial inside Sage to create the patch.
>  i) First change directory to the unpacked sage/sage directory
> ii) Next, run the command (where /path/to/sage is where the sage script is
> present and 12345 is the ticket number)
> /path/to/sage -hg qnew 12345_documentation.patch
> iii) Hack hack hack and make your changes :)
> You will need to follow the developer documentation for syntax and
> formatting.
> iv) Now that you are satisfied with your changes, run
> /path/to/sage -hg qref -m "a one line description of your changes"
> v) Make hg generate the patch:
> /path/to/sage -hg export qtip > ~/$(/path/to/sage -hg qtop)
>
> 5. Go back to the ticket and upload the patch that is present at
> ~/12345_documentation.patch
>
> Hopefully, this procedure will become much simpler after the move to git,
> since trivial changes can be made directly in github (if the project
> remains hosted in github).
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/**
> topic/sage-support/**3mekDq5Stvk/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> sage-support+unsubscribe@**googlegroups.com
> .
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at 
> http://groups.google.com/**group/sage-support?hl=en
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-support] Re: Segmentation fault in Matrix(QQ).rank()

[Jeroen Demeyer]

On 04/17/2013 09:38 PM, William Stein wrote:

On Wed, Apr 17, 2013 at 11:55 AM, Sure  wrote:

Thanks! Built from source and now it works.
So there is a bug in sage binary distributions? I took
sage-5.8-linux-64bit-ubuntu_10.04.4_lts-x86_64-Linux.tar.lzma,
and ubuntu is based on debian. It really may call ATLAS, but what its fault
might cause such behaviour?


When you first installed and started the Sage binary did it give some
terrifying warning message about missing CPU instructions, along with
a message about how to disable the warning?   If you got no such
message, there is a bug -- the cpu checks should be more stringent --
what is the output of "cat /proc/cpuinfo" on your computer?  If you
did get such a message, well, you were warned :-)
In any case, I fail to see how missing CPU features could lead to a 
Segmentation Fault. It's more likely a library incompatibility or something.


--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-support] Conjunctive Normal Form

[Santanu Sarkar]

Dear all,
  Thank you very much for your help.

With regards,
Santanu


On 21 April 2013 07:02, Martin Albrecht wrote:

> sage: B. = BooleanPolynomialRing()
> sage: f=a+b*c
> sage: from sage.sat.converters.polybori import CNFEncoder
> sage: from sage.sat.solvers.dimacs import DIMACS
> sage: solver = DIMACS()
> sage: ce = CNFEncoder(solver, B)
> sage: ce([f])
> [None, a, b, c]
> sage: solver.clauses()
> [((-2, -3, 1), False, None), ((3, -1), False, None), ((2, -1), False,
> None)]
>
>
> On Saturday 20 Apr 2013, Santanu Sarkar wrote:
> > Dear all,
> >   I want to convert the polynomial f into Conjunctive Normal Form (CNF)
> > in Sage. How can I do this?
> >
> >
> > B. = BooleanPolynomialRing()
> > f=a+b*c
>
> Cheers,
> Martin
>
> --
> name: Martin Albrecht
> _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
> _www: http://martinralbrecht.wordpress.com/
> _jab: martinralbre...@jabber.ccc.de
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-support@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-support?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-support] Re: Segmentation fault in Matrix(QQ).rank()

[Sure]

Nope, I didn't see warnings, and didn't try to dismiss them.
What the steps it might have suggested?
I put cpuinfo content into the attach. 

On Wednesday, April 17, 2013 11:38:42 PM UTC+4, William wrote:
>
>
> When you first installed and started the Sage binary did it give some 
> terrifying warning message about missing CPU instructions, along with 
> a message about how to disable the warning?   If you got no such 
> message, there is a bug -- the cpu checks should be more stringent -- 
> what is the output of "cat /proc/cpuinfo" on your computer?  If you 
> did get such a message, well, you were warned :-) 
>
> William 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Core(TM)2 CPU  6600  @ 2.40GHz
stepping: 6
microcode   : 0xcb
cpu MHz : 2394.000
cache size  : 4096 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm 
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor 
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow
bogomips: 4800.76
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Core(TM)2 CPU  6600  @ 2.40GHz
stepping: 6
microcode   : 0xcb
cpu MHz : 2394.000
cache size  : 4096 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm 
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor 
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow
bogomips: 4799.93
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management: