proteus
proteus copied to clipboard
A computational methods and simulation toolkit
When I use an anaconda python 2 environment, I have the issue where the proteus build does not create the linux directory as its build destination, but rather overwrites the...
Problem mentioned in issue #1056. The TwoPhaseFlow/dambreak_solver_options test fails via the hashdist build but not via the conda build. ``` =================================== FAILURES =================================== [31m[1m________________ TestTwoPhaseFlow.test_damBreak_solver_options _________________[0m [gw0] linux -- Python...
So right now, the "new" documentation is on a separate repository (proteus-doc), and the process to push documentation is not automatic at all. There are 3 ways to do it:...
- [ ] rewrite parun as pro using argparse - [ ] replace app option as subcommand and move over app-specific options to subcommand - [ ] split off some...
There used to be an interface to Triangle in `proteus/TriangleTools.py` (see https://proteustoolkit.org/api/proteus.TriangleTools.html). The file is not present in master. Is it not supported any more?
I'm trying to build Proteus for conda-forge: https://github.com/conda-forge/staged-recipes/pull/9942 I am running into several problems. To start with, do you recommend taking the latest release of Proteus (1.7.0)?
**Tests to add for proteus.mbd (FSI):** - [ ] moments/forces retrieved from NS (update barycenters directly in RANS2P/RANS3P or check that moment calculations are right) - [ ] added-mass matrix...
/home/travis/build/erdc/proteus/proteus/mprans/GN_SW2DCV.py:389: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (self.model.boundaryIndex is None and self.model.normalx is not None, /home/travis/build/erdc/proteus/proteus/mprans/SW2DCV.py:350: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert (self.model.boundaryIndex is...
When using ALE mesh, it seems that the free surface gets disturbed, particularly on the first few steps of moving the mesh. This can be particularly obvious when using MoveMeshMonitor...
If we start a simulation with these initial conditions (sediment with black in the air phase - red is air, blue is water) then at the third checkpoint (icnluding zero)...