comp.lang.idl-pvwave archive: archive » Optimizing code for faster calculation

Home » Public Forums » archive » Optimizing code for faster calculation

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Optimizing code for faster calculation [message #88043 is a reply to message #88036]

Thu, 13 March 2014 17:46

Kenneth D
Messages: 3
Registered: March 2014

Junior Member

Thank you so much!

Converting my strings to index values and processing like this:

modeled_class[where(min_rmse GT rmse_threshold, /NULL)] = unmodeled_index

Totally made a difference! Now the biggest ding on my program is the built in function: min()

min_rmse = min(rmse_subset, min_subs, dimension=1)

I'm going to see if a histogram of this might be faster or something...

Additional Info:
My test case is a 200x200 matrix. My real world case is a 17000x17000 matrix
I'm using IDL 8.2.#, I tried my code on 8.3 at our university and the index (i) gave me an error, so I changed those to [i]. I blame it on switching between Python and IDL.

Report message to a moderator

[Message index]

		Optimizing code for faster calculation By: Kenneth D on Wed, 12 March 2014 23:33
		Re: Optimizing code for faster calculation By: Helder Marchetto on Thu, 13 March 2014 00:55
		Re: Optimizing code for faster calculation By: David Fanning on Thu, 13 March 2014 05:28
		Re: Optimizing code for faster calculation By: Heinz Stege on Thu, 13 March 2014 06:34
		Re: Optimizing code for faster calculation By: chris_torrence@NOSPAM on Thu, 13 March 2014 06:46
		Re: Optimizing code for faster calculation By: Kenneth D on Thu, 13 March 2014 17:46

Previous Topic:	Difficulty using cgimage2kml for swath data plotted in a cylindrical (Map_set) projection
Next Topic:	Force to print exponential to e-6

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 19:57:51 PDT 2025

Total time taken to generate the page: 0.00426 seconds