-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Implementing the Vectorized (and threaded) Stokes Solver (Stokes-Vec) would result in significant simulation speed ups. There have be numerous reasons barring us from its implementation, some resolved some still unresolved.
Resolved Reasons:
.resultfile parsing:- An early attempt use
Stokes-Vecwas abandoned because it wrote it's solution vectors to.resultfiles differently, than the legacy Stokes solver.elmer2ncwas not built out to handle these differences, soStokes-Vecwas abandoned. - With the adoption of
NetcdfUGRIDOutputSolverSolver, this no longer an obstacle.NetCDFfiles with solution vectors are directly written by the.siffile so don't need to parse.resultfiles anymore.
- An early attempt use
Unresolved Reasons:
Structured Mesh Mapper:- It appears as though the
Stokes-Vecsolver does not work well with theStructured Mesh Mapper.
- It appears as though the
Metadata
Metadata
Assignees
Labels
No labels