Algorithms

Nelek wrote:

P.S. how about your template?

F_Variation=SumOn(i,j)[parm_i*parm_j*calib(i,j)]

Nelek wrote:

The programming will be easier

c#_keithy wrote:

Any ideas would be greatly appreciated

ashwiny wrote:

should i use the fopen,fclose and fread for this type of file?

Leslie Sanford wrote:

floating point seems faster.

Luc Pattyn wrote:

If you need to add code to prevent integers from overflowing, you should consider floats,
since unpredictable conditional branches are very bad for performance.

void Function(bool condition)
{
    for(int i = 0; i < 1000; i++)
    {
        if(condition)
        {
            // Do stuff.
        }
        else
        {
            // Do other stuff.
        }
    }
}

Luc Pattyn wrote:

If your inputs and outputs are integers, using floats will cost conversion times; most modern
CPUs have different register sets for ints and floats, and can pass data between them only
through "memory" (i.e. the data cache), adding to latency, and probably taking away some
performance.
If you need transcendental functions, floats are the obvious choice.
If you have streaming data the CPU might be optimized more for one or the other.
The Intel processor line has a long tradition of favoring integers over floats when spending
the transistor budget.
If your CPU is general-purpose (as opposed to DSP) and your algorithm needs a lot of
address calculations and indexing, you should consider float data, so the integer ALUs
are available for sequencing and addressing, the float ALU(s) for data operations.

if (condition) {
    for(loop_control) { stuff }
} else {
    for(loop_control) { other_stuff }
}