User 62a37f4796
17-08-2010 12:58:39
I have an MRV that was created by MarvinSketch 5.2.4.
I can read it in to MarvinSketch 5.3.7, but if I try to save it as a 5.3.7 MRV file, I am told that it is not a valid MRV format, and the application then throws a Stack Trace error:
chemaxon.marvin.io.MolExportException: document does not contain MolAtom@11576d7[O] (0) in MAtomSetPoint
at chemaxon.marvin.io.formats.cml.MrvExport.findMolAtomIds(Unknown Source)
at chemaxon.marvin.io.formats.cml.MrvExport.appendPoint(Unknown Source)
at chemaxon.marvin.io.formats.cml.MrvExport.appendMObject(Unknown Source)
at chemaxon.marvin.io.formats.cml.MrvExport.convert0(Unknown Source)
at chemaxon.marvin.io.formats.cml.MrvExport.convert(Unknown Source)
at chemaxon.marvin.common.swing.modules.LoadSave.prepareSaving(Unknown Source)
at chemaxon.marvin.common.swing.modules.LoadSave.saveAs(Unknown Source)
at chemaxon.marvin.common.swing.modules.LoadSave.saveAsPerformed(Unknown Source)
at chemaxon.marvin.common.swing.modules.LoadSave.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Any idea what's going on here? I have a huge number of 5.2.4 files that I'm not keen to convert to 5.3.7 if this comes up frequently.
Thanks,
Michiel
UPDATE 1: the incompatibility with 5.2.4 turns out to be a red herring. 5.2.4 can be processed by 5.3.4, but not by 5.3.7. In fact, 5.3.7 cannot write the same information contained in the 5.2.4 file even if drawn in completely from scratch .... there's something flaky about the write-out module in 5.3.7, because the built-in structure checker tells me everything's OK.
UPDATE 2: 5.3.6 gives the same error; 5.3.5 seems to work OK so far ...