Opened 5 years ago

Last modified 5 years ago

#1560 reopened enhancement

Calculate solution error in EinsteinExact

Reported by: Erik Schnetter Owned by:
Priority: major Milestone:
Component: EinsteinToolkit thorn Version: development version
Keywords: Cc:


I implemented a facility to calculate the solution error as analysis quantity in EinsteinExact. I pushed this to a new branch eschnett/solution-error.

Attachments (0)

Change History (6)

comment:1 Changed 5 years ago by Erik Schnetter

Status: newreview

comment:2 Changed 5 years ago by Barry Wardell

Status: reviewreviewed_ok

This looks good to me. It would be nice to avoid using the internal TensorTools notation with the replacement rules, but I can't think of a good way to do so right now, so please feel free to merge the proposed version into master.

comment:3 Changed 5 years ago by Erik Schnetter

Resolution: fixed
Status: reviewed_okclosed


comment:4 Changed 5 years ago by Ian Hinder

The way I have done this in the past is to add new variables for the exact solution rather than using the ADM variables. You can then output these, which give you the exact solution, and add a calculation which subtracts the ADM variables from the exact solution, and populates the error variables. This way, you can have all quantities available, and as a side benefit, you don't need to do the pattern matching on the calculation.

So you would have this:

calcExact = {
  gxxExact -> …,

calcADMBase = {
  gxx -> gxxExact,

calcError = {
  gxxError -> gxx - gxxExact,

You would then schedule this so that the exact, ADMBase and error calculations are always run at INITIAL. Then, depending on the parameters, you would either:

  1. Calculate exact, ADMBase and error also during evolution. This would preserve the current expected behaviour of the ADMBase variables containing the exact solution for the whole evolution. OR
  2. Calculate just the exact and error variables during evolution, so that the error variables contain the error of the (separate) evolution of the ADMBase variables.

It is also useful to compute the gridfunction whose norm is the norm of the whole solution error. i.e.

  uErr = sqrt((gErr_ij)^2 + (KErr_ij)^2 + alpErr^2 + (betaErr^i)^2).

Then you can output the norm of this from Cactus, and you can look at convergence for the entire (ADM) solution very easily.

comment:5 Changed 5 years ago by Barry Wardell

Resolution: fixed
Status: closedreopened

This does sound like a good solution. The only potential problem is that simulations could use a lot more memory since there are now a whole extra set of variables required for the exact solution. Would you consider that to be a problem? I guess we're typically not limited by memory in situations where exact solutions are used, so maybe it's not such a big deal.

comment:6 Changed 5 years ago by Erik Schnetter

The new variables would only be active if requested in the parameter file.

Modify Ticket

Change Properties
Set your email in Preferences
as reopened The ticket will remain with no owner.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from (none) to the specified user.
The owner will be changed from (none) to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.