Skip to content

Simulation pipeline requires an overarching point of entry #47

Open

Description

@cerebis

Since parts of the sweep had to be split into separate SCons scripts, it has lead to only weak coupling of inter-script dependencies. At present this dependency hierarchy is managed manually -- running each stage in the correct order once the last one finishes. It highlights the need for something.

A overlord script is required, which performs the stages and would naturally take on the "whole simulation" output path and other variables such as seed. This script it itself could use Nestly -- but I would be tentative to do so as the goal isn't Application Inception. :-) Also, it would be a good time to yank out all the bash scripting.

Activity

  1. cerebis commented on Nov 14, 2015

    @cerebis
    CollaboratorAuthor

    SCons provides hierarchical builds. We would need to remove use of variables supplied as arguments in subscripts and pass them as SCons env's.

    An abstraction layer for queue submission would obviously need to be considered, when refactoring what information is need by lower level stages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions