We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An example of how we create external MPI sub-jobs from Swift/T is here:
https://bitbucket.org/mdorier/mpix_launch/src/master/example
The idea is that the child MPI app can be run on any subcommunicator from the parent MPI app.
If we could get a similar example working with Flux, it will be simple to bring that into Swift/T.
This all depends on #12 and #13 .
The text was updated successfully, but these errors were encountered:
Yes, this is excellent. I do have an Univ. of Utah collaboration who wants to try Flux+Swift/T to speed up a floating point analysis search/testing workflow (FLiT Bisect tool: see https://cacm.acm.org/magazines/2021/2/250083-keeping-science-on-keel-when-software-moves/fulltext?mobile=false).
Once we have some level of integration, I can ask the student to try this.
Sorry, something went wrong.
j-woz
No branches or pull requests
An example of how we create external MPI sub-jobs from Swift/T is here:
https://bitbucket.org/mdorier/mpix_launch/src/master/example
The idea is that the child MPI app can be run on any subcommunicator from the parent MPI app.
If we could get a similar example working with Flux, it will be simple to bring that into Swift/T.
This all depends on #12 and #13 .
The text was updated successfully, but these errors were encountered: