You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been maintaining a collection of parflow builds on ocelote as modules, but its been relatively ad-hoc and not automated or documented.
For future user (primarily Laura and her students), I think it would be useful to have better process for this.
At a minimum, documentation can be written that clearly describes how to build parflow from scratch, and how to make it into a module for general use.
Alternatively (an this is more preferred in my mind) a python/bash tool could be written which takes a configuration file listing source and configurations for parflow and other libraries.
I already have a number of the build processes automated in some form (as bash scripts)
Alternatively, we might look into spack which is a package manager for super-computers and might be useful here.
They might even already have a parflow module.
Deliverables:
Documentation about building parflow and libraries
Documentation about creating a parflow module (and best practices)
(Maybe) a tool accepting a configuration file for parflow and libraries and
Done when:
Laura/Michelle can build, modularize, and run (using PBS, which is where this is most useful) a reasonably arbitrary version and configuration of parflow.
Activity