JiMM

I wonder how bad the drag coefficient is. It must be horrible.

Amazing. I swear for a few seconds there I felt like a 13 Y.O. again! Thanks Ton.

AQ,

Thanks for the great idea. I didn't know you could drag them into the toolbar. Mine didn't have the icon either until I used the link. When the page re-loaded I got the icon.

And now I feel like a pile of #2

And since it's Friday:

"All right, brain. You don't like me and I don't like you, but let's just do this and I can get back to killing you with beer." :beer: :beer: :beer:

Glad you got the information you needed. If you need to find out why the VI you were left does not do what you need feel free to post it here for help.

Hi ednos,

That question would be easier to answer if you post the VI you are using to collect the data.

Another thing that would be usefull is either the data collected or a picture of the ACTUAL data, not a crayon depiction. What is the amplitude and time scale of the data for all three graphs? We cannot guess why it is not working if we also have to guess what it actually is doing. :beer:

QUOTE (TobyD @ Jun 9 2008, 04:59 PM)

This is fun stuff. Thanks for posting the link. I'm up to number 9! WooHoo!

That's exactly where I am!

QUOTE

I sent an email the first time I went to the web site :thumbup:

QUOTE (Phillip Brooks @ Jun 10 2008, 11:47 AM)

I just recieved an NI email about training (Ugh!) and noticed the link at the bottom to update my profile.

I decided to look at my profile a bit closer.

I wonder of the communications settings might put an end to receiving these types of calls? I just change Phone to "No".

http://lavag.org/old_files/monthly_06_2008/post-949-1213112834.png' target="_blank">

Thanks, Phillip, I just checked mine and all were set to "YES". I know that I had set Phone to NO. GRRRRR!

Yes, your 2.25MB BMP file is 68KB when saved as a PNG!

Holy Mackerel! I am stunned by how fast the Coding Chalenge winner did this. Of course it was obvious that clever math tactics would be necessary to minimize time, but .... just WOW. I got less than 1ms with that VI on my PC. AMAZING! :worship: I am not worthy!!!!!!

QUOTE (JDave @ Jun 4 2008, 06:32 PM)

Math efficiency is going to be a large part of keeping the speed down. A slow mathematical algorithm will be slow no matter have programmatically efficient you make it.

Oh, there is no doubt that knowing tricks of the mathematical trade will help solve those problems more efficiently. As is seen by the version thatn only looks to the smaller primes for divisibility. But I was not looking to set records. I am meerly looking for insights from better LV programmers as to how I can optimize my use of arrays, loops etc. Trying to polish my toolbox, and improve my ability to use it :thumbup:

I don't know if my wife would appreciate me starting up. It does look fun though.

It is interesting to both solve the problem, and then say "how can I do this better?" At work I to often get in the mode of solve the problem and move on. If it works, the boss doesn't care (or notice) if it's elegant, or efficient.

Amazing. I wonder how the bio-interface works. Fantastic things coming! :thumbup:

The first posted version was in LV8. I now have two revised versions. The first (Euler3_Take2.vi) fixes blatent errors in my first attempt - like I eliminated testing of even numbers (DUH!). That dropped execution to ~2.3 minutes. The third version (Euler3_VJT.vi) uses a theory that to test N for primality you only need to check for divisibility by all of the primes up to N/2. Not the route I was really looking for because it relies on number theory rather than programming efficiency, but interesting to try. That one dropped execution time to 1.2 minutes. And used up my lunch hour rather than a night The attached VIs are in LV7.1.

Antoine,

Thank you for introducing me to this fascinating challenge. My wife would not thank you I would be interested in any suggestions to improve my code. I can get the job done, but I am sure that my LV coding skills can only go up. Attached is my solution to the Euler project chalenge #3. I would love to hear any suggestions as to how to improve it's efficiency. I am not looking for fancy mathematical insights (won't help future projects). I have a solution, it's just slow (~4.5 minutes). What I am interested to learn is how to improve the code using more efficient LabVIEW practices. Thanks for any insights!

Wow, that's some beautiful code!

Greetings fellow wire-mongers. Jim from Atlanta, GA here. I've been a LAVA Lurker for a while, but a regular on NI forums.

Both have been great places for an education. :thumbup: