LISFLOOD-FP - Revision history

Tim-fewtrell at 12:28, 17 December 2009

2009-12-17T12:28:28Z

2009-12-17T12:28:21Z

2009-06-25T09:46:11Z

2009-06-16T17:06:20Z

2009-06-08T11:10:37Z

2009-06-08T10:10:15Z

2009-04-15T12:38:10Z

Checkpointing on Condor (beta)

2009-04-15T12:36:22Z

Checkpointing on Condor (beta)

2009-02-24T12:26:17Z

2009-02-23T12:16:59Z

@@ Line 6: / Line 6: @@
 ===Boundary Conditions===
-# In order to ensure that variable boundary conditions (i.e. <tt>.bdy</tt> file) on the floodplain and in the channel are applied, it is necessary to include two versions of the boundary condition; one for the channel and one for the floodplain with different names. In other words, the <tt>.river</tt> file should reference <tt>downstream1</tt> and the <tt>.bci</tt> file should reference <tt>downstream2</tt> where <tt>downstream2</tt> is a copy of <tt>downstream1</tt>.
+In order to ensure that variable boundary conditions (i.e. <tt>.bdy</tt> file) on the floodplain and in the channel are applied, it is necessary to include two versions of the boundary condition; one for the channel and one for the floodplain with different names. In other words, the <tt>.river</tt> file should reference <tt>downstream1</tt> and the <tt>.bci</tt> file should reference <tt>downstream2</tt> where <tt>downstream2</tt> is a copy of <tt>downstream1</tt>.
 ===Inertial and Channel Interaction===

@@ Line 7: / Line 7: @@
 ===Boundary Conditions===
 # In order to ensure that variable boundary conditions (i.e. <tt>.bdy</tt> file) on the floodplain and in the channel are applied, it is necessary to include two versions of the boundary condition; one for the channel and one for the floodplain with different names. In other words, the <tt>.river</tt> file should reference <tt>downstream1</tt> and the <tt>.bci</tt> file should reference <tt>downstream2</tt> where <tt>downstream2</tt> is a copy of <tt>downstream1</tt>.
 ===Inertial and Channel Interaction===

@@ Line 15: / Line 15: @@
 LISFLOOD-FP checkpointing on Condor should work out of the box. Do NOT include a .chkpnt file with the original submission - Condor will manage the checkpointing and file creation correctly. In addition, there has been an upgrade to Condor (v6.x to v7.2) which has been rolled out onto all the machines. The submit host for Condor has also changed from <tt><nowiki>dylan.ggy.bris.ac.uk</nowiki></tt> to <tt><nowiki>condor.ggy.bris.ac.uk</nowiki></tt>.
-;N.B. Condor with checkpointing functionality is still in "beta" - Check here for updates on when it is operational.:
+For Condor statistics and machine usage, check [http://intranet.ggy.bris.ac.uk/NewCondorView CondorView] *Requires UoB login*
 ===Channel Specification===

@@ Line 4: / Line 4: @@
 ==Usage Notes==
 ===Inertial and Channel Interaction===
@@ Line 15: / Line 19: @@
 ===Channel Specification===
 The river depth assigned in the channel solver is set as an elevation relative to the same datum as the DEM. However, using LiDAR or SRTM data often returns a value for the water surface, however spurious this value may be. Furthermore, channel information is often supplied as a depth rather than a channel bed elevation. Therefore, it is best to assign the channel elevation in the DEM as the bankfull height and specify the bed elevation in the .river file as your channel depth below the bankful height (elevation).
 ===File Output===

@@ Line 51: / Line 51: @@
 Our tests show that on a linux box the Intel compiler is about 1.5-2x faster than g++.
-==[[Lisflood_in_matlab|MATLAB Functions for LISFLOOD-FP]]==
+==MATLAB Functions for LISFLOOD-FP==
 Here is a repository of useful snippets of code for LISFLOOD-FP users in MATLAB:
 # [[Lisflood_in_matlab#File import and export|File import and export]]
 # [[Lisflood_in_matlab#Plotting flow vectors from .Qx and .Qy files|Plotting flow vectors]]
 # [[Lisflood_in_matlab#Making movies from .wd files|Making movies from LISFLOOD-FP output]]

← Older revision		Revision as of 10:10, 8 June 2009
Line 4:		Line 4:

	==Usage Notes==		==Usage Notes==
		+
		+	===Inertial and Channel Interaction===
		+	Care should be taken when using the <tt>ts_multiple</tt> keyword in tandem with the inertial/acceleration version of LISFLOOD-FP. The inertial model creates significantly longer time steps which, when used in conjuction with <tt>ts_multiple</tt> causes large instabilities in the channel model calculation. Testing is ongoing to assess limits for <tt>ts_multiple</tt> with the diffusive channel and inertial floodplain model combination.

	===Checkpointing on Condor (beta)===		===Checkpointing on Condor (beta)===

@@ Line 6: / Line 6: @@
 ===Checkpointing on Condor (beta)===
-LISFLOOD-FP checkpointing on Condor should work out of the box. Do NOT include a .chkpnt file with the original submission - Condor will manage the checkpointing and file creation correctly. This will currently only work with Condor v7.2.0 in 1.4N and will not work with the Condor version currently installed on Dylan.
+LISFLOOD-FP checkpointing on Condor should work out of the box. Do NOT include a .chkpnt file with the original submission - Condor will manage the checkpointing and file creation correctly. In addition, there has been an upgrade to Condor (v6.x to v7.2) which has been rolled out onto all the machines. The submit host for Condor has also changed from dylan.ggy.bris.ac.uk to condor.ggy.bris.ac.uk.
 ;N.B. Condor with checkpointing functionality is still in "beta" - Check here for updates on when it is operational.:

← Older revision	Revision as of 12:16, 23 February 2009
(No difference)