~fluidity-core/fluidity/fluidity-gmsh2triangle-fix-reordering : changes

~fluidity-core/fluidity/fluidity-gmsh2triangle-fix-reordering » Changes from revision 3950

From Revision 3950 to 3931

Rev	Summary	Authors	Date
3950	Also remove remapping for the case where gmsh's nodes are no... Also remove remapping for the case where gmsh's nodes are not consecutively numbered (this also didn't deal with the .face/.edge file).	Stephan Kramer	12 years ago
3949	Merge from trunk. Merge from trunk.	Stephan Kramer	12 years ago
3948	gmsh2triangle no longer taking out isolated nodes and theref... gmsh2triangle no longer taking out isolated nodes and therefore renumbering. The renumbering was only done half way and we shouldn't rely on this feature as fluidity also read gmsh files directly.	Stephan Kramer	12 years ago
3947	Following the update of spud in Fluidity to r.520 of lp:spud... Following the update of spud in Fluidity to r.520 of lp:spud, this commit updates all options files in the Fluidity trunk, resulting from running tools/update_options.py.	Tim Greaves	12 years ago
3946	Merging upstream updates to spud into the Fluidity trunk; th... Merging upstream updates to spud into the Fluidity trunk; this brings the local copy in Fluidity in sync with r.520 of the spud trunk.	Tim Greaves	12 years ago
3945	Small changes to the mphase_tephra_settling test to reduce t... Small changes to the mphase_tephra_settling test to reduce the runtime. Passes locally.	Christian Jacobs	12 years ago
3944	Shortening the test again. Should be half the time now Shortening the test again. Should be half the time now	Jon Hill	12 years ago
3943	One-line fix in buildsystem only targetting bug lp:920446. One-line fix in buildsystem only targetting bug lp:920446. This checks for an empty DESTDIR and replaces such with / rather than supplying an empty --root= which was causing problems with distutils. Thanks to Patrick, Florian, and Stephan for input.	Tim Greaves	12 years ago
3942	And four became two. Hopefully this passes in less than 10 m... And four became two. Hopefully this passes in less than 10 mins on buildbot	Jon Hill	12 years ago
3941	Change solver and steady state tolerances to speed this test... Change solver and steady state tolerances to speed this test up. Now runs in less than 1 minute on my system.	Rhodri Davies	12 years ago
3940	Shortening gls-KP test by remove one of the four tests withi... Shortening gls-KP test by remove one of the four tests within this	Jon Hill	12 years ago
3939	Relax two tolerances for the intel build for this recently a... Relax two tolerances for the intel build for this recently added test. 5.0e-03 --> 8.0e-03 (integral of tracer) 5.0e-04 --> 6.0e-04 (min of tracer)	Brendan Tollit	12 years ago
3938	Small correction to last merge. Only use the relevant variab... Small correction to last merge. Only use the relevant variables from Global parameters and correct some repetetive English in a couple of FLExit's.	Brendan Tollit	12 years ago
3937	Remove the porosity from the DG_CourantNumber and ControlVol... Remove the porosity from the DG_CourantNumber and ControlVolumeCFLNumber diagnostic fields. Add three new diagnostic fields being InterstitialVelocityCGCourantNumber, InterstitialVelocityCVCourantNumber and InterstitialVelocityDGCourantNumber which are only for porous media flow where the Darcy velocity (= porosity * interstitial velocity) is solved for. These are magic named diagnostic fields rather than algorithm names due to the way the courant number fields are already used. Everywhere in the options where ControlVolumeCFLNumber can be selected (such as CV face value schemes) permit the selection of InterstitialVelocityCVCourantNumber. For CV (or coupled CV) discretised fields there is a restriction that all the 'porosity' fields used must be the same with the same theta averaging also, due to the way this is obtained from one call in Field_Equations_CV. The default options when used satisfy this constraint. For adaptive time stepping also permit the selection of InterstitialVelocityCGCourantNumber. If an InterstitialVelocityCG/CV CourantNumber is used for adaptive time stepping then always force its calculation in this routine as the options here may be different to a field that may exist in the state. For a scalar field discretised with DG add the small new capability to select which Courant number field to use for the temporal sub cycling with the available selections being DG_CourantNumber and InterstitialVelocityDGCourantNumber. To avoid changing all the test cases, by default if not activated this option will do as before and use DG_CourantNumber. Add a copy of a short darcy flow test case that now discretises the tracer with DG using subcycling and adaptive time stepping related to the new interstitial velocity courant number fields. Adjust all relevant darcy test cases to also test this. Add a routine in assemble/Porous_Media.F90 to find the theta averaged porosity field, to avoid a code copy in the adv-diff CG/CV/DG routines. Add to the manual a description of the three new diagnostic fields and adjust the configuring Porous media flow section as required.	Brendan Tollit	12 years ago
3936	Remove the finest simulation (_E) from the Burgers MMS repla... Remove the finest simulation (_E) from the Burgers MMS replay test. This should hopefully speed up the test so that it falls within buildbot's 20-minute limit ..	Patrick Farrell	12 years ago
3935	Forgot an option check. Sorry for the noise. Forgot an option check. Sorry for the noise.	Axelle Vire	12 years ago
3934	Correct Brendan's option check regarding the use of CV for c... Correct Brendan's option check regarding the use of CV for continuity with two-way coupling. Apologies that it hasn't been done before the merge.	Axelle Vire	12 years ago
3933	Relax a tolerance on this test with Brendan's consent. The t... Relax a tolerance on this test with Brendan's consent. The test was passing locally but failed on independent buildbot branches.	Axelle Vire	12 years ago
3932	Loose the tolerance on this test slightly (with Brendan's co... Loose the tolerance on this test slightly (with Brendan's consent) since it makes the trunk fails locally on my Maverick machine.	Axelle Vire	12 years ago
3931	Bug-fix for SampleNetCDF which is used in tidal boundary con... Bug-fix for SampleNetCDF which is used in tidal boundary conditions. This bug would occur whenever a node was interpolated that is located exactly on one any of the constant longitutde or latitude lines of the input netcdf grid. In this case instead of interpolating between the value of the 2 nearest nodes, the value was extrapolated. This code clearly needs some more tests. Coming up...	Stephan Kramer	12 years ago

Older »