OGSModel-class
1 unresolved thread
1 unresolved thread
ToDos:
- Tests
- Usage of OGSMesh-class
-
OGSModel.from_feflow()
-method - return value
run_model
sim_result = model.run_model(logfile=f"{out_dir}/out.txt", args=f"-o {out_dir} -m .")
ms = ot.MeshSeries(sim_result)
Edited by Tobias Meisel
Merge request reports
Activity
Filter activity
added Infrastructure workflowin development labels
requested review from @FZill and @TobiasMeisel
removed Infrastructure label
added API label
- ogstools/ogs_model/ogs_model.py 0 → 100644
1 # Copyright (c) 2012-2024, OpenGeoSys Community (http://www.opengeosys.org) 2 # Distributed under a Modified BSD License. 3 # See accompanying file LICENSE.txt or 4 # http://www.opengeosys.org/project/license 5 # 6 7 8 from collections import defaultdict 9 from pathlib import Path 10 11 import pyvista as pv 12 13 from ogstools import Mesh changed this line in version 2 of the diff
- Resolved by Julian Heinze
How do we distinguish between boundary meshes and meshes used i.e. for source terms which don't need to be boundaries. I think it wouldn't be practical to stored them in a separate attribute, so maybe we rename boundary_meshes to subdomain_meshes which covers all submeshes?
added 72 commits
-
c06145ec...6f07be18 - 71 commits from branch
main
- 67e458b1 - introduce OGSModel-class
-
c06145ec...6f07be18 - 71 commits from branch
added 11 commits
-
67e458b1...b7e6e4cc - 10 commits from branch
main
- 07abcd51 - introduce OGSModel-class
-
67e458b1...b7e6e4cc - 10 commits from branch
changed milestone to %0.5.1 Release
added 29 commits
-
07abcd51...ba922e82 - 25 commits from branch
main
- 77234ce2 - introduce OGSModel-class
- 64c6390f - add methods to work with FEFLOW data
- 1027045b - FeflowModel inheritates from OGSModel
- 33f4041a - test for ogs_model
Toggle commit list-
07abcd51...ba922e82 - 25 commits from branch
mentioned in merge request ogs/ogs!5217 (merged)
Please register or sign in to reply