(sin (* z0 PI))

Percentage Accurate: 51.6% → 51.6%
Time: 1.8s
Alternatives: 1
Speedup: 1.0×

Specification

?
\[\sin \left(z0 \cdot \pi\right) \]
(FPCore (z0)
  :precision binary64
  (sin (* z0 PI)))
double code(double z0) {
	return sin((z0 * ((double) M_PI)));
}

public static double code(double z0) {
	return Math.sin((z0 * Math.PI));
}

def code(z0):
	return math.sin((z0 * math.pi))

function code(z0)
	return sin(Float64(z0 * pi))
end

function tmp = code(z0)
	tmp = sin((z0 * pi));
end

code[z0_] := N[Sin[N[(z0 * Pi), $MachinePrecision]], $MachinePrecision]

\sin \left(z0 \cdot \pi\right)

Local Percentage Accuracy vs ?

The average percentage accuracy by input value. Horizontal axis shows value of an input variable; the variable is choosen in the title. Vertical axis is accuracy; higher is better. Red represent the original program, while blue represents Herbie's suggestion. These can be toggled with buttons below the plot. The line is an average while dots represent individual samples.

Accuracy vs Speed?

Herbie found 1 alternatives:

AlternativeAccuracySpeedup
The accuracy (vertical axis) and speed (horizontal axis) of each alternatives. Up and to the right is better. The red square shows the initial program, and each blue circle shows an alternative.The line shows the best available speed-accuracy tradeoffs.

Initial Program: 51.6% accurate, 1.0× speedup?

\[\sin \left(z0 \cdot \pi\right) \]
(FPCore (z0)
  :precision binary64
  (sin (* z0 PI)))
double code(double z0) {
	return sin((z0 * ((double) M_PI)));
}

public static double code(double z0) {
	return Math.sin((z0 * Math.PI));
}

def code(z0):
	return math.sin((z0 * math.pi))

function code(z0)
	return sin(Float64(z0 * pi))
end

function tmp = code(z0)
	tmp = sin((z0 * pi));
end

code[z0_] := N[Sin[N[(z0 * Pi), $MachinePrecision]], $MachinePrecision]

\sin \left(z0 \cdot \pi\right)

Reproduce

?
herbie shell --seed 2025271 -o generate:taylor -o generate:evaluate
(FPCore (z0)
  :name "(sin (* z0 PI))"
  :precision binary64
  (sin (* z0 PI)))