Automated for use with the supercomputer. #2
Conversation
This file contains 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
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.
This branch was developed because of the following issue: differences in architecture on different nodes of the supercomputer requires the FMM C++ code to be compiled on the node in question. This becomes annoying when attempting to run jobs with sbatch, as the user does not always know which node with the desired memory requirements will be next available.
A build_tmp.sh script is provided that allows the user to build FLOWExaFMM and store the shared library with a random tag, making it possible to rebuild FLOWExaFMM many times for running jobs and various nodes simultaneously. If the environment variable FMM is set, FLOWExaFMM uses the shared library at the path specified by FMM. Otherwise, it defaults to the old behavior.