Activity for Jmol
-
Bob Hanson committed [r22701] on Code
-
-
Jmol.___JmolVersion="16.3.49" // (legacy) also 16.3.50 (swingJS)
-
Jmol released /Jmol/Version 16.3/Jmol 16.3.49/Jmol.properties
-
-
-
-
-
Jmol 16.3.49
-
-
-
-
-
Jmol.___JmolVersion="16.3.50" // (swingJS) also 16.3.49 (legacy)
-
16.3.49 prerelease
-
Jmol.___JmolVersion="16.3.47" // (legacy) also 16.3.48 (swingJS)
-
-
-
-
-
-
-
-
-
-
Jmol.___JmolVersion="16.3.47" // (legacy) also 16.3.48 (swingJS)
-
-
-
-
-
-
-
-
-
Jmol.___JmolVersion="16.3.45" // (legacy) also 16.3.46 (swingJS)
-
inconsistency between Jmol and JmolData
-
Actually, both programs are showing this message. But it is not a meaningful message. It is just a warning that "variable" is not a property that can be set in an isosurface. It arises from my forgetting to take out some unused code in IsoExt.java. I've tracked down where it is coming from and removed that code. Thanks for spotting this.
-
John Terning created ticket #636
inconsistency between Jmol and JmolData
-
Jmol.___JmolVersion="16.3.45" // (legacy) also 16.3.46 (swingJS)
-
Angel Herraez committed [r22691] on Code
update splash image to (c) 2026
-
-
-
-
-
Jmol.___JmolVersion="16.3.43" // (legacy) also 16.3.44 (swingJS)
-
-
-
-
Jmol.___JmolVersion="16.3.41" // (legacy) also 16.3.42 (swingJS)
-
-
-
-
-
-
Jmol.___JmolVersion="16.3.41" // (legacy) also 16.3.42 (swingJS)
-
I would really appreciate it if you would contribute that.
-
Egon Willighagen created ticket #635
Releases on Maven Central?
-
-
corezip.js cleanup
-
-
-
-
-
Jmol.___JmolVersion="16.3.37" // (legacy) also 16.3.38 (swingJS)
-
Indeed. The presence of G orbitals causes the MO coefficient pointer to go awry. The problem was a simple error in logic in MOCalculation.java. This is fixed for Jmol 16.3.37/38. for a preview release Jmol.jar, see https://sourceforge.net/p/jmol/code/HEAD/tree/trunk/Jmol/test/jmol-jar/
-
Indeed. The presence of G orbitals causes the MO coefficient pointer to go awry. The problem was a simple error in logic in MOCalculation.java. This is fixed for Jmol 16.32.37/38. for a preview release Jmol.jar, see https://sourceforge.net/p/jmol/code/HEAD/tree/trunk/Jmol/test/jmol-jar/
-
Indeed. The presence of G orbitals causes the MO coefficient pointer to go awry. This is fixed for Jmol 16.32.37/38. for a preview release Jmol.jar, see https://sourceforge.net/p/jmol/code/HEAD/tree/trunk/Jmol/test/jmol-jar/
-
bug fix: MO calculation fails when G orbitals are present
-
Jmol.___JmolVersion="16.3.37" // (legacy) also 16.3.38 (swingJS)
-
Marco Foscato created ticket #634
v14 vs. v16: Inconsistent orbials visualization from Molden file
-
-
override
-
Jmol.___JmolVersion="16.3.37" // (legacy) also 16.3.38 (swingJS)
-
-
-
-
-
-
-
Jmol.___JmolVersion="16.3.35" // (legacy) also 16.3.36 (swingJS)
-
Jmol 16.3.35
-
closing this issue if no further response. On Tue, Aug 26, 2025 at 10:11 PM Bob Hanson hansonr@users.sourceforge.net wrote: ... of NBO files. On Tue, Aug 26, 2025, 9:05 PM Robert Hanson hansonr@stolaf.edu wrote: PS. Please send the full set of no files. At least include 31. On Tue, Aug 26, 2025, 6:31 PM Bob Hanson hansonr@users.sourceforge.net wrote: The -2147483648 error is indicating that the file was found, but its format was different from what was expected. nbo files #37 are reading correctly...
-
test jsmol.zip for AH
-
PS. Please send the full set of no files. At least include 31. On Tue, Aug 26, 2025, 6:31 PM Bob Hanson hansonr@users.sourceforge.net wrote: The -2147483648 error is indicating that the file was found, but its format was different from what was expected. nbo files #37 are reading correctly for our test set. Please attach the file in a response to this message so we can see what might be the issue. Probably a simple fix. Q: What is the source version of ORCA you are using? This might be something...
-
... of NBO files. On Tue, Aug 26, 2025, 9:05 PM Robert Hanson hansonr@stolaf.edu wrote: PS. Please send the full set of no files. At least include 31. On Tue, Aug 26, 2025, 6:31 PM Bob Hanson hansonr@users.sourceforge.net wrote: The -2147483648 error is indicating that the file was found, but its format was different from what was expected. nbo files #37 are reading correctly for our test set. Please attach the file in a response to this message so we can see what might be the issue. Probably a simple...
-
The -2147483648 error is indicating that the file was found, but its format was different from what was expected. nbo files #37 are reading correctly for our test set. Please attach the file in a response to this message so we can see what might be the issue. Probably a simple fix. Q: What is the source version of ORCA you are using? This might be something you will need to address with that group. But first, let's find out exactly what the problem is.
-
Hello, Maureen For this kind of problems, you should use the jmol-users email distribution list. Anyway, it is hard to help unless you share the problematic file.
-
Maureen Kitheka created ticket #633
Unable to view FILE.37
-
-
-
-
-
Jmol.___JmolVersion="16.3.33" // (legacy) also 16.3.34 (swingJS)
-
-
-
-
-
Jmol.___JmolVersion="16.3.31" // (legacy) also 16.3.32 (swingJS)
-
-
1 >
