You can subscribe to this list here.
2001 
_{Jan}

_{Feb}

_{Mar}

_{Apr}

_{May}
(20) 
_{Jun}
(13) 
_{Jul}
(45) 
_{Aug}

_{Sep}
(3) 
_{Oct}
(5) 
_{Nov}
(1) 
_{Dec}
(1) 

2002 
_{Jan}
(20) 
_{Feb}
(8) 
_{Mar}
(10) 
_{Apr}
(38) 
_{May}
(8) 
_{Jun}
(1) 
_{Jul}

_{Aug}
(8) 
_{Sep}
(45) 
_{Oct}
(116) 
_{Nov}
(195) 
_{Dec}
(67) 
2003 
_{Jan}
(94) 
_{Feb}
(84) 
_{Mar}
(23) 
_{Apr}
(21) 
_{May}
(246) 
_{Jun}
(100) 
_{Jul}
(23) 
_{Aug}
(54) 
_{Sep}
(73) 
_{Oct}
(166) 
_{Nov}
(52) 
_{Dec}
(46) 
2004 
_{Jan}
(138) 
_{Feb}
(175) 
_{Mar}
(194) 
_{Apr}
(76) 
_{May}
(423) 
_{Jun}
(412) 
_{Jul}
(127) 
_{Aug}
(133) 
_{Sep}
(172) 
_{Oct}
(273) 
_{Nov}
(192) 
_{Dec}
(272) 
2005 
_{Jan}
(178) 
_{Feb}
(178) 
_{Mar}
(97) 
_{Apr}
(76) 
_{May}
(138) 
_{Jun}
(57) 
_{Jul}
(130) 
_{Aug}
(88) 
_{Sep}
(168) 
_{Oct}
(61) 
_{Nov}
(52) 
_{Dec}
(120) 
2006 
_{Jan}
(37) 
_{Feb}
(259) 
_{Mar}
(426) 
_{Apr}
(175) 
_{May}
(299) 
_{Jun}
(135) 
_{Jul}
(79) 
_{Aug}
(145) 
_{Sep}
(390) 
_{Oct}
(142) 
_{Nov}
(98) 
_{Dec}
(50) 
2007 
_{Jan}
(52) 
_{Feb}
(129) 
_{Mar}
(77) 
_{Apr}
(84) 
_{May}
(122) 
_{Jun}
(91) 
_{Jul}
(39) 
_{Aug}
(62) 
_{Sep}
(63) 
_{Oct}
(95) 
_{Nov}
(67) 
_{Dec}
(69) 
2008 
_{Jan}
(72) 
_{Feb}
(41) 
_{Mar}
(107) 
_{Apr}
(22) 
_{May}
(28) 
_{Jun}
(33) 
_{Jul}
(68) 
_{Aug}
(144) 
_{Sep}
(39) 
_{Oct}
(123) 
_{Nov}
(78) 
_{Dec}
(24) 
2009 
_{Jan}
(58) 
_{Feb}
(45) 
_{Mar}
(78) 
_{Apr}
(95) 
_{May}
(50) 
_{Jun}
(82) 
_{Jul}
(52) 
_{Aug}
(46) 
_{Sep}
(102) 
_{Oct}
(42) 
_{Nov}
(94) 
_{Dec}
(59) 
2010 
_{Jan}
(48) 
_{Feb}
(102) 
_{Mar}
(190) 
_{Apr}
(69) 
_{May}
(61) 
_{Jun}
(106) 
_{Jul}
(126) 
_{Aug}
(46) 
_{Sep}
(87) 
_{Oct}
(66) 
_{Nov}
(136) 
_{Dec}
(92) 
2011 
_{Jan}
(83) 
_{Feb}
(25) 
_{Mar}
(46) 
_{Apr}
(18) 
_{May}
(24) 
_{Jun}
(30) 
_{Jul}
(17) 
_{Aug}
(21) 
_{Sep}
(45) 
_{Oct}
(107) 
_{Nov}
(61) 
_{Dec}
(35) 
2012 
_{Jan}
(33) 
_{Feb}
(34) 
_{Mar}
(46) 
_{Apr}
(38) 
_{May}
(84) 
_{Jun}
(58) 
_{Jul}
(40) 
_{Aug}
(82) 
_{Sep}
(21) 
_{Oct}
(74) 
_{Nov}
(20) 
_{Dec}
(10) 
2013 
_{Jan}
(55) 
_{Feb}
(57) 
_{Mar}
(45) 
_{Apr}
(77) 
_{May}
(18) 
_{Jun}
(9) 
_{Jul}
(6) 
_{Aug}
(10) 
_{Sep}
(33) 
_{Oct}
(29) 
_{Nov}
(48) 
_{Dec}
(25) 
2014 
_{Jan}
(17) 
_{Feb}
(15) 
_{Mar}
(35) 
_{Apr}
(22) 
_{May}
(17) 
_{Jun}
(25) 
_{Jul}
(32) 
_{Aug}
(16) 
_{Sep}
(39) 
_{Oct}

