lp:~fluidity-core/fluidity/hector_hacks
- Get this branch:
- bzr branch lp:~fluidity-core/fluidity/hector_hacks
Branch merges
Branch information
Recent revisions
- 4141. By Stephan Kramer
-
Hopefully fixing the intel debug build.
For some bizarre reason intel started to choke on a bit of debugging code, code that is perfectly legal and hasn't changed for a long time. However on reading the code I realized the debugging check was actually incorrect. So hopefully fixing that will also placate the intel compiler.
- 4140. By Cian Wilson
-
Merging in changes from lp:~amcg-stokes/fluidity/multimaterial_diagnostic_dependencies. This changes the behaviour of diagnostic algorithm's dependency search when material_phase support is set to multiple. It now searches across all material_phases for FieldName. The behaviour when material_
phase_support is set to single or when StateName: :FieldName is given is unchanged. This has been tested using the example of bulk_viscosity under Viscosity which now depends on MaterialViscosity (requires options file that use it to be updated), which is found across all material_phases as it should be. - 4138. By Stephan Kramer
-
Merging in of the viscous free surface branch.
This implements the free surface algorithm that enforces a no normal stress condition at the free surface, instead of p=0. For more details, see http://
dx.doi. org/10. 1016/j. pepi.2012. 01.001
To use, simply add the no_normal_stress option under the free_surface boundary condition and switch the FreeSurface field from diagnostic to prognostic.
As this is required for testing, this commit also introduces the option to apply remove_null_space seperately for components of a vector solve.This is a Team Stokes production. Thanks to Simon F. for reviewing.
- 4137. By Frank Milthaler <<email address hidden>.
-
forgot to change the xml of the example flow_past_
sphere_ Re1000 in revision 4135. this commit fixes that. - 4136. By Stephan Kramer
-
Bug-fix: small inconsistency in memory registration for csr sparsities lead to spurious memory leak reports.
- 4135. By Frank Milthaler <<email address hidden>.
-
The user is now allowed to define how many body forces they want to compute, whereas one body force could be assembled by 1 or more surface ids in the mesh. The user then gives each body force a unique name, which will be dumped as such in the stat file, e.g. force_uniquebod
yforcename% 1 is the x component of the body force which has the name uniquebodyforce name.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:fluidity