Nektar merge requestshttps://gitlab.nektar.info/nektar/nektar/-/merge_requests2021-04-15T07:11:53Zhttps://gitlab.nektar.info/nektar/nektar/-/merge_requests/1241Adding SolverUtils as a core library built by default with other core libs2021-04-15T07:11:53ZJeremy CohenAdding SolverUtils as a core library built by default with other core libsv5.0.2https://gitlab.nektar.info/nektar/nektar/-/merge_requests/1236Update build config to build SolverUtils by default when not building solvers...2021-04-09T17:59:35ZJeremy CohenUpdate build config to build SolverUtils by default when not building solvers (fixes #259)This update modifies the build system to build the `SolverUtils` library by default when `NEKTAR_BUILD_SOLVERS=OFF`.
A new dependent option has been added - `NEKTAR_BUILD_SOLVERUTILS`. I `NEKTAR_BUILD_SOLVERS=OFF`, you can also set `NEK...This update modifies the build system to build the `SolverUtils` library by default when `NEKTAR_BUILD_SOLVERS=OFF`.
A new dependent option has been added - `NEKTAR_BUILD_SOLVERUTILS`. I `NEKTAR_BUILD_SOLVERS=OFF`, you can also set `NEKTAR_BUILD_SOLVERUTILS=OFF` if you don't want to build the SolverUtils library. As a dependent option, setting contradictory option values - i.e. `NEKTAR_BUILD_SOLVERUTILS=OFF` `NEKTAR_BUILD_SOLVERS=ON` - results in the solvers AND the `SolverUtils` library being built.
Fixes #259.v5.0.2https://gitlab.nektar.info/nektar/nektar/-/merge_requests/1231WIP: Feature/wall normal data single point2021-03-21T01:29:08ZGanlinWIP: Feature/wall normal data single pointGet the boundary layer data at a input point on the boundaryGet the boundary layer data at a input point on the boundaryv5.0.2Dave MoxeySpencer SherwinAnkang Gaoankanggao@ustc.edu.cnDave Moxeyhttps://gitlab.nektar.info/nektar/nektar/-/merge_requests/1169WIP: fix stuck in GlobalSolve2021-03-14T02:39:06ZAnkang Gaoankanggao@ustc.edu.cnWIP: fix stuck in GlobalSolveWhen one or more processes in parallel consists entirely of Dirichlet boundary points and therefore has no DOFs to solve for, the call `LinSys->Solve(locrhs,inout,m_locToGloMap,dirForcing);` is not currently called on that process, causi...When one or more processes in parallel consists entirely of Dirichlet boundary points and therefore has no DOFs to solve for, the call `LinSys->Solve(locrhs,inout,m_locToGloMap,dirForcing);` is not currently called on that process, causing deadlock as some processes then do not participate in broadcast calls.
Fixes #236.v5.0.2Chris CantwellChris Cantwellhttps://gitlab.nektar.info/nektar/nektar/-/merge_requests/1148Fix/mesh graph multi domain2020-09-16T09:43:12ZCharles HoustonFix/mesh graph multi domainWrites composites into separate domains in XML for multi-domain simulations.
Adds map storage (and getter) for domains to keep IDs consistent in multi-domain parallel simulations.Writes composites into separate domains in XML for multi-domain simulations.
Adds map storage (and getter) for domains to keep IDs consistent in multi-domain parallel simulations.v5.0.2Chris CantwellChris Cantwell