David Jordan's profile - activity

Hi, I should have specified that. I'm using "magma" as the interpreter on the top of the screen. One might ask why I'm not just using the magma terminal interface directly, but it's because I'm using the sharing features in sage notebook to allow several people to work on the same file remotely. Except for this really odd bug, it's working well...

Hi all,

I'm experiencing a strange phenomenon when using the sage interface to magma, through the notebook interface (in firefox and chrome browsers, on separate computers). If I enter a command that is long enough to require word-wrapping in the standard input window, it causes the magma interpreter to throw an error. As best I can tell, it is passing the newline to magma erroneously. That is, I don't intend to have a newline there, but it's still causing an error. I was baffled what was causing the error, but then I broke the code (a long sum) into two shorter lines, each a command for half of the code for the sum.

Can anyone offer advice how to work with long lines of code in the sage magma interface, without having to awkwardly break them up? Thanks, David

Anyhow, thanks again! I am a graduate student in math and am employing Sage and its cousins in a range of different problems. I love that Sage can interface with Gap and Magma, the latter of which has some more robust algorithms for non-commutative algebra.

As to the issue of fixing this permanently: The notebook did say "processing..." but didn't give any other indication that the tab completion process would take a particularly long time, or that there was any danger in aborting, until I after I hit "interrupt", at which point it released a message warning me that it would take a few minutes to set up (but it was too late, as I had already aborted). Also, once I had messed it up, there seemed to be nowhere in the documentation telling me how to fix it, and no methods in the "magma" object (e.g. magma.cleanup() ) to address things within the notebook. It just didn't respond to the tab key any longer. So while it was a user error on my part which caused it, I guess maybe some more robust handling and some documentation could help.

Thanks so much! Indeed, there was a file called " magma_intrinsic_cache.sobj" which had been created with only garbage the first time, because I had interrupted the evaluation. Deleting that made it work.

I don't know for sure, but probably it is somewhere in ~/.sage There is a subdirectory there having to do with the notebook, and presumably the tab completion data is somewhere inside. Probably there's no great harm in deleting some of these files (unless you have important data in the notebook -- if so, save it elsewhere first!).

As an aside, this probably qualifies as a bug in the notebook interface to magma -- let us know if you have further difficulties, or other comments about how this should or shouldn't work.

Hello,

I have been attempting to use the magma interface functionality in the notebook() web interface. It seems to work (our school has a magma license, and it is able to connect). However, the first time I attempted tab completion in the notebook GUI, it seemed to freeze. Not knowing any better, I stopped evaluation; afterwards I received an error message indicating that I needed to wait awhile for a cache with all the tab completion data to be compiled. However, this was too late, and somehow it seems to have written a blank tab completion cache.

I don't know where this cache is stored, or how to trigger the interface to remake the cache. Can anyone offer assistance?