2018-01-05 16:21:45 +0200 | received badge | ● Good Answer (source) |
2018-01-04 22:43:34 +0200 | received badge | ● Nice Answer (source) |
2017-12-26 22:15:12 +0200 | received badge | ● Teacher (source) |
2017-12-26 22:15:12 +0200 | received badge | ● Necromancer (source) |
2017-12-21 08:44:20 +0200 | answered a question | 'launched jmol viewer for Graphics3d Object' fails I've got the identical situation occurring. What I've noticed is that if I open the sage shell and run jmol I get: However, if I go in to /opt/sagemath-8.1/local/share/jmol/ and run jmol it works: I believe I understand part of what the underlying issue is. The java I have is a windows java that expects windows pathnames. I can make it work by editing the jmol shell script to run this: This will launch jmol from within sage, when you run things like So it seems like sage is expecting to run a java that works with these unix-like paths, but the java that is installed only accepts windows-like paths. In any case, launching jmol doesn't actually make the image display correctly. This is because the arguments that are passed contain another unix-like path, ie: /dot_sage/temp/DESKTOP-HUU9IR5/21144/dir_JxIjMK/scene.spt Once I modified that to have a windows-like path, I then opened that file and found that the file itself contained more unix-like paths. Once I modified that remaining path to a windows-like path, jmol did in fact render the image that I wanted. So, this is obviously an awful solution, but what I've done is replaced the jmol bash script with a python script that takes all the parameters, modifies them to use windows paths, and runs java. It's dirty but it works. |