Reply To: Fluent

[Rob]

Start with the default number of steps and see what happens: they're usually good enough. If you get a high number of incomplete tracks look to see why before increasing the maximum number. If tracks are stuck somewhere you may just use more cpu for no gain; if the tracks are still heading somewhere but (for example) swirling as in a cyclone try doubling the max number. Fluent uses up to that number, but if you get a rogue parcel or few and add a silly maximum value you could be waiting for a while for no good reason.