<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16788" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I have been able to render a surface using a jvxl file. The Jmol command that I used was isosurface surface_cn "../images/b/ba/1kyo_cn.jvxl ". The file url is relative to the url of the page. When I sent the command through the Jmol console, the surface appeared in one or two seconds. But through the green link the rendering take five minutes or more, but then ever since last Friday it has been taking all the green links to respond.</DIV>
<DIV> </DIV>
<DIV>Karl</DIV>
<DIV><BR><BR>>>> Eran Hodis <eran.hodis@weizmann.ac.il> 1/30/2009 3:04 PM >>><BR>Karl,<BR><BR>Changed it so that jvxl is now a permitted file upload type. Give it a try.<BR><BR>What Angel said is exactly what we've wanted to do for a while now. We know that Proteopedia is not handling surface creation and display optimally, both with the menu offered for creation and manipulation of the surface in the Scene Authoring Tools, as well as with the fact that the surfaces must be recalculated each time rather than having them saved on the server for quick loading. Now seems like a good time to address the these issues on Proteopedia.<BR><BR>Eran<BR><BR>-----Original Message-----<BR>>From Karl Oberholser <oberhols@messiah.edu><BR>Sent Fri 1/30/2009 9:23 PM<BR>To Forum for the Proteopedia User Community <proteopedialist-for-users@bioinformatics.org><BR>Subject Re: [Proteopedia] Script compiler error<BR><BR>Eran and Jaim,<BR>If
jvxl could be made to be an acceptable file type for uploading, I think<BR>that I will be able to display a surface in PP by drawing it using a jvxl<BR>data file, and thereby avoid the long computation time. At least I would<BR>like to try doing it.<BR><BR>Karl<BR><BR>>>> "Angel Herraez" <angel.herraez@uah.es> 1/30/2009 10:05 AM >>><BR>I've managed to reach the source of the script files saved for <BR>scenes. Those contain the isosurface command, as expected.<BR>So the solution would be to implement in the SAT a way to substitute <BR>the isosurface generation code for an isosurface loading code, plus <BR>to save the isosurface to a file on the server. <BR>Not trivial at all!<BR><BR><BR><BR>_______________________________________________<BR>Proteopedialist-for-users mailing list<BR>Proteopedialist-for-users@bioinformatics.org <BR><A href="http://www.bioinformatics.org/mailman/listinfo/proteopedialist">http://www.bioinformatics.org/mailman/listinf
o/proteopedialist</A>-for-users<BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <<A href="http://www.bioinformatics.org/pipermail/proteopedialist">http://www.bioinformatics.org/pipermail/proteopedialist</A>-for-users/attachments/20090130/5feb3109/attachment.html><BR>_______________________________________________<BR>Proteopedialist-for-users mailing list<BR>Proteopedialist-for-users@bioinformatics.org<BR><A href="http://www.bioinformatics.org/mailman/listinfo/proteopedialist">http://www.bioinformatics.org/mailman/listinfo/proteopedialist</A>-for-users<BR><BR><BR>_______________________________________________<BR>Proteopedialist-for-users mailing list<BR>Proteopedialist-for-users@bioinformatics.org<BR><A href="http://www.bioinformatics.org/mailman/listinfo/proteopedialist">http://www.bioinformatics.org/mailman/listinfo/proteopedialist</A>-for-users<BR></DIV></BODY></HTML>