Issue 88: flow calling flow - #89
Merged
Merged
Conversation
dylanmcreynolds
approved these changes
Oct 7, 2025
davramov
marked this pull request as ready for review
October 7, 2025 16:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Addressing #88
For 8.3.2, I am rewriting
dispatcher.pyandmove.pymove.py:process_new_832_file_flow()is now a wrapper forProcess_new_832_file_task(), which contains the movement and scicat ingestion logic.dispatcher.py: thedispatcher()flow now is named after the file name, and calls process_new_832_file_task directly, followed by the asynchronous calls to alcf/nersc for reconstruction.Hopefully, this makes it clearer when inspecting a dispatcher flow, and still allows us to run sub-tasks as flows directly if needed.