_{Nov}

_{Dec}

S  M  T  W  T  F  S 







1
(6) 
2
(3) 
3
(1) 
4
(11) 
5
(2) 
6

7
(2) 
8

9
(3) 
10
(1) 
11
(2) 
12
(2) 
13

14

15

16

17

18
(1) 
19
(5) 
20

21
(11) 
22

23
(5) 
24

25

26
(1) 
27
(4) 
28

29

30

31
(1) 





From: Robert Hanson <hansonr@st...>  20100521 20:11:36

thanks  fixed. On Fri, May 21, 2010 at 2:16 PM, Nicolas Vervelle <nvervelle@...>wrote: > Hi, > > When running the unit tests, I have several exceptions for the crystal > reader : > > > java.lang.StringIndexOutOfBoundsException: String index out of range: 28 > at java.lang.String.substring(String.java:1935) > at > org.jmol.adapter.readers.xtal.CrystalReader.readGradient(CrystalReader.java:312) > at > org.jmol.adapter.readers.xtal.CrystalReader.checkLine(CrystalReader.java:237) > at > org.jmol.adapter.smarter.AtomSetCollectionReader.readAtomSetCollection(AtomSetCollectionReader.java:218) > at > org.jmol.adapter.smarter.AtomSetCollectionReader.readData(AtomSetCollectionReader.java:191) > at > org.jmol.adapter.smarter.Resolver.getAtomCollectionAndCloseReader(Resolver.java:263) > at > org.jmol.adapter.smarter.SmarterJmolAdapter.staticGetAtomSetCollectionFromReader(SmarterJmolAdapter.java:78) > at > org.jmol.adapter.smarter.SmarterJmolAdapter.getAtomSetCollectionFromReader(SmarterJmolAdapter.java:70) > > > junit.framework.AssertionFailedError: Error returned for > ..\Jmoldatafiles\crystal\alpha_quartz.out: Error reading file at line 893: > > String index out of range: 28 > for file alpha_quartz.out > type Crystal > > > > >  > > > _______________________________________________ > Jmoldevelopers mailing list > Jmoldevelopers@... > https://lists.sourceforge.net/lists/listinfo/jmoldevelopers > >  Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 5077863107 If nature does not answer first what we want, it is better to take what answer we get.  Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 
From: Nicolas Vervelle <nvervelle@gm...>  20100521 19:17:21

Hi, When running the unit tests, I have several exceptions for the crystal reader : java.lang.StringIndexOutOfBoundsException: String index out of range: 28 at java.lang.String.substring(String.java:1935) at org.jmol.adapter.readers.xtal.CrystalReader.readGradient(CrystalReader.java:312) at org.jmol.adapter.readers.xtal.CrystalReader.checkLine(CrystalReader.java:237) at org.jmol.adapter.smarter.AtomSetCollectionReader.readAtomSetCollection(AtomSetCollectionReader.java:218) at org.jmol.adapter.smarter.AtomSetCollectionReader.readData(AtomSetCollectionReader.java:191) at org.jmol.adapter.smarter.Resolver.getAtomCollectionAndCloseReader(Resolver.java:263) at org.jmol.adapter.smarter.SmarterJmolAdapter.staticGetAtomSetCollectionFromReader(SmarterJmolAdapter.java:78) at org.jmol.adapter.smarter.SmarterJmolAdapter.getAtomSetCollectionFromReader(SmarterJmolAdapter.java:70) junit.framework.AssertionFailedError: Error returned for ..\Jmoldatafiles\crystal\alpha_quartz.out: Error reading file at line 893: String index out of range: 28 for file alpha_quartz.out type Crystal 
From: SourceForge.net <noreply@so...>  20100521 15:45:48

