That sounds like a really cool trip. Have fun.
I am a little nervous that you are leaving and I am not further along on my SciPy paper. I am making progress, but still struggling to understand LinearElasticTerm.__call__. My main question is that the output of LinearElasticTerm.__call__ changes shape depending on whether it was called by assemble_vector or assemble_matrix in evaluate.py. assemble_vector is called by eval_residuals, while assemble_matrix is called by eval_tangent_matrices. Not suprisingly, the output of __call__ when called by assemble_vector is a vector (or really one vector per element) and the output when called by assemble_matrix is one matrix per element. The main difference as far as the input to LinearElasticTerm.__call__ is concerned is that the first element in args is either a vector or a matrix.
I guess I don't have my mind around what is going on inside LinearElasticTerm.__call__. By the nature of the calculation, does it automatically adapt to have its output match the size of the input vector or matrix, or are there different cases depending on input shapes?
3 files are attached. sfepy_flow_summary.pdf is a rough draft of trying to summarize the big picture of how my problem flows through the code. axial_rod_sfepy.py is the setup file for my 3D axial rod problem. axial_rod_log.pdf is basically a nicely formatted print out of various steps in the processing of axial_rod_sfepy.py.
Thanks,
Ryan
On Tue, Aug 12, 2008 at 5:14 AM, Robert Cimrman robert....@gmail.com wrote:
Hi all,
I will be hiking in Alps from 14. to 24. August, so keep posting your questions/bugreports/patches, I will process the unresolved ones as fast as possible after.
This week is unfortunately an IT infrastructure maintenance week at our university, so I may have problems getting on-line even before Thursday. It is already very slow.
best wishes, r.