Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools

You are here: metafor.ltas.ulg.ac.be » Commits » 2017 » Commit 2017-12-20
Trace: • Commit 2017-12-20
commit:2017:12_20

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
commit:2017:12_20 [2017/12/20 10:45] – [Added [a] / deleted [d] / modified [m] / renamed [r] files/folders] boemercommit:2017:12_20 [2018/05/04 16:47] (current) – boman
Line 1: Line 1:
-====== Commit December 20, 2017 ======+====== Commit 2017-12-20 ======
  
 In this commit, the asperity crushing simulations in the generalized plane strain state created by Carretta for the Metalub/Metafor coupling were simplified as much as possible and corrected where necessary.  The scripts of these simulations can be found in: In this commit, the asperity crushing simulations in the generalized plane strain state created by Carretta for the Metalub/Metafor coupling were simplified as much as possible and corrected where necessary.  The scripts of these simulations can be found in:
Line 22: Line 22:
  
 Notice that the rolling direction in this model is aligned with the axis $\mathbf{z}$, while the vertical axis is $\mathbf{y}$ since plane strain simulations are usually represented in the $xy$-plane.  In Metalub, the rolling direction is $\mathbf{x}$ and the vertical direction is $\mathbf{y}$ since cold rolling was first modeled in 2D.  To extend the model to 3D, even another but more general choice was made in the reference document by Boemer, i.e.  the rolling direction is $\mathbf{x}$ and the vertical axis is $\mathbf{z}$.   Notice that the rolling direction in this model is aligned with the axis $\mathbf{z}$, while the vertical axis is $\mathbf{y}$ since plane strain simulations are usually represented in the $xy$-plane.  In Metalub, the rolling direction is $\mathbf{x}$ and the vertical direction is $\mathbf{y}$ since cold rolling was first modeled in 2D.  To extend the model to 3D, even another but more general choice was made in the reference document by Boemer, i.e.  the rolling direction is $\mathbf{x}$ and the vertical axis is $\mathbf{z}$.  
 +
 +
 +===== CMakeLists.txt =====
 +
 +The following line was added in the ''IF(MSVC)'' of the main CMakeLists.txt file to enable parallel compilation even without IncrediBuild:
 +
 +  SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /MP")
  
  
Line 198: Line 205:
 Either Godunov's method or the finite volume linear reconstruction method (see [[doc:user:ale:ale|]]) can be used for the convection step with sub-stepping depending on whether ''conv'' is equal to ''godunov'' or ''benson''.  Only the pressure is convected.  More precisely, to compute the pressure, Metafor computes a pressure increment at each time step based on the bulk modulus and the volume variation of the lubricant elements.  To compute the pressure at the following time step it is therefore necessary to convect the pressure. Either Godunov's method or the finite volume linear reconstruction method (see [[doc:user:ale:ale|]]) can be used for the convection step with sub-stepping depending on whether ''conv'' is equal to ''godunov'' or ''benson''.  Only the pressure is convected.  More precisely, to compute the pressure, Metafor computes a pressure increment at each time step based on the bulk modulus and the volume variation of the lubricant elements.  To compute the pressure at the following time step it is therefore necessary to convect the pressure.
  
-According to Carretta, the velocities and accelerations were not convected because they made the convergence more difficult.+According to Carretta, the velocities and accelerations were not convected because they made the convergence more difficult/impossible.
  
 :?: ** Why is only the convection of the pressure sufficient?  Is this sufficient to model the creation of a pressure gradient due to a convergent effect? I am not sure, if it is a good idea to not convect the velocities and accelerations since they are at the cause of creating pressure gradients, which might lead to the microhydrodynamism. ** :?: ** Why is only the convection of the pressure sufficient?  Is this sufficient to model the creation of a pressure gradient due to a convergent effect? I am not sure, if it is a good idea to not convect the velocities and accelerations since they are at the cause of creating pressure gradients, which might lead to the microhydrodynamism. **
Line 341: Line 348:
  
  
-===== Added [a] / deleted [d] / modified [m] / renamed [r] files/folders ======+===== Added [a] / deleted [d] / modified [m] / renamed [r] general files/folders ======
  
 <code> <code>
Line 387: Line 394:
  
 <code> <code>