Bugs item #3005028, was opened at 20100520 20:29 Message generated for change (Comment added) made by hansonr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User interface Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Rene Kanters (rkanters) Assigned to: Miguel (migueljmol) Summary: loss of feature in rev 12 Initial Comment: This could have happened a long time ago since I haven't been keeping my version up to date. But in the 11.x versions whenever you read a g03 output file with different input and standard orientations in a geometry optimization calculation, the AtomSetChooser would be able to show the same kind of orientations in the same 'folder'. The frequency calculation results would be in their own folder again. This makes it a lot easier to animate optimizations and stay within one set of orientations (so you don't get the flipping of the molecules). Between 11.6.x or so and 12 the reader has been modified so much that I can't really figure out any more how to set this up (even though I initially implemented it a long time ago). Sigh....  >Comment By: Bob Hanson (hansonr) Date: 20100521 10:45 Message: OK, that's fixed  just had two lines switched order in ModelLoader. Thanks, Bob  Comment By: Bob Hanson (hansonr) Date: 20100521 10:35 Message: duh. I see it now  Jmol!  Comment By: Bob Hanson (hansonr) Date: 20100521 10:35 Message: duh. I see it now  Jmol!  Comment By: Bob Hanson (hansonr) Date: 20100521 10:32 Message: Rene, it's the .PATH property: atomSetCollection.setAtomSetProperty(SmarterJmolAdapter.PATH_KEY, "Calculation "+calculationNumber+ (scanPoint>=0?(SmarterJmolAdapter.PATH_SEPARATOR+"Scan Point "+scanPoint):"")+ SmarterJmolAdapter.PATH_SEPARATOR+path); as far as I know, that should still work. For example, I see for one of the test files: auxiliaryinfo.properties.PATH_SEPARATOR ";" auxiliaryinfo.properties.PATH_KEY ".PATH" modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[4].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[5].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[6].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[7].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[8].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[9].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[10].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[11].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[12].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[13].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" and for another: modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;Input" modelinfo.models[4].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[5].modelProperties..PATH "Calculation 1;Input" modelinfo.models[6].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[7].modelProperties..PATH "Calculation 1;Input" modelinfo.models[8].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[9].modelProperties..PATH "Calculation 1;Input" modelinfo.models[10].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[11].modelProperties..PATH "Calculation 2;Input" modelinfo.models[12].modelProperties..PATH "Calculation 2;Standard" modelinfo.models[13].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[15].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" These are exactly the same properties that are shown using Jmol 10.9, so maybe it's just how you are extracting them. What are you using to view this hierarchy? Bob maybe there is  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 
From: SourceForge.net <noreply@so...>  20100521 15:35:26

Bugs item #3005028, was opened at 20100520 20:29 Message generated for change (Comment added) made by hansonr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rene Kanters (rkanters) Assigned to: Miguel (migueljmol) Summary: loss of feature in rev 12 Initial Comment: This could have happened a long time ago since I haven't been keeping my version up to date. But in the 11.x versions whenever you read a g03 output file with different input and standard orientations in a geometry optimization calculation, the AtomSetChooser would be able to show the same kind of orientations in the same 'folder'. The frequency calculation results would be in their own folder again. This makes it a lot easier to animate optimizations and stay within one set of orientations (so you don't get the flipping of the molecules). Between 11.6.x or so and 12 the reader has been modified so much that I can't really figure out any more how to set this up (even though I initially implemented it a long time ago). Sigh....  >Comment By: Bob Hanson (hansonr) Date: 20100521 10:35 Message: duh. I see it now  Jmol!  Comment By: Bob Hanson (hansonr) Date: 20100521 10:35 Message: duh. I see it now  Jmol!  Comment By: Bob Hanson (hansonr) Date: 20100521 10:32 Message: Rene, it's the .PATH property: atomSetCollection.setAtomSetProperty(SmarterJmolAdapter.PATH_KEY, "Calculation "+calculationNumber+ (scanPoint>=0?(SmarterJmolAdapter.PATH_SEPARATOR+"Scan Point "+scanPoint):"")+ SmarterJmolAdapter.PATH_SEPARATOR+path); as far as I know, that should still work. For example, I see for one of the test files: auxiliaryinfo.properties.PATH_SEPARATOR ";" auxiliaryinfo.properties.PATH_KEY ".PATH" modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[4].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[5].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[6].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[7].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[8].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[9].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[10].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[11].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[12].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[13].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" and for another: modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;Input" modelinfo.models[4].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[5].modelProperties..PATH "Calculation 1;Input" modelinfo.models[6].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[7].modelProperties..PATH "Calculation 1;Input" modelinfo.models[8].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[9].modelProperties..PATH "Calculation 1;Input" modelinfo.models[10].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[11].modelProperties..PATH "Calculation 2;Input" modelinfo.models[12].modelProperties..PATH "Calculation 2;Standard" modelinfo.models[13].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[15].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" These are exactly the same properties that are shown using Jmol 10.9, so maybe it's just how you are extracting them. What are you using to view this hierarchy? Bob maybe there is  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 
From: SourceForge.net <noreply@so...>  20100521 15:35:25

Bugs item #3005028, was opened at 20100520 20:29 Message generated for change (Comment added) made by hansonr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rene Kanters (rkanters) Assigned to: Miguel (migueljmol) Summary: loss of feature in rev 12 Initial Comment: This could have happened a long time ago since I haven't been keeping my version up to date. But in the 11.x versions whenever you read a g03 output file with different input and standard orientations in a geometry optimization calculation, the AtomSetChooser would be able to show the same kind of orientations in the same 'folder'. The frequency calculation results would be in their own folder again. This makes it a lot easier to animate optimizations and stay within one set of orientations (so you don't get the flipping of the molecules). Between 11.6.x or so and 12 the reader has been modified so much that I can't really figure out any more how to set this up (even though I initially implemented it a long time ago). Sigh....  >Comment By: Bob Hanson (hansonr) Date: 20100521 10:35 Message: duh. I see it now  Jmol!  Comment By: Bob Hanson (hansonr) Date: 20100521 10:32 Message: Rene, it's the .PATH property: atomSetCollection.setAtomSetProperty(SmarterJmolAdapter.PATH_KEY, "Calculation "+calculationNumber+ (scanPoint>=0?(SmarterJmolAdapter.PATH_SEPARATOR+"Scan Point "+scanPoint):"")+ SmarterJmolAdapter.PATH_SEPARATOR+path); as far as I know, that should still work. For example, I see for one of the test files: auxiliaryinfo.properties.PATH_SEPARATOR ";" auxiliaryinfo.properties.PATH_KEY ".PATH" modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[4].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[5].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[6].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[7].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[8].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[9].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[10].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[11].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[12].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[13].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" and for another: modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;Input" modelinfo.models[4].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[5].modelProperties..PATH "Calculation 1;Input" modelinfo.models[6].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[7].modelProperties..PATH "Calculation 1;Input" modelinfo.models[8].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[9].modelProperties..PATH "Calculation 1;Input" modelinfo.models[10].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[11].modelProperties..PATH "Calculation 2;Input" modelinfo.models[12].modelProperties..PATH "Calculation 2;Standard" modelinfo.models[13].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[15].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" These are exactly the same properties that are shown using Jmol 10.9, so maybe it's just how you are extracting them. What are you using to view this hierarchy? Bob maybe there is  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 
From: SourceForge.net <noreply@so...>  20100521 15:32:13

Bugs item #3005028, was opened at 20100520 20:29 Message generated for change (Comment added) made by hansonr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rene Kanters (rkanters) Assigned to: Miguel (migueljmol) Summary: loss of feature in rev 12 Initial Comment: This could have happened a long time ago since I haven't been keeping my version up to date. But in the 11.x versions whenever you read a g03 output file with different input and standard orientations in a geometry optimization calculation, the AtomSetChooser would be able to show the same kind of orientations in the same 'folder'. The frequency calculation results would be in their own folder again. This makes it a lot easier to animate optimizations and stay within one set of orientations (so you don't get the flipping of the molecules). Between 11.6.x or so and 12 the reader has been modified so much that I can't really figure out any more how to set this up (even though I initially implemented it a long time ago). Sigh....  >Comment By: Bob Hanson (hansonr) Date: 20100521 10:32 Message: Rene, it's the .PATH property: atomSetCollection.setAtomSetProperty(SmarterJmolAdapter.PATH_KEY, "Calculation "+calculationNumber+ (scanPoint>=0?(SmarterJmolAdapter.PATH_SEPARATOR+"Scan Point "+scanPoint):"")+ SmarterJmolAdapter.PATH_SEPARATOR+path); as far as I know, that should still work. For example, I see for one of the test files: auxiliaryinfo.properties.PATH_SEPARATOR ";" auxiliaryinfo.properties.PATH_KEY ".PATH" modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[4].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[5].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[6].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[7].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[8].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[9].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[10].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[11].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[12].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[13].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 1;FrequenciesFrequencies" and for another: modelinfo.models[1].modelProperties..PATH "Calculation 1;Input" modelinfo.models[2].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[3].modelProperties..PATH "Calculation 1;Input" modelinfo.models[4].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[5].modelProperties..PATH "Calculation 1;Input" modelinfo.models[6].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[7].modelProperties..PATH "Calculation 1;Input" modelinfo.models[8].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[9].modelProperties..PATH "Calculation 1;Input" modelinfo.models[10].modelProperties..PATH "Calculation 1;Standard" modelinfo.models[11].modelProperties..PATH "Calculation 2;Input" modelinfo.models[12].modelProperties..PATH "Calculation 2;Standard" modelinfo.models[13].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[14].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" modelinfo.models[15].modelProperties..PATH "Calculation 2;FrequenciesFrequencies" These are exactly the same properties that are shown using Jmol 10.9, so maybe it's just how you are extracting them. What are you using to view this hierarchy? Bob maybe there is  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 
From: Robert Hanson <hansonr@st...>  20100521 15:05:22

