Skip to content
Snippets Groups Projects
Commit 256e4ce6 authored by Oliver Sander's avatar Oliver Sander Committed by sander@PCPOOL.MI.FU-BERLIN.DE
Browse files

bugfix: don't disregard initial rod configuration when computing errors

[[Imported from SVN: r1609]]
parent db9bbf00
No related branches found
No related tags found
No related merge requests found
......@@ -138,10 +138,8 @@ int main (int argc, char *argv[]) try
rodX.back().q = Quaternion<double>(axis, M_PI*angle/180);
std::cout << "Right boundary orientation:" << std::endl;
std::cout << "director 0: " << rodX[rodX.size()-1].q.director(0) << std::endl;
std::cout << "director 1: " << rodX[rodX.size()-1].q.director(1) << std::endl;
std::cout << "director 2: " << rodX[rodX.size()-1].q.director(2) << std::endl;
// Backup initial rod iterate for later reference
RodSolutionType initialIterateRod = rodX;
int toplevel = rodGrid.maxLevel();
......@@ -467,7 +465,9 @@ int main (int argc, char *argv[]) try
// from zero anyways
oldError += computeEnergyNormSquared(exactSol3d, *hessian3d);
/** \todo Rod error still missing */
// Error of the initial rod iterate
RodDifferenceType rodDifference = computeRodDifference(initialIterateRod, exactSolRod);
oldError += computeEnergyNormSquared(rodDifference, hessianRod);
oldError = std::sqrt(oldError);
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment