No secret at all... As you might have guessed, it is global model fields that I am working with:
360x180 (lon,lat) I have three 'z' levels. (360,180,3) Then I have different 'fields', usually on the order of ~50-80 (360,180,3,60) Lastly, I have output for a several timesteps, then those timesteps ultimately become summed for each field, but in the interim I need.. (360,180,3,60,x) I am currently working on a f2py solution, but it has caused me some problems as well... The format of the data is not something I can change, though I may be able to read it in in smaller 'chunks', say creating separate arrays for each field, or day. -- View this message in context: http://www.nabble.com/More-efficient-array-processing-tp20136676p20141712.html Sent from the Python - python-list mailing list archive at Nabble.com. -- http://mail.python.org/mailman/listinfo/python-list