-[m] aspCrushing/tests/threeD/triangle.py +[m] aspCrushing/tests/twoDhalf/reelDry.py 
-aspCrushing/tests/twoDhalf/bc +[r] aspCrushing/tests/twoDhalf/splineDry.py 
-aspCrushing/tests/twoDhalf/bc/res_bc_ht.ascii +[m] aspCrushing/tests/twoDhalf/reelDry.tsc 
-aspCrushing/tests/twoDhalf/bc/res_bc_lx.ascii +[r] aspCrushing/tests/twoDhalf/splineDry.tsc 
-aspCrushing/tests/twoDhalf/bc/res_bc_lx_lub.ascii + 
-aspCrushing/tests/twoDhalf/bc/res_bc_lxx.ascii +[m] aspCrushing/tests/twoDhalf/reelLub.py 
-aspCrushing/tests/twoDhalf/bc/res_bc_lxx_lub.ascii +[r] aspCrushing/tests/twoDhalf/splineLub.py 
-aspCrushing/tests/twoDhalf/bc/res_bc_p.ascii +[m] aspCrushing/tests/twoDhalf/reelLub.tsc 
-aspCrushing/tests/twoDhalf/bc/res_bc_pb_rey.ascii +[r] aspCrushing/tests/twoDhalf/splineLub.tsc 
-aspCrushing/tests/twoDhalf/bc/res_bc_pi.ascii + 
-aspCrushing/tests/twoDhalf/bc/res_bc_pl.ascii +[m] aspCrushing/tests/twoDhalf/triang1Dry.py 
-aspCrushing/tests/twoDhalf/bc/res_bc_x.ascii +[r] aspCrushing/tests/twoDhalf/triangle1Dry.py 
-aspCrushing/tests/twoDhalf/bCond +[m] aspCrushing/tests/twoDhalf/triang1Dry.tsc 
-aspCrushing/tests/twoDhalf/bCond/res_bc_ht.ascii +[r] aspCrushing/tests/twoDhalf/triangle1Dry.tsc 
-aspCrushing/tests/twoDhalf/bCond/res_bc_lxx.ascii + 
-aspCrushing/tests/twoDhalf/bCond/res_bc_lxx_lub.ascii +[m] aspCrushing/tests/twoDhalf/triang1Lub.py 
-aspCrushing/tests/twoDhalf/bCond/res_bc_p.ascii +[r] aspCrushing/tests/twoDhalf/triangle1Lub.py 
-aspCrushing/tests/twoDhalf/bCond/res_bc_pb_rey.ascii +[m] aspCrushing/tests/twoDhalf/triang1Lub.tsc 
-aspCrushing/tests/twoDhalf/bCond/res_bc_x.ascii +[r] aspCrushing/tests/twoDhalf/triangle1Lub.tsc 
-aspCrushing/tests/twoDhalf/reelDry.py + 
-aspCrushing/tests/twoDhalf/reelDry.tsc +[m] aspCrushing/tests/twoDhalf/triang2Dry.py 
-aspCrushing/tests/twoDhalf/reelLub.py +[r] aspCrushing/tests/twoDhalf/triangle2Dry.py 
-aspCrushing/tests/twoDhalf/reelLub.tsc +[m] aspCrushing/tests/twoDhalf/triang2Dry.tsc 
-aspCrushing/tests/twoDhalf/splineDry.py +[r] aspCrushing/tests/twoDhalf/triangle2Dry.tsc 
-aspCrushing/tests/twoDhalf/splineDry.tsc + 
-aspCrushing/tests/twoDhalf/splineLub.py +[m] aspCrushing/tests/twoDhalf/triang2Lub.py 
-aspCrushing/tests/twoDhalf/splineLub.tsc +[r] aspCrushing/tests/twoDhalf/triangle2Lub.py 
-aspCrushing/tests/twoDhalf/triang1Dry.py +[m] aspCrushing/tests/twoDhalf/triang2Lub.tsc 
-aspCrushing/tests/twoDhalf/triang1Dry.tsc +[r] aspCrushing/tests/twoDhalf/triangle2Lub.tsc
-aspCrushing/tests/twoDhalf/triang1Lub.py +
-aspCrushing/tests/twoDhalf/triang1Lub.tsc +
-aspCrushing/tests/twoDhalf/triang2Dry.py +
-aspCrushing/tests/twoDhalf/triang2Dry.tsc +
-aspCrushing/tests/twoDhalf/triang2Lub.py +
-aspCrushing/tests/twoDhalf/triang2Lub.tsc +
-aspCrushing/tests/twoDhalf/triangle1Dry.py +
-aspCrushing/tests/twoDhalf/triangle1Dry.tsc +
-aspCrushing/tests/twoDhalf/triangle1Lub.py +
-aspCrushing/tests/twoDhalf/triangle1Lub.tsc +
-aspCrushing/tests/twoDhalf/triangle2Dry.py +
-aspCrushing/tests/twoDhalf/triangle2Dry.tsc +
-aspCrushing/tests/twoDhalf/triangle2Lub.py +
-aspCrushing/tests/twoDhalf/triangle2Lub.tsc +
-aspCrushing/tools/python/aspCrush.py +
-aspCrushing/tools/python/aspExtr.py +
-aspCrushing/tools/python/aspExtractors.py +
-aspCrushing/tools/python/bCondPb.py +
-aspCrushing/tools/python/evolutionFunction.py +
-aspCrushing/tools/python/geoSpline.py +
-aspCrushing/tools/python/geoTriang.py +
-aspCrushing/tools/python/geoTriangle1.py +
-aspCrushing/tools/python/geoTriangle2.py +
-aspCrushing/tools/python/geoTwoAsp.py +
-aspCrushing/tools/python/rollingAsp.py +
-aspCrushing/tools/python/Vector.py +
-CMakeLists.txt+
 </code> </code>
  
  
- --- //[[gwautelet@ulg.ac.be|gaëtan]] 2017/12/17 12:00//+ --- // [[dominik.boemer@uliege.be|Dominik Boemer]] 2017/12/20 11:30 //
commit/2017/12_20.1513763149.txt.gz · Last modified: by boemer
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki