common compiling environments
Users within the HPCMP are increasingly making use of multiple HPC systems at multiple centers for processing and code development. When using systems of the same architecture at different centers, developers of application codes could more efficiently distribute their workload if those systems were to maintain the same default compiling environment versions.
This policy addresses the need for commonality with the following requirements:
Compiling environment modules created by a center shall follow the naming and location conventions described in BC policy FY11-04 entitled "Common Modules Environment" unless prohibited by requirements of the system vendor.
Due to local operational and contractual commitments, centers may install new compiling environments and new versions of existing compiling environments at any time. However, neither the default environment nor the default version of an environment for a given architecture shall change until all systems of that type are ready for the change. The change in environment will be initiated by and coordinated through the HPCMP Enterprise Configuration Management process.
On occasion, emergency operational or security requirements may require centers to make changes to the compiling environment without advance coordination. Once the emergency situation has been mitigated, resynchronization of the default compiling environment(s) will take place using the process described in this policy.
The appearance of hyperlinks does not constitute endorsement by the U.S. Air Force of this website or the information, products, or services contained therein. For other than authorized activities such as military exchanges and morale, welfare and recreation sites, the U.S. Air Force does not exercise any editorial control over the information you may find at these locations. Such links are provided consistent with the stated purpose of this DoD website.