Jump to content
TUFLOW Forum

ta007

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ta007

  • Rank
    Member
  • Birthday 01/02/1981

Profile Information

  • Gender
    Male
  • Location
    Brisbane

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Guys I came across this same issue recently when batching up some StormTide runs for a local LGA. I too had a grunt machine with multiple cards and whished to use loops in a batch file as I had many event scenarios. In my case I had 4 Tuflow licenses, 2 GPU add on modules and two GPU cards in our grunt machine. Ordinarily using classic I would use a loop in a batch file and limit my amount of runs based on instances of TUFLOW running in the 'tasklist' which is possible as each instance of TUFLOW correlates to 1 license and one CPU core. However trying to automate the process using loops is not so straight forward when you have multiple GPU cards - as each instance of TUFLOW can be split between multiple cards. In my case, the majority of my runs took similar time to run. So - I customized a batch file to switch between GPU cards when starting a new simulation. This is not ideal, as there will be times when two simulations may share the same graphics card (particularly problematic when running large models that use up all the GPU memory). However it works for the most part. Its super basic and clunky - but may help? See script below: @ echo off setlocal enabledelayedexpansion echo Model Design - HPC BRC ALL StormTide Simulations rem ______________SET RUN VARIABLES_____________ set TUFLOWEXE=C:\tuflow\TUFLOW.2018-03-AC\2018-03-AC\TUFLOW_iSP_w64.exe set RUN=start "TUFLOW" /low "%TUFLOWEXE%" -b set /a CPU_Cores=2 set /a GTX_Card=0 rem sets GPU card count to zero set tcf=BCR_~e1~_003a_~e2~_5m_03.tcf Set A=S T rem set B in loop below rem ______________SET LOOPS____________________ FOR %%a in (%A%) do ( rem _____DEFINE RUN LOGIC______ IF %%a==T ( set B=E_ F2030_ F2050_ F2070_ F2100_ F2130_ set C=HAT ) IF %%a==S ( set B=E_ F2050_ F2070_ F2100_ F2130_ set C=00020Y 00100Y 01000Y 10000Y ) rem ______________RUN LOOPS____________________ FOR %%b in (!B!) do ( FOR %%c in (!C!) do ( call :do_while_loop_start SET /a GTX_Card+=1 rem increment "up" GPU card count If /i !GTX_Card!==1 ( %RUN% -e1 %%a -e2 %%b%%c -pu!GTX_Card! %tcf% Set /a GTX_Card=-1 rem increment "down" GPU card count timeout 5 ) ELSE ( %RUN% -e1 %%a -e2 %%b%%c -pu!GTX_Card! %tcf% timeout 5 ) ) ) ) rem ___________COUNT RUN INSTANCES______________ :do_while_loop_start set /a count=0 for /f %%x in ('tasklist ^| find /c "TUFLOW"') do set count=%%x if %count% geq %CPU_Cores% ( PING 1.1.1.1 -n 1 -w 60000 >NUL goto do_while_loop_start ) endlocal run_BRC_03_All.txt
  2. Hi Tuflow I have a Stormtide Inundation Model with no upstream inflows and a downstream boundary which applies a temporally varying water level using a 2d_bc polyline (HX type - linearly varying) + 1d_bc Nodes + 1d_Nwk_Nodes. There are three subtly different water level timeseries which are applied across the HX line (along the shoreline of a coastal estuary) I wish to set an initial water level (IWL) based on only ONE of the time series (contained within a .csv file) which are referenced from the bc_dbase. I note the current version of TUFLOW allows the user to use an automatic method for setting IWL which works really well if you only have one downstream timeseries. i.e. Set IWL == AUTO I was wondering, is there some way I can set one of my timeseries as a variable using the "Set Variable" command and then reference this to set the IWL? I could imagine the syntax might look something like below - where WL1 is the timeseries I wish to apply as my IWL Set Variable WL1 == ..\..\Storm_Tide.csv | WL1 Set IWL == WL1 Tuflow would then apply WL1 the same way as the AUTO option. Can I already do something like this? Would save me Lots of time when I have MANY scenarios!!!!!!!
  3. I am currently testing existing regional flood models using the HPC solver. Most of these models have source inflows applied using traditional SA inflows. While switching to the HPC solver in the control files is easy - overcoming the limit applied to source inflows on individual cells (4 source inflows in total) becomes problematic, especially when the messages layer in the log files does not show specifically where there are too many inflows applied. Can anyone suggest a quick workaround?
  4. I am currently testing existing regional flood models using the HPC solver. Most of these models have source inflows applied using traditional SA inflows. While switching to the HPC solver in the control files is easy - overcoming the limit applied to source inflows on individual cells (4 source inflows in total) becomes problematic, especially when the messages layer in the log files does not show specifically where there are too many inflows applied. Can anyone suggest a quick workaround?
  5. Hi Phil, My first posting here. Was just wondering what attributes need to be selected when considering depth-flow (SD). I cant seem to download the zipped shape file above. Selecting the type as 'SD' for the 'pump' point and connecting via an SC line doesnt seem to connect the cells? The check layer indicates my 'pump' connects to the grid - but no connection at the outlet (end of the SC line). Kind Regards ta007
×
×
  • Create New...