Closed ClairePA closed 7 years ago
I save the xhelm as a file, and then try to load it to the demo site. The app complains R is an unknown monomer.
The HELM string is the file is RNA1{R(A)p.r(C)p.r(G)p.r(U)p}$$$$V2.0, where R is not defined in Monomers list.
xHELM should be independent of the monomers since they are defined in the monomer list, tried again with a file generated by the web-editor version which is using the old monomer list and it still complains. I think the issue is the mismatch between base64 encoded molfiles expected by the toolkit and non-base64 encoded xHELM file generated by the web-editor. The HELM notation currently specifies base64 encoding. Discussing with Tianhong.
The web editor does accept both base64-encoded and plaintext mol string
It does accept both formats, but needs to create the encoded version. I am using the version via these links http://elncloud.com/helm/helm/index.htm and it is giving me a non-encoded file.
Confirmed fixed. xHELM can be generated and read into both editors and new monomers are recognised. Perfect.
I created the following xHELM string and validated it using the toolkit. The editor returns an error 'null' when I try to load it. As the monomer definitions are contained within the file there should be no monomer set incompatibilities.