#12299: Advance Jmol Interactive Features in Flask Notebook
------------------------------------------------------------+---------------
       Reporter:  gutow                                     |         Owner:  
jason, mpatel, was                                        
           Type:  enhancement                               |        Status:  
needs_work                                                
       Priority:  major                                     |     Milestone:  
sage-5.2                                                  
      Component:  notebook                                  |    Resolution:    
                                                        
       Keywords:  Jmol, 3D, notebook                        |   Work issues:  
very minor doc issues                                     
Report Upstream:  Workaround found; Bug reported upstream.  |     Reviewers:  
Karl-Dieter Crisman, Steven Trogdon, Punarbasu Purkayastha
        Authors:  Jonathan Gutow                            |     Merged in:    
                                                        
   Dependencies:  #11080,#11078,#11503                      |      Stopgaps:    
                                                        
------------------------------------------------------------+---------------

Comment (by gutow):

 Replying to [comment:95 kcrisman]:
 > > Decided to keep JmolData specific error as may need it for movie
 generation.
 >
 > Sorry, still 'needs work'.  ''Every'' method needs doctesting.  In
 particular, the !JmolDataError needs a docstring and test in its
 {{{__init__}}} and {{{__str__}}} methods.
 No biggy. I hope to have time to get to it tomorrow.  Have a research
 student in all day working on building a high-powered node (8 cores) for
 our quantum mechanics cluster.
 > Will increasing the Jmol memory cause problems?   I don't have time to
 do any more Jmol testing right now, how much more memory are we talking,
 where does it live?
 This just brings the memory used by the image generating application up to
 what is used by the applet in the browser (512 MB of heap--much can be
 virtual).  Anyway, the image generating application should now be able to
 handle data sets at least as big as the applet.  It should have no effect
 on the in browser memory issues.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12299#comment:97>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to