Re: [sage-devel] "Tri bool"
Not currently (though we have "Unknown"). The main problem is the interaction with Python booleans and the operators "or", "and", "not" (which are *not* logical operators). The Sage "Unknown" is badly broken for these reasons sage: not Unknown # waiting for Unknown True sage: Unknown or False # waiting for Unknown False So be careful if you start using it! If we would use the correct logical operators ~ (for negation), ^ (for xor) and & (for and) then we might be able to come up with something. But Sage sort of ignore them. This problem has been discussed a lot on this mailing list and there even exists a (refused) PEP request in this direction. Best, Vincent On 15 November 2016 at 08:22, Thierry Dumontwrote: > When developing a software which aims to prove something, it seems > necessary to be able to return something in > {True, False, Indeterminate}. > > Of course, there are many possibilities to do this, but is there a > "canonical" one in Sage ? > > In C++, for example, there exists the Boost Tribool library > (http://www.boost.org/doc/libs/1_62_0/doc/html/tribool.html#tribool.introduction) > . > > t.d. > > -- > 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 https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] "Tri bool"
When developing a software which aims to prove something, it seems necessary to be able to return something in {True, False, Indeterminate}. Of course, there are many possibilities to do this, but is there a "canonical" one in Sage ? In C++, for example, there exists the Boost Tribool library (http://www.boost.org/doc/libs/1_62_0/doc/html/tribool.html#tribool.introduction) . t.d. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. <>
[sage-devel] Re: Building 7.4.beta5 after building 7.5 betas
On Tuesday, November 15, 2016 at 2:34:00 AM UTC+1, Paul Masson wrote: > > Or is the current recommendation to always merge develop after every new > beta? > I think it's to use it sparingly. That the history from git log is gobbled is IMO a git bug. The branch I've been working on has been under review for some time, so I > don't want to set things back by moving code around unnecessarily. > There is the possibility of pushing a new branch (which gets complicated if several authorships must be preserved). I don't think it would strain trac resources too much. > Besides, why shouldn't I always be able to go back and rebuild a previous > branch without wiping everything clean? > Because Sage is one of the most complicated software systems, and reality rears its head quite a bit (with her beauty in the eye of the beholder). > Trying to understand what goes wrong in the process. > We all do. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Errors from importing abs
On Tuesday, November 15, 2016 at 4:36:01 AM UTC+1, Nils Bruin wrote: > > ... The "abs" in the global namespace is just the generic python one: > abs(a) dispatches to a.__abs__() > > sage: class A(object): > : def __abs__(self): > : return "abs" > : > sage: a=A() > sage: abs(a) > 'abs' > sage: sage.functions.all.abs_symbolic(a) > TypeError: cannot coerce arguments: no canonical coercion from '__main__.A'> to Symbolic Ring > However, using the #21657 branch where abs is imported from functions.other I get sage: abs(a) --- TypeError Traceback (most recent call last) in () > 1 abs(a) /home/ralf/sage/src/sage/symbolic/function.pyx in sage.symbolic.function. BuiltinFunction.__call__ (build/cythonized/sage/symbolic/function.cpp:11333 )() 993 res = self._evalf_try_(*args) 994 if res is None: --> 995 res = super(BuiltinFunction, self).__call__( 996 *args, coerce=coerce, hold=hold) 997 /home/ralf/sage/src/sage/symbolic/function.pyx in sage.symbolic.function. Function.__call__ (build/cythonized/sage/symbolic/function.cpp:6218)() 471 if callable(method): 472 return method() --> 473 raise TypeError("cannot coerce arguments: %s" % (err )) 474 475 else: # coerce == False TypeError: cannot coerce arguments: no canonical coercion from to Symbolic Ring so it seems the Python abs can be overridden. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-combinat-devel] Re: kronecker coefficient
Mike's version with symmetrica is 20 times faster for 3 partitions of 5, 100 times faster for 3 partitions of 10. For partitions of 15, my version used up all my memory and I had to kill it. Mike's version was still very quick (11.8ms). Also, I think the syntax should be agreeable to both Dima and me. I would like to put it as a standalone function (maybe in partition.py), which need not be loaded into the namespace automatically, and then also add methods to the Partition element class and to the PartitionTuple element class. Does that sound reasonable? Amri. On Tuesday, November 15, 2016 at 8:02:17 AM UTC+5:30, Mike Zabrocki wrote: > > I am not so sure that if you are explaining the definition that you want > to state it in terms of "the multiplicity of the trivial..." > It kind of depends on where you put this method. One place to consider is > in the Partition class or in PartitionTuple class. > > For example: > PartitionTuple([[3,1],[2,2],[3,1]]).kronecker_coefficient() > or > Partition([3,1]).kronecker_coefficient([2,2],[3,1]) > > You might check if this procedure is faster (however you should note that > it is called for example kronecker_coefficient([3,1],[2,2],[3,1])): > > sage: from sage.libs.symmetrica.symmetrica import charvalue_symmetrica as > chv > > sage: def kronecker_coefficient(*partns): > > : if partns==(): > > : return 1 > : else: > > : return sum(mul(chv(la,mu) for la in partns) for mu in > Partitions(sum(partns[0]))) > > : > > This version automatically has an optional last parameter. > > -Mike > > On Monday, 14 November 2016 05:53:10 UTC-5, Dima Pasechnik wrote: >> >> >> >> On Monday, November 14, 2016 at 10:44:35 AM UTC, Amri wrote: >>> >>> But you just add the "arbitrary irreducible" to your list: >>> >>> mult of la in mu\otimes nu = mult of triv in mu\otimes\nu\otimes la >>> >>> there is complete symmetry between the parameters. >>> >> >> Well, this still does not imply that one doesn't want la as an extra >> parameter for >> the function, even if only for convenience. >> (imagine a user that has a bit less representation theory of S_n loaded >> in his/her head >> than you :-)) >> >> >>> On Monday, November 14, 2016 at 3:54:24 PM UTC+5:30, Dima Pasechnik >>> wrote: On Monday, November 14, 2016 at 5:36:19 AM UTC, Amri wrote: > > It would be nice to have a function for kronecker coefficients in > sage. I would be happy to implement it once I have some inputs on what > would be the best way/place. One definition of the kronecker coefficient > is > the following: > > Defn. Given a sequence [la1, , lan] of ineteger partitions on n, > the kronecker coef of this sequence is the multiplicity of the trivial > representation the tensor product of the Specht modules corresponding to > the partitions la1, la2,...,lan. > I'd say that there should be a function for the multiplicity of an arbitrary irreducible, not only the trivial one. > > Note: some people like to think of it slightly differently: given > three partitions la, mu and nu of n, the kronecker coefficient is the > multiplicity of V_la in V_mu \times V_nu. This coincided with the > multiplicity of the trivial rep in V_la\otimes V_\mu\otimes V_\nu (which > is > the definition above). > > A quick implementation is: > sage: def kronecker_coefficient(partns): > : S = SymmetricFunctions(QQ).schur() > : pr = reduce(lambda x, y: x.itensor(y), [S[la] for la in > partns]) > : return pr.coefficient(Partition([sum(partns[0])])) > > This code is already in the documentation for a patch of mine at: > > https://trac.sagemath.org/ticket/17437 > > Looking forward to some feedback. > > Thanks, > Amri. > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Errors from importing abs
On Monday, November 14, 2016 at 12:49:17 PM UTC-8, Paul Masson wrote: > > Doesn't the explicit alias to abs_symbolic put abs into the global name > space as a symbolic function? Why does an import of abs create more > problems than the alias? Is this a general Python problem or something > specific to SageMath? > No, it doesn't. The "abs" in the global namespace is just the generic python one: abs(a) dispatches to a.__abs__() sage: class A(object): : def __abs__(self): : return "abs" : sage: a=A() sage: abs(a) 'abs' sage: sage.functions.all.abs_symbolic(a) TypeError: cannot coerce arguments: no canonical coercion from to Symbolic Ring -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Relevant op-ed in Notices
An op-ed by a prof. at Berkeley entitled "Mathematical Software: Is It Mathematics or Is It Software?" should be of interest to this group. http://www.ams.org/journals/notices/201611/ I'm told that discussion on the Notices website is highly encouraged! - kcrisman -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Building 7.4.beta5 after building 7.5 betas
On Monday, November 14, 2016 at 3:51:49 PM UTC-8, Dima Pasechnik wrote: > > Did you have a pressing need to build an old branch? > I'd normally first rebase over the latest beta, and then build. > What do you mean by "rebase" precisely? Just merging the current develop branch or something else? I'm under the impression that merging develop, while convenient, is confusing for the history of a branch, so I've been avoiding that and running ccache instead to cut down on build time. Or is the current recommendation to always merge develop after every new beta? The branch I've been working on has been under review for some time, so I don't want to set things back by moving code around unnecessarily. Besides, why shouldn't I always be able to go back and rebuild a previous branch without wiping everything clean? Trying to understand what goes wrong in the process. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Building 7.4.beta5 after building 7.5 betas
Did you have a pressing need to build an old branch? I'd normally first rebase over the latest beta, and then build. On Monday, November 14, 2016 at 10:56:35 PM UTC, Paul Masson wrote: > > I'm running into an problem that after building 7.5.beta1 or 7.5.beta2, > building a branch based on 7.4.beta5 fails for two packages: cysignals-1.1.1 > and mistune-0.7.3. The only way I've found around it so far is to run make > dist-clean && make but that takes more time than should be necessary. > > Is this an error others have encountered? Is there a faster way to get > past it? Logs attached for these two packages. > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Building 7.4.beta5 after building 7.5 betas
I'm running into an problem that after building 7.5.beta1 or 7.5.beta2, building a branch based on 7.4.beta5 fails for two packages: cysignals-1.1.1 and mistune-0.7.3. The only way I've found around it so far is to run make dist-clean && make but that takes more time than should be necessary. Is this an error others have encountered? Is there a faster way to get past it? Logs attached for these two packages. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. Found local metadata for cysignals-1.1.1 Using cached file /Users/Masson/Downloads/GitHub/sage/upstream/cysignals-1.1.1.tar.bz2 cysignals-1.1.1 Setting up build directory for cysignals-1.1.1 Finished extraction Host system: Darwin MacBook-Retina.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Sep 1 15:01:16 PDT 2016; root:xnu-3248.60.11~2/RELEASE_X86_64 x86_64 C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/Users/Masson/Downloads/GitHub/sage/local/libexec/gcc/x86_64-apple-darwin15.6.0/4.9.3/lto-wrapper Target: x86_64-apple-darwin15.6.0 Configured with: ../src/configure --prefix=/Users/Masson/Downloads/GitHub/sage/local --with-local-prefix=/Users/Masson/Downloads/GitHub/sage/local --with-gmp=/Users/Masson/Downloads/GitHub/sage/local --with-mpfr=/Users/Masson/Downloads/GitHub/sage/local --with-mpc=/Users/Masson/Downloads/GitHub/sage/local --with-system-zlib --disable-multilib --disable-nls --enable-languages=c,c++,fortran --disable-libitm --with-build-config=bootstrap-debug --without-isl --without-cloog Thread model: posix gcc version 4.9.3 (GCC) checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for library containing pari_init... -lpari checking how to run the C preprocessor... cpp checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking sys/prctl.h usability... no checking sys/prctl.h presence... no checking for sys/prctl.h... no checking for backtrace... yes checking whether PARI_SIGINT_block is declared... yes checking for emms instruction... yes configure: creating ./config.status config.status: creating build/src/config.h config.status: executing build/src/config.pxd commands python setup.py build generating build/src/cysignals/__init__.pxd Compiling src/cysignals/signals.pyx because it changed. Compiling src/cysignals/alarm.pyx because it changed. Compiling src/cysignals/tests.pyx because it changed. [1/3] Cythonizing src/cysignals/alarm.pyx [2/3] Cythonizing src/cysignals/signals.pyx [3/3] Cythonizing src/cysignals/tests.pyx running build running build_py creating build/lib.macosx-10.9-x86_64-2.7 creating build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/__init__.py -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/memory.pxi -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/signals.pxi -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/memory.pxd -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/signals.pxd -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/debug.h -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/macros.h -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/pxi.h -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying src/cysignals/struct_signals.h -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying build/src/cysignals/__init__.pxd -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying build/src/cysignals/signals.h -> build/lib.macosx-10.9-x86_64-2.7/cysignals copying build/src/cysignals/signals_api.h ->
Re: [sage-devel] RFC: correct way to deal with particular methods
Dear All, sorry for the late reply and thank you very much for the input. As far as having methods not always defined the consensus here is leaning towards making sublcasses but I am quite reluctant to do that because of future things I want to implement. Down the road there are going to be many more methods that only make sense in certain cases and not in others. Unfortunately the cases are many so that I would have to implement lots of different classes. The sublclass approach is the OOP-clean way but it can be nightmarish to maintain if there are too many corner cases. This will be one such situation when everything is implemented. Johan's suggestion is very intriguing but, unless I am completely mistaken, it does not work in python. If I understand correctly if O is an instance of Foo and O does not have the attribute x then python looks for Foo().x At the moment it seems "better" (sigh) to define the methods anyway and raise an error in case they are meaningless. Any objection? As for the question about the wrapper. Currently I am using @wrap and not @sage_wrap but the result is analogous. I am indeed changing the documentation at decoration-time (that is what I meant by "on the fly") and reviewers are objecting precisely to this. Could someone explain to me how sublcasses can help here? Could you please have a look at the code? The branch is public/ticket/21254. The wrapper begins at line 358 and the documentation edit at line 384. The methods being wrapped are at lines 1047 and 2150. Thanks S. * Johan S. H. Rosenkilde[2016-11-07 09:45:57]: VulK writes: The first question is about which is the correct way to implement methods that are not always defined. I agree with Nils that subclassing is the most OOP-clean way of achieving this. That being said, one might argue that it is a pretty heavy-handed solution which potentially leads to class-explosion and mega-multiple-inheritance. Another possibility is to do the converse of what you are doing: add the method on the class but *delete* at construction time if it is not appropriate. This can be done using delattr. VulK writes: The second problem is a little more involved, I will try to give you a souped up version here. ... Did you take a look at performing the preparsing using a decorator which properly uses @sage_wraps? It is possible to do the documentation modification at decoration-time, and then it should properly show up in Sphinx as well. Best, Johan -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: why chrome kiosk mode in sage appliance??
The recommended (for power users) way to run the virtual machine is using their host browser, just go to http://localhost:8000. This requires a non-broken windows networking stack, though (and various dodgy windows programs can interfere). In the kiosk mode you can still go back,e.g. open a notebook and then File -> Close and Halt. If you really do want a full browser inside the VM (with a virtualbox menu on top) then you can edit ~/.xinitrc inside the vm. On Monday, November 14, 2016 at 3:21:32 PM UTC+1, Stan wrote: > > Dear all, > > A student of mine has been using SMC because the sage appliance in > virtualbox did not appear very useful with the jupyter notebook. Now that > he encountered a critical bug in SMC (reported offline), he is back with > the sage appliance in VB but it is truly a nightmare. The installation > instructions are still specific for sagews, not jupyter, but we at least > managed to change the working directory to something he can access. What we > haven't managed, is to get out of the kiosk mode in chrome. There is no > obvious possibility of opening several tabs, no address bar to get back to > the directory page and no back button. This means that every time he wants > to go back, e.g. after downloading the worksheet, he has to restart the > virtual machine! I don't understand why chrome was chosen instead of > firefox, and I have no idea why it is set up in kiosk mode. Is there any > sensible way to productively work with the sage appliance using the now > standard jupyter notebook?? I'm sorry if my frustration shows in these > lines, I probably should have asked earlier, but I am wondering a bit if > those that created the sage appliance actually use it themselves. I don't, > which is why it never occurred to me how difficult to use it might be. > Thanks for your help! > > Cheers > Stan > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Errors from importing abs
Since abs is declared in functions/other.py as an explicit alias of abs_symbolic, I figured it wouldn't hurt to import if from that file but on https://trac.sagemath.org/ticket/21657 it leads to a variety of failed doctests. Some of these are coercion errors and others are more severe. I'd like to understand why this happens. Doesn't the explicit alias to abs_symbolic put abs into the global name space as a symbolic function? Why does an import of abs create more problems than the alias? Is this a general Python problem or something specific to SageMath? -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: why chrome kiosk mode in sage appliance??
On Mon, Nov 14, 2016 at 12:46 PM, William Steinwrote: > On Mon, Nov 14, 2016 at 12:40 PM, Dima Pasechnik wrote: >> >> >> On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote: >>> >>> Dear all, >>> >>> A student of mine has been using SMC because the sage appliance in >>> virtualbox did not appear very useful with the jupyter notebook. Now that he >>> encountered a critical bug in SMC (reported offline), he is back with the >>> sage appliance in VB but it is truly a nightmare. The installation >>> instructions are still specific for sagews, not jupyter, but we at least >>> managed to change the working directory to something he can access. What we >>> haven't managed, is to get out of the kiosk mode in chrome. There is no >>> obvious possibility of opening several tabs, no address bar to get back to >>> the directory page and no back button. This means that every time he wants >>> to go back, e.g. after downloading the worksheet, he has to restart the >>> virtual machine! I don't understand why chrome was chosen instead of >>> firefox, and I have no idea why it is set up in kiosk mode. Is there any >>> sensible way to productively work with the sage appliance using the now >>> standard jupyter notebook?? I'm sorry if my frustration shows in these >>> lines, I probably should have asked earlier, but I am wondering a bit if >>> those that created the sage appliance actually use it themselves. >> >> >> I think you are right, there aren't any known to me Sage devs who develop on >> Windows... >> >> A better way to run Sage in a VM is via (host) network, so that you use the >> native web browser to access notebooks, while >> VM would be running a server. This is more or less clear how to set up for >> sagews; I don't know enough about jupyter >> to say how it can be done so that the web interface is not on localhost: >> (but it looks as it is doable). I'm very surprised the VM doesn't *already* work that way, starting up, starting a server, and just displaying on screen that one should visit a certain URL.It did when I used to make the VM. William > > sage -ipython notebook --no-browser --ip=0.0.0.0 > > -- William > > > -- > William (http://wstein.org) -- William (http://wstein.org) -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: why chrome kiosk mode in sage appliance??
On Mon, Nov 14, 2016 at 12:40 PM, Dima Pasechnikwrote: > > > On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote: >> >> Dear all, >> >> A student of mine has been using SMC because the sage appliance in >> virtualbox did not appear very useful with the jupyter notebook. Now that he >> encountered a critical bug in SMC (reported offline), he is back with the >> sage appliance in VB but it is truly a nightmare. The installation >> instructions are still specific for sagews, not jupyter, but we at least >> managed to change the working directory to something he can access. What we >> haven't managed, is to get out of the kiosk mode in chrome. There is no >> obvious possibility of opening several tabs, no address bar to get back to >> the directory page and no back button. This means that every time he wants >> to go back, e.g. after downloading the worksheet, he has to restart the >> virtual machine! I don't understand why chrome was chosen instead of >> firefox, and I have no idea why it is set up in kiosk mode. Is there any >> sensible way to productively work with the sage appliance using the now >> standard jupyter notebook?? I'm sorry if my frustration shows in these >> lines, I probably should have asked earlier, but I am wondering a bit if >> those that created the sage appliance actually use it themselves. > > > I think you are right, there aren't any known to me Sage devs who develop on > Windows... > > A better way to run Sage in a VM is via (host) network, so that you use the > native web browser to access notebooks, while > VM would be running a server. This is more or less clear how to set up for > sagews; I don't know enough about jupyter > to say how it can be done so that the web interface is not on localhost: > (but it looks as it is doable). sage -ipython notebook --no-browser --ip=0.0.0.0 -- William -- William (http://wstein.org) -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] why chrome kiosk mode in sage appliance??
On Monday, November 14, 2016 at 5:44:01 PM UTC, William wrote: > > On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray> wrote: > > On Mon, Nov 14, 2016 at 4:49 PM, William Stein > wrote: > >> On Mon, Nov 14, 2016 at 6:21 AM, Stan > wrote: > >>> Dear all, > >>> > >>> A student of mine has been using SMC because the sage appliance in > >>> virtualbox did not appear very useful with the jupyter notebook. Now > that he > >>> encountered a critical bug in SMC (reported offline), he is back with > the > >> > >> I'm not aware of this bug. I don't know of any critical bugs in SMC. > >> There are exactly 22 known SMC *bugs*, which you can see listed here, > >> all of which we plan to fix ASAP: > >> > >> > https://github.com/sagemathinc/smc/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20label%3AI-bug%20sort%3Acreated-asc%20-label%3Ablocked > > >> > >> On can also use SMC via docker on Windows, Linux and OS X, as explained > here: > >> > >> > https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md > >> > >> I wish I could recommend the official sagemath docker images, but it > >> looks like they haven't been updated in 6 months to 1 year ago? (What > >> the heck?) > >> > >>https://hub.docker.com/u/sagemath/ > > > > > > I'm not sure where you're looking-- > > > Click on the link above. I clicked on sagemath/sage since it is ON > TOP (hence what you find with a typical google search), and it has > vastly more downloads than all other docker Sage images put together. > It's clearly the one people are getting for some reason. > > I then clicked on the sagemath-jupyter one, since -- based on the name > -- I imagine that's the other reasonable choice if a person wants a > web interface... and it is 6 months old. > > Clicking on all of them now, only sagemath/sagemath has been updated > recently. All others are out of date. > > > the image called sagemath/sage is > > definitely deprecated and should be removed. > > OK. Who has the power to do that? Also, I wonder what is driving so > much traffic there? > > all these docker images are owned by "sagemath", whoever (s)he is. Please raise your hand :-) I suppose that whoever has the creds of this account, can manage the images. Dima > > sagemath/sagemath is the > > latest and has sage 7.4. > > > > > Erik > > > > -- > > 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 post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > William (http://wstein.org) > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: why chrome kiosk mode in sage appliance??
On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote: > > Dear all, > > A student of mine has been using SMC because the sage appliance in > virtualbox did not appear very useful with the jupyter notebook. Now that > he encountered a critical bug in SMC (reported offline), he is back with > the sage appliance in VB but it is truly a nightmare. The installation > instructions are still specific for sagews, not jupyter, but we at least > managed to change the working directory to something he can access. What we > haven't managed, is to get out of the kiosk mode in chrome. There is no > obvious possibility of opening several tabs, no address bar to get back to > the directory page and no back button. This means that every time he wants > to go back, e.g. after downloading the worksheet, he has to restart the > virtual machine! I don't understand why chrome was chosen instead of > firefox, and I have no idea why it is set up in kiosk mode. Is there any > sensible way to productively work with the sage appliance using the now > standard jupyter notebook?? I'm sorry if my frustration shows in these > lines, I probably should have asked earlier, but I am wondering a bit if > those that created the sage appliance actually use it themselves. > I think you are right, there aren't any known to me Sage devs who develop on Windows... A better way to run Sage in a VM is via (host) network, so that you use the native web browser to access notebooks, while VM would be running a server. This is more or less clear how to set up for sagews; I don't know enough about jupyter to say how it can be done so that the web interface is not on localhost: (but it looks as it is doable). Dima > I don't, which is why it never occurred to me how difficult to use it > might be. Thanks for your help! > > Cheers > Stan > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] why chrome kiosk mode in sage appliance??
On Mon, Nov 14, 2016 at 8:40 AM, Erik Braywrote: > On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote: >> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote: >>> Dear all, >>> >>> A student of mine has been using SMC because the sage appliance in >>> virtualbox did not appear very useful with the jupyter notebook. Now that he >>> encountered a critical bug in SMC (reported offline), he is back with the >> >> I'm not aware of this bug. I don't know of any critical bugs in SMC. >> There are exactly 22 known SMC *bugs*, which you can see listed here, >> all of which we plan to fix ASAP: >> >> >> https://github.com/sagemathinc/smc/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20label%3AI-bug%20sort%3Acreated-asc%20-label%3Ablocked >> >> On can also use SMC via docker on Windows, Linux and OS X, as explained here: >> >> https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md >> >> I wish I could recommend the official sagemath docker images, but it >> looks like they haven't been updated in 6 months to 1 year ago? (What >> the heck?) >> >>https://hub.docker.com/u/sagemath/ > > > I'm not sure where you're looking-- Click on the link above. I clicked on sagemath/sage since it is ON TOP (hence what you find with a typical google search), and it has vastly more downloads than all other docker Sage images put together. It's clearly the one people are getting for some reason. I then clicked on the sagemath-jupyter one, since -- based on the name -- I imagine that's the other reasonable choice if a person wants a web interface... and it is 6 months old. Clicking on all of them now, only sagemath/sagemath has been updated recently. All others are out of date. > the image called sagemath/sage is > definitely deprecated and should be removed. OK. Who has the power to do that? Also, I wonder what is driving so much traffic there? > sagemath/sagemath is the > latest and has sage 7.4. > > Erik > > -- > 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 https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] why chrome kiosk mode in sage appliance??
On Mon, Nov 14, 2016 at 4:49 PM, William Steinwrote: > On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote: >> Dear all, >> >> A student of mine has been using SMC because the sage appliance in >> virtualbox did not appear very useful with the jupyter notebook. Now that he >> encountered a critical bug in SMC (reported offline), he is back with the > > I'm not aware of this bug. I don't know of any critical bugs in SMC. > There are exactly 22 known SMC *bugs*, which you can see listed here, > all of which we plan to fix ASAP: > > > https://github.com/sagemathinc/smc/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20label%3AI-bug%20sort%3Acreated-asc%20-label%3Ablocked > > On can also use SMC via docker on Windows, Linux and OS X, as explained here: > > https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md > > I wish I could recommend the official sagemath docker images, but it > looks like they haven't been updated in 6 months to 1 year ago? (What > the heck?) > >https://hub.docker.com/u/sagemath/ I'm not sure where you're looking--the image called sagemath/sage is definitely deprecated and should be removed. sagemath/sagemath is the latest and has sage 7.4. Erik -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] why chrome kiosk mode in sage appliance??
On Mon, Nov 14, 2016 at 6:21 AM, Stanwrote: > Dear all, > > A student of mine has been using SMC because the sage appliance in > virtualbox did not appear very useful with the jupyter notebook. Now that he > encountered a critical bug in SMC (reported offline), he is back with the I'm not aware of this bug. I don't know of any critical bugs in SMC. There are exactly 22 known SMC *bugs*, which you can see listed here, all of which we plan to fix ASAP: https://github.com/sagemathinc/smc/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20label%3AI-bug%20sort%3Acreated-asc%20-label%3Ablocked On can also use SMC via docker on Windows, Linux and OS X, as explained here: https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md I wish I could recommend the official sagemath docker images, but it looks like they haven't been updated in 6 months to 1 year ago? (What the heck?) https://hub.docker.com/u/sagemath/ William > sage appliance in VB but it is truly a nightmare. The installation > instructions are still specific for sagews, not jupyter, but we at least > managed to change the working directory to something he can access. What we > haven't managed, is to get out of the kiosk mode in chrome. There is no > obvious possibility of opening several tabs, no address bar to get back to > the directory page and no back button. This means that every time he wants > to go back, e.g. after downloading the worksheet, he has to restart the > virtual machine! I don't understand why chrome was chosen instead of > firefox, and I have no idea why it is set up in kiosk mode. Is there any > sensible way to productively work with the sage appliance using the now > standard jupyter notebook?? I'm sorry if my frustration shows in these > lines, I probably should have asked earlier, but I am wondering a bit if > those that created the sage appliance actually use it themselves. I don't, > which is why it never occurred to me how difficult to use it might be. > Thanks for your help! > > Cheers > Stan > > -- > 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 https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] why chrome kiosk mode in sage appliance??
Dear all, A student of mine has been using SMC because the sage appliance in virtualbox did not appear very useful with the jupyter notebook. Now that he encountered a critical bug in SMC (reported offline), he is back with the sage appliance in VB but it is truly a nightmare. The installation instructions are still specific for sagews, not jupyter, but we at least managed to change the working directory to something he can access. What we haven't managed, is to get out of the kiosk mode in chrome. There is no obvious possibility of opening several tabs, no address bar to get back to the directory page and no back button. This means that every time he wants to go back, e.g. after downloading the worksheet, he has to restart the virtual machine! I don't understand why chrome was chosen instead of firefox, and I have no idea why it is set up in kiosk mode. Is there any sensible way to productively work with the sage appliance using the now standard jupyter notebook?? I'm sorry if my frustration shows in these lines, I probably should have asked earlier, but I am wondering a bit if those that created the sage appliance actually use it themselves. I don't, which is why it never occurred to me how difficult to use it might be. Thanks for your help! Cheers Stan -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-combinat-devel] Re: kronecker coefficient
On Monday, November 14, 2016 at 10:44:35 AM UTC, Amri wrote: > > But you just add the "arbitrary irreducible" to your list: > > mult of la in mu\otimes nu = mult of triv in mu\otimes\nu\otimes la > > there is complete symmetry between the parameters. > Well, this still does not imply that one doesn't want la as an extra parameter for the function, even if only for convenience. (imagine a user that has a bit less representation theory of S_n loaded in his/her head than you :-)) > On Monday, November 14, 2016 at 3:54:24 PM UTC+5:30, Dima Pasechnik wrote: >> >> >> >> On Monday, November 14, 2016 at 5:36:19 AM UTC, Amri wrote: >>> >>> It would be nice to have a function for kronecker coefficients in sage. >>> I would be happy to implement it once I have some inputs on what would be >>> the best way/place. One definition of the kronecker coefficient is the >>> following: >>> >>> Defn. Given a sequence [la1, , lan] of ineteger partitions on n, the >>> kronecker coef of this sequence is the multiplicity of the trivial >>> representation the tensor product of the Specht modules corresponding to >>> the partitions la1, la2,...,lan. >>> >> >> I'd say that there should be a function for the multiplicity of an >> arbitrary irreducible, not only the trivial one. >> >> >>> >>> Note: some people like to think of it slightly differently: given three >>> partitions la, mu and nu of n, the kronecker coefficient is the >>> multiplicity of V_la in V_mu \times V_nu. This coincided with the >>> multiplicity of the trivial rep in V_la\otimes V_\mu\otimes V_\nu (which is >>> the definition above). >>> >>> A quick implementation is: >>> sage: def kronecker_coefficient(partns): >>> : S = SymmetricFunctions(QQ).schur() >>> : pr = reduce(lambda x, y: x.itensor(y), [S[la] for la in >>> partns]) >>> : return pr.coefficient(Partition([sum(partns[0])])) >>> >>> This code is already in the documentation for a patch of mine at: >>> >>> https://trac.sagemath.org/ticket/17437 >>> >>> Looking forward to some feedback. >>> >>> Thanks, >>> Amri. >>> >> -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
[sage-combinat-devel] Re: kronecker coefficient
But you just add the "arbitrary irreducible" to your list: mult of la in mu\otimes nu = mult of triv in mu\otimes\nu\otimes la there is complete symmetry between the parameters. On Monday, November 14, 2016 at 3:54:24 PM UTC+5:30, Dima Pasechnik wrote: > > > > On Monday, November 14, 2016 at 5:36:19 AM UTC, Amri wrote: >> >> It would be nice to have a function for kronecker coefficients in sage. I >> would be happy to implement it once I have some inputs on what would be the >> best way/place. One definition of the kronecker coefficient is the >> following: >> >> Defn. Given a sequence [la1, , lan] of ineteger partitions on n, the >> kronecker coef of this sequence is the multiplicity of the trivial >> representation the tensor product of the Specht modules corresponding to >> the partitions la1, la2,...,lan. >> > > I'd say that there should be a function for the multiplicity of an > arbitrary irreducible, not only the trivial one. > > >> >> Note: some people like to think of it slightly differently: given three >> partitions la, mu and nu of n, the kronecker coefficient is the >> multiplicity of V_la in V_mu \times V_nu. This coincided with the >> multiplicity of the trivial rep in V_la\otimes V_\mu\otimes V_\nu (which is >> the definition above). >> >> A quick implementation is: >> sage: def kronecker_coefficient(partns): >> : S = SymmetricFunctions(QQ).schur() >> : pr = reduce(lambda x, y: x.itensor(y), [S[la] for la in >> partns]) >> : return pr.coefficient(Partition([sum(partns[0])])) >> >> This code is already in the documentation for a patch of mine at: >> >> https://trac.sagemath.org/ticket/17437 >> >> Looking forward to some feedback. >> >> Thanks, >> Amri. >> > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.