Ticket #78 (new task)
pseudo-fields and the FieldTypeIsDensity macro
|Reported by:||dreynolds||Owned by:||somebody|
|Priority:||minor||Milestone:||Enzo 1.5 Code Development|
In the conversion to Enzo 1.5, a number of additional field types were added to typedefs.h (pseudo-fields). Immediately following their definition is an existing macro, FieldTypeIsDensity?, that returns TRUE or FALSE depending on whether the argument is a density field or not. This macro is now incorrect, given the newly-defined fields.
My question is this: will that cause a problem? The FieldTypeIsDensity? macro is used throughout the AMR handling of parent/child interfaces, so I would be somewhat concerned that any 'pseudo-field' (or for that matter a new emissivity field -- Geoffrey), would be treated incorrectly.