The correct shape means the difference between adding (correct) 20% thrust, or robbing (wrong shape) 50% thrust - and the shape is determined from how it will be used, which I somehow need to ask my users to tell me so I can compute it.

must it be fixed, or can you manage a variable nozzle arrangement). Hi Karen (and toller): would you be able to spare 5 or 10 mins to help me narrow down the questions my add-in needs to ask to produce useful ducts for people? Maybe post in the forum below (or reply by email to ): It would be useful to learn what kind of duct you want (I assume for a prop? if not - tell me!), and what information you already know (or can reasonably find out) about it (speed ranges, size, thrust needed, medium, etc) and how you intend to construct it (e.g. I'm able to give this away for free because another software product I wrote pays my wages indefinitely - that's the cool thing about software: write it well, and it works indefinitely for you, and you get to spend the money it earns for you :-) The 'back end' stuff runs on a cluster with 204 high-speed CPUs. Software is a great area to get into - especially if you've got 'the knack' (i.e.

I'm able to give this away for free because another software product I wrote pays my wages indefinitely - that's the cool thing about software: write it well, and it works indefinitely for you, and you get to spend the money it earns for you :-) Thanks for the kind review! There are 3 parts to this app: the Fusion 360 add-in (written in Python), the particle-swarm and genetic optimizer (written in Perl), and the CFD solver (Written in Fortran - I kid you not). Software is a great area to get into - especially if you've got 'the knack' (i.e. The 'back end' stuff runs on a cluster with 204 high-speed CPUs. Thanks for the kind review! There are 3 parts to this app: the Fusion 360 add-in (written in Python), the particle-swarm and genetic optimizer (written in Perl), and the CFD solver (Written in Fortran - I kid you not).

Rc wing airfoil generator software