[FLASH-BUGS] Constant parameters from ignored units override parameters from included units.
Aaron Froese
aaron.froese at generalfusion.com
Mon Feb 28 16:58:57 CST 2011
Hi,
I am writing code to include anisotropic conductivity, viscosity, and resistivity into the USM solver. However, I have come across some peculiar behaviour by the setup script.
The new code is inconsistent with the existing materialProperties units, so I re-declare the three parameters use_Conductivity, use_Viscosity, and use_Resistivity.
I use the setup command:
./setup ConductionDelta-aniso -2d -auto \
-with-unit=physics/Hydro/HydroMain/unsplit/Anisotropic_MHD \
-without-unit=physics/materialProperties/Conductivity \
-without-unit=physics/materialProperties/Viscosity \
-without-unit=physics/materialProperties/MagneticResistivity
However, the setup_params file contains the values in the Conductivity and Viscosity Config files instead of the correct values in Anisotropic_MHD.
physics/materialProperties/Conductivity
useConductivity [BOOLEAN] CONSTANT [FALSE]
flags whether the conductivity material property is being used
physics/materialProperties/Viscosity
useViscosity [BOOLEAN] CONSTANT [FALSE]
flags whether the viscosity material property is being used
Notice that this only happens for Conductivity and Viscosity, but not Resistivity. I think this is because use_Resistivity is declared without the CONSTANT keyword, but the other two are.
Without delving into the workings of the setup script, I have found a workaround by renaming the materialProperties directory before running the setup script.
Best regards,
Aaron
More information about the flash-bugs
mailing list