Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T TurTLE
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TurTLE
  • TurTLE
  • Issues
  • #11

Closed
Open
Created May 02, 2017 by Cristian Lalescu@clalescuMaintainer

simplified wrapper

Generating code piece by piece from the Python wrapper is not easy to deal with the first time you see it done. I think I should write a cleaner version of the wrapper. I'm doing this in branch feature/new-wrapper. In the interest of cleaner code to discuss/diagnose/optimise during the scaling workshop (issue #10 (closed)), I may need to do this sooner rather than later.

Broadly speaking:

  1. write an abstract class "direct_numerical_simulation", which will contain all the code that's currently written as strings in "_code.py".
  2. write children of "direct_numerical_simulation" that will contain the code written as strings in "_fluid_solver.py" and "NSVorticityEquation.py".
  3. write minimal child of "_code.py", which will generate a small main file, initial conditions and hdf5 stats datasets, and then compile and launch.
Assignee
Assign to
Time tracking