Changes (by Roland Haas):

status:

wontfix (was new)

Comment (by Roland Haas):

After some (offline) discussion with @Steven R. Brandt and some thinking about this, it turns out that rdwr.pl must accept inconsistent read / write statements and, since there is only one DECLARE_CCTK_ARGUMENTS_Foo per function Foo, the generated macro must use the union of the read / write statements.

This is because there can be (will be most likely) schedule.ccl that look like so:

if(evolve_Y_e) {
  schedule GRHydro_Con2Prim
  {
    READ: rho Y_e
  }
} else {
  schedule GRHydro_Con2Prim
  {
    READ: rho
  }
}

for codes where the state vector depends on runtime parameters.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2351/rdwrpl-accepts-inconsistent-read-write