PHASTA/Wish List

This page is intended to be a log of useful features to add to various tools such as Phasta and NSpre. Odds are that no one will ever actually implement anything listed on this page, but if you somehow find yourself with a little extra time, it's always here.

Phasta

• Standardize the Sync IO library to work as is across Phasta and Paraview.
• Get rid of the need to know a priori how many fields will need to be written when using Sync IO
• Write interface to allow Phasta to read and write both Sync IO and Posix
• Fix bug in Sync IO to allow serial IO.
• Modify common.h (and the rest of the code) to allow implicit none.
• Convert all Fortran to a separate language (such as C or Julia)
• Cross Platform (Hey, I can dream)
• Add testing (unit and regression)
  • See FortranTestGenerator to automatically generate unit tests from the code (and it's accompanying IEEE paper).
  • Also possibly build up using libFRUIT for unit tests
• Convert all code to use blk%_ instead of it's equivalents (npro, etc.)
• Split generation of d2wall from SA code into a separate module
• Make timestep increaseable through rerun-check
  • Replace iterative do loop with while loop
• Implement style guide/formatter
  • findent for formatting and converting fixed-form to free-form (also actively maintained!)
  • fprettify is a Python derived version
• Convert to free-form Fortran
  • Most tools these days support >=F90 format, also generally just an easier format to use
  • findent will convert fixed-form to free-form (also actively maintained!)
  • Several tools listed in this webpage
• Documentation via doxygen
  • See jrwrigh/volumetric-stg-DoxygenTest branch for example. Open docs/index.html in a browser to see resulting code.
  • The compressible and incompressible should be documented with different Doxygen instances, then be linked to separately
• Review code for use of nshl vs nenl.
  • Things having to do with nodes (xl) or linear fields (dwallocalized) are nodal fields and are size nenl.
  • Other fields that would be interpolated by all of the shape functions on an element (e.g., yl, acl, ) or residuals (rl) are of size nshl.
  • Similarly, at the global level nodal/linear fields are sized numnp while things that could be higher order are nshg.
  • These maybe hidden bugs, as they won't have a problem unless you run higher order basis functions.
• Modern solver.inp file format
  • json, yaml, toml
  • Requirements are the ability to comment/uncomment data and have flexible inputs (boolean, string, array, path, etc.)
  • Code should also have a way of checking for valid inputs
• Have input file checking utility
  • Something like phasta --check-inputs to run the input file reader and check if there are any errors in the file
  • Codewise, this would need to be in front of the MPI initialization to allow for execution without mpiexec
• Replace temp (and other) arrays with equivalence statements
  • See Fortran#Equivalence Statement for more information and examples

NSpre

• Error checking to make sure that the size of the mesh contained in geom.sms is equal to the size of the mesh associated with restart.*.0.
• Ability to interpolate directly from a partitioned mesh.