Add df regions to their own files and only edges to the po file #652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Properly serialize the different df regions when spec preprocessing and only add the edges to the po file.
Use by running the following when in
$PASH_TOP
.The
partial_order.txt
file will look like this:where the path is the directory that stores different df regions. For example, region
0
is stored in/tmp/pash_BYmDfbB//speculative/partial_order/0
for that particular example. Furthermore, the arrows show the partial order of df_regions in the original file (for now it is always a sequence, but it can be extended to be a partial order.TODO: The next step is to add a proper entry point in PaSh that will wait for the scheduler at each runtime invocation. The new entry point should be invoked by a wrapper around PaSh that will first run the scheduler and initialize some environment variables, and then call PaSh.