Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

New DualSPHysics v3.2
  • We are pleased to announce the release of new packages of DualSPHysics (v3.2) that includes the executable of the multi-phase code by Fourtakas et al. (2014) that deals with two-phase liquid-solid problems with flow-induced erosion of fully saturated sediment. The model predicts multi-phase sediment scouring phenomena that are induced by rapid flows creating shear forces at the surface of the sediment which causes the surface to yield and produce a shear layer of sediment suspended particles at the interface and finally sediment suspension in the fluid.

    - This is a beta version, so support and stuff on the forum is limited and you should read the readme file ("MPhase_V3.0_Beta_README.txt") and the PDF ("Guide_CaseTwoPhases.pdf") included in the new version.

    - A new testcase ("CASETWOPHASES") is also included to be executed with the new executable (“DualSPHysics_win64_MPhase”).

    REFERENCE: Fourtakas, G., B.D. Rogers, and D.R. Laurence. 3-D SPH Modelling of Sediment Scouring Induced by Rapid Flows. in 9th International SPHERIC SPH Workshop. 2014. Paris, France.
  • Hi Alex,

    Thank you for the update. I downloaded the new version and tried to run the two-phase case. However it stoped after the initialising step. I can see that for the raw case only 3506 particles so it seems not the problem of computational efficiency but more like something like a endless loop. Could you have a look at it? Thanks!

    Yi Pan
  • Can you please paste here the output from Run.out?
    Regards


  • Copyright (C) 2015 by Dr Georgios Fourtakas,
    Dr Jose M. Dominguez, Dr Benedict Rogers, Dr Alejandro Crespo,
    Prof. M. Gomez Gesteira, Dr Anxo Barreiro, Dr Ricardo Canelas,
    Dr Renato Vacondio.

    EPHYSLAB Environmental Physics Laboratory, Universidade de Vigo
    School of Mechanical, Aerospace and Civil Engineering, University of Manchester

    DualSPHysics is free software: you can redistribute it and/or
    modify it under the terms of the GNU General Public License as
    published by the Free Software Foundation, either version 3 of
    the License, or (at your option) any later version.

    DualSPHysics is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License,
    along with DualSPHysics. If not, see .


    DUALSPHYSICS for MultiPhase V3.0 (22-09-2015)
    ==============================================
    [Select CUDA Device]
    Device 0: "GeForce GTX 760"
    Compute capability: 3.0
    Multiprocessors: 6 (1152 cores)
    Memory global: 2048 MB
    Clock rate: 1.07 GHz
    Run time limit on kernels: Yes
    ECC support enabled: No

    [GPU Hardware]
    Device default: 0 "GeForce GTX 760"
    Compute capability: 3.0
    Memory global: 2048 MB
    Memory shared: 49152 Bytes
    [Initialising JSphGpuSingle v3.00 30-09-2015 16:29:50]

    [Multi-phase configuration]
    PhaseCount=2
    Phase_0-> mkfluid:0 idbegin:800 count:594 rhop0:1090119490620926500000000000.000000 csound:72250710197730502000000000000.000000 gamma:0.000000
    Phase_1-> mkfluid:1 idbegin:1394 count:2112 rhop0:198560776821242030000000000000.000000 csound:4592633630852250300000000000.000000 gamma:68872225043086548000000.000000

    **Case configuration is loaded
    Loading initial state of particles...
    Loaded particles: 3506 (3506+0)
    MapPos(border)=(0.002461,0.999961,0.002461)-(4.007539,1.000039,4.007539)
    MapPos=(0.002461,0.999961,0.002461)-(4.007539,1.000039,24.032930)
    **Initial state of particles is loaded
    **2D-Simulation parameters:
    CaseName="CaseTwoPhases"
    RunName="CaseTwoPhases"
    SvTimers=True
    StepAlgorithm="Symplectic"
    Kernel="Wendland"
    Viscosity="SumSPS"
    Visco=0.000100
    ShepardSteps=0
    DeltaSph="DBC"
    DeltaSphValue=0.100000
    CaseNp=3506
    CaseNbound=800
    CaseNfixed=800
    CaseNmoving=0
    CaseNfloat=0
    PeriodicActive=0
    Dx=0.030000
    H=0.039032
    CteB=554965.687500
    Gamma=7.000000
    Rhop0=1000.000000
    Eps=0.000000
    Cs0=3461172224.000000
    CFLnumber=0.100000
    DtIni=0.000000
    DtMin=0.000000
    MassFluid=0.900000
    MassBound=0.450000
    WendlandCte.awen=365.600677
    WendlandCte.bwen=-46836.468750
    TimeMax=2.000000
    TimePart=0.010000
    Gravity=(0.000000,0.000000,-9.810000)
    PartOutMax=2706
    RhopOut=True
    RhopOutMin=100.000000
    RhopOutMax=3000.000000
    CellOrder="XYZ"
    **Requested gpu memory for 3506 particles: 1.0 MB.
    **CellDiv: Requested GPU memory for 3506 particles: 0.0 MB.
    **CellDiv: Requested gpu memory for 16016 cells (CellMode=2H): 0.2 MB.
    CellMode="2H"
    Hdiv=1
    MapCells=(52,1,308)

    PtxasFile="../../EXECS/DualSPHysics_win64_MPhase_ptxasinfo"
    **Without optimization of registers.
    BsForcesBound=256 (? regs)
    BsForcesFluid=256 (? regs)
    BsForcesFluidCorr=256 (? regs)

    RunMode="Single-Gpu"

    Loading multiphase Constants to Constant memory

    Finish Loading multiphase Constants to Constant memory

    Allocated memory in CPU: 309420 (0.30 MB)
    Allocated memory in GPU: 1365568 (1.30 MB)
    Part_0000 3506 particles successfully stored

    [Initialising simulation (u5h3rodd) 30-09-2015 16:29:50]
    PART PartTime TotalSteps Steps Time/Seg Finish time
    ========= ============ ============ ======= ========= ===================


    it just stop here
  • Hi Alex,

    could you find the possible reason? 'Cause all other cases work well in my computer.

    Thanks!
  • Hi,

    Lazycatyi we are looking into this

    thanks for your patience

    George
  • Thank you!
  • Hi,

    We found a peculiar situation related with my MVStudio configuration.
    It was running in some machines but not in others.
    We will update the files shortly and let you know!

    Thanks for reporting the problem!

    Regards,
    George
  • Hi All,

    The issues have been resolved.
    We have updated the Package v3.2.

    Please let us know if you have any more issues,

    Happy multi-SPH_ing

    George
  • Hi George,

    Thank you for rapid update. I'm trying to use the code to deal with coastal processes with sediment. Could you email me two of your papers: "3-D SPH Modelling of Sediment Scouring Induced by Rapid Flows" and "Modelling sediment resuspension in industrial tanks using SPH"? If you have other papers that would be helpful to understand the code, could you also give me a copy?
    Thank you very much! My email is panyi21hhu@gmail.com

    Regards

    Yi
  • Hi All,

    I currently run a multi phase simulation. As I did before in v3.1 I copied my "_out"-Folder to somewhere else and created a previev (just executed the BoundaryVTK, PartVTK and Isosurface).
    This works pretty good in v3.1 but in the new version all Executables crash.

    I didn´t change so much in the ".bat"-File:
    =========================================
    @echo off

    rem "name" and "dirout" are named according to the testcase

    set name=Testcase1
    set dirout=%name%_out
    set boundaryvtk="../EXECS/BoundaryVTK_win64.exe"

    rem "executables" are renamed and called from their directory

    set gencase="../../EXECS/GenCase_win64.exe"
    set dualsphysics="../../EXECS/DualSPHysics_win64_MPhase.exe"
    set boundaryvtk="../../EXECS/BoundaryVTK_win64.exe"
    set partvtk="../../EXECS/PartVTK_win64.exe"
    set measuretool="../../EXECS/MeasureTool_win64.exe"
    set isosurface="../../EXECS/IsoSurface_win64.exe"

    rem "dirout" is created to store results or it is removed if it already exists


    %boundaryvtk% -loadvtk %dirout%/%name%_Druckplatte_Actual.vtk -filexml %dirout%/%name%.xml -savevtkdata %dirout%/BoundaryMotion

    %partvtk% -dirin %dirout% -savevtk %dirout%/PartFluid -onlymk:0 -vars:-all,+rhop,+vel,+mass,+press
    %partvtk% -dirin %dirout% -savevtk %dirout%/PartSediment -onlymk:1 -vars:-all,+rhop,+vel,+mass,+press
    if not "%ERRORLEVEL%" == "0" goto fail

    %isosurface% -dirin %dirout% -filexml %dirout%/%name%.xml -onlymk:0 -saveiso %dirout%/IsosurfaceWater -onlymk:1 -saveiso %dirout%/IsosurfaceSoil
    if not "%ERRORLEVEL%" == "0" goto fail

    :success
    echo All done
    goto end

    :fail
    echo Execution aborted.

    :end
    pause
    ===========================================

    Is it my mistake (maybe I am just to impatient ;) ) or is this a bug?

    Best regards

    Chris
  • Hi,

    Well if it all executables, then probably you went somewhere wrong,
    where is the %dualsphysics% command line in your *.bat?

    Check your script..

    Cheers,
    George


  • Hi,

    i removed it, because this *.bat is just for calculating the whole output after the simulation.

    As is said it´s just for creating a preview. So I copy the current output-Folder (and XML, CAD-Files etc.) somewhere else and run the *.bat to create all desired outputs until the current state.

    PartVTK and Isosurface are crashing both.

    EDIT: PartVTK is crashing when it tries to extract the 3D Data:

    PartVTK v1.41 (17-12-2013)
    ===========================
    Threads for parallel execution: 8
    LoadData> Einspuelschale_out/PartOut.bi2
    LoadData> Einspuelschale_out/Part0000.bi2
    LoadData> 3D data files...
  • Hi,

    Email me the *.bat file, I will take a look when I get some time, but it is very strange for your PartVTK to crash..

    :(

    Cheers,
    George
  • Hi all,
    A few questions related to DPI and the new release:
    a. is "density" and "body density" different from "PhaseRhop"? and why can't the first two be different for each fluid phase?
    b. is "PhaseVisco" the fluid dynamic viscosity?
    c. are the units SI? or is there no inherent set of units?
    Thanks!
  • Hello idaapm,

    DPI was created well before the current multi-phase release of DualSPHysics was implemented, as such it refers only to the original single phase code. Saying that, as I understand it, there have been few changes to the form of the XML that the new GenCase accepts, with the majority being added as parameters. DPI supports free editing of non-standard parameters so it should still be useful to some regard, even if just to define a geometry.

    I'll let somebody from the DualSPHysics multi-phase development team fill in the specifics though.
  • Thanks a lot for the feedback.
    Also, I've sent you a message about some issues I got while accessing the "Geometry" tab on DPI. Any idea what's wrong?
  • Hi all,

    Can anyone let me know about the possibility of generating say 1000 irregular waves in DualSPHysics. If it is possible, how long would be the computational time?
    I want to do numerical simulation on wave runup and wave overtopping on a curved dike.

    Thanks,
    Suba
  • in less than 2 weeks we will release new version of the code with automatic wave generation (regular or irregular)

    a 2D case can take hours but 3D case.... 1000 waves can take 2-3 days (on GPU)
  • Hello Alex,

    Thanks for your reply. I would really wait for the new version.
    Before that I would like to pre equip myself in DualSPHysics.
    Is there is any pre requisite before I start exploring the new version?
    Can you suggest me something in this regard.

    Thanks,
    Suba