should read all my messages.... Right, that's what I understand. His position is that there is no way of using the code he has, so he would have to start from scratch, and that is not very appealing or possible within his time allowances. On Fri, May 21, 2010 at 10:03 AM, Robert Hanson <hansonr@...> wrote: > Not according to Peter, but maybe he's going to surprise us. > > 2010/5/21 Angel Herráez <angel.herraez@...> > > I've just found (from reading his recent paper in J.Cheminformatics) >> that Peter Ertl is working on an opensource javascriptbased >> equivalent of JME. Might be a good complement for Jmol. >> >> >> >> >>  >> >> _______________________________________________ >> Jmoldevelopers mailing list >> Jmoldevelopers@... >> https://lists.sourceforge.net/lists/listinfo/jmoldevelopers >> > > > >  > Robert M. Hanson > Professor of Chemistry > St. Olaf College > 1520 St. Olaf Ave. > Northfield, MN 55057 > http://www.stolaf.edu/people/hansonr > phone: 5077863107 > > > If nature does not answer first what we want, > it is better to take what answer we get. > >  Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 >  Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 5077863107 If nature does not answer first what we want, it is better to take what answer we get.  Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 
From: Robert Hanson <hansonr@st...>  20100521 15:04:04

Not according to Peter, but maybe he's going to surprise us. 2010/5/21 Angel Herráez <angel.herraez@...> > I've just found (from reading his recent paper in J.Cheminformatics) > that Peter Ertl is working on an opensource javascriptbased > equivalent of JME. Might be a good complement for Jmol. > > > > >  > > _______________________________________________ > Jmoldevelopers mailing list > Jmoldevelopers@... > https://lists.sourceforge.net/lists/listinfo/jmoldevelopers >  Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 5077863107 If nature does not answer first what we want, it is better to take what answer we get.  Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 
From: Angel Herráez <angel.herraez@ua...>  20100521 13:21:31

I just received news from Peter Ertl. The JME2 development is currently stalled with no known date for resuming it. ;( El 21 May 2010 a las 10:39, Angel Herráez escribió: > I've just found (from reading his recent paper in J.Cheminformatics) > that Peter Ertl is working on an opensource javascriptbased > equivalent of JME. Might be a good complement for Jmol. 
From: Angel Herráez <angel.herraez@ua...>  20100521 08:39:36

I've just found (from reading his recent paper in J.Cheminformatics) that Peter Ertl is working on an opensource javascriptbased equivalent of JME. Might be a good complement for Jmol. 
From: SourceForge.net <noreply@so...>  20100521 01:29:28

Bugs item #3005028, was opened at 20100520 20:29 Message generated for change (Tracker Item Submitted) made by rkanters You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: User interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rene Kanters (rkanters) Assigned to: Miguel (migueljmol) Summary: loss of feature in rev 12 Initial Comment: This could have happened a long time ago since I haven't been keeping my version up to date. But in the 11.x versions whenever you read a g03 output file with different input and standard orientations in a geometry optimization calculation, the AtomSetChooser would be able to show the same kind of orientations in the same 'folder'. The frequency calculation results would be in their own folder again. This makes it a lot easier to animate optimizations and stay within one set of orientations (so you don't get the flipping of the molecules). Between 11.6.x or so and 12 the reader has been modified so much that I can't really figure out any more how to set this up (even though I initially implemented it a long time ago). Sigh....  You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=379133&aid=3005028&group_id=23629 