[ET Trac] [Einstein Toolkit] #572: Change scoping of TmunuBase parameter to allow parameter checking in other thorns

[Einstein Toolkit]

#572: Change scoping of TmunuBase parameter to allow parameter checking in other
thorns
-------------------------------+--------------------------------------------
  Reporter:  filga@…           |       Owner:        
      Type:  defect            |      Status:  review
  Priority:  major             |   Milestone:        
 Component:  Other             |     Version:        
Resolution:                    |    Keywords:        
-------------------------------+--------------------------------------------

Comment (by rhaas):

 (written in parallel to Erik's reply, so please ignore duplicate
 information)

 checking parameters in paramcheck might be a good idea, so changing of
 scope would make sense (the other option being to move
 SetStressEnergyState into WRAGH [or STARTUP? if there is already storage
 available there]). I am not sure if steering the parameter to the
 "desired" value in paramcheck is possible/effictive/a good idea though.
 The parameter controls storage in schedule.ccl which is executed before
 paramcheck (before any scheduled function in fact), so steering does not
 help. You would have to use GroupStorageIncrease I would think.

 Changing scope of the paremeter will change the arguments to ParameterSet
 (http://einsteintoolkit.org/documentation/ReferenceManual/ReferenceManualch2.html#x4-142000A2):
 {{{
 Parameters

 name Parameter name
 thorn Thorn name (for private parameters) or implementation name (for
 restricted parameters)
 value The new (stringified) value for the parameter parameter
 }}}
 which is fine in this case (since both at thorn name and implementation
 name are "TmunuBase").

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/572#comment:5>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit