rmfs aren't compatible with chimera

[shanot]

description of bug:

opening an rmf3 file generated by latest imp/pmi results in error:

Error while processing output/rmfs/0.rmf3:
"usageError: "Enum value not defined"" while loading file data

how to reproduce bug:

1. use imp 6351513,
2. use pmi 1691f1331bc821ece0793267a51436f82a6cc0ab,
3. run the rnapolii modeling script of the imp_tutorial on 1 core,
4. open modeling/rmfs/0.rmf3 with chimera

[Pellarin]

It can be related to the recent IMP.rmf change to incorporate IMP.atom.Chain sequence and type. However it could be also a bug in chimera, in that case, I don't know how to proceed, because I guess Chimera's rmf is not maintained anymore!

[benmwebb]

Use the Report a Bug menu option in Chimera - this is clearly a bug at their end. As Riccardo points out, it's likely because they are getting confused by recent extensions, either the addition of new attributes to Chain or (more likely in my opinion) the new node type I added for provenance info. They should just be ignoring stuff like this that they don't expect.

[shanot]

I reported the bug to chimera. Will update here when I hear from them.

[benmwebb]

This is probably coming from the copy of RMF in Chimera. Either they'll need to update it, or I can look into adding some forward compatibility support to RMF, and they can backport the patch.

[benmwebb]

Simplest solution would be for the Chimera folks to backport salilab/rmf@d00edc4e.

[shanot]

they have fixed it, it will be in the next build.
http://plato.cgl.ucsf.edu/trac/chimera/ticket/15898