Repository 'package_atlas_3_10'
hg clone https://testtoolshed.g2.bx.psu.edu/repos/iuc/package_atlas_3_10

Changeset 1:3508de0ebae1 (2013-09-12)
Previous changeset 0:2f75622926c5 (2013-07-08) Next changeset 2:d32504e1aea8 (2013-09-20)
Commit message:
Uploaded
modified:
tool_dependencies.xml
b
diff -r 2f75622926c5 -r 3508de0ebae1 tool_dependencies.xml
--- a/tool_dependencies.xml Mon Jul 08 10:11:28 2013 -0400
+++ b/tool_dependencies.xml Thu Sep 12 07:07:57 2013 -0400
b
@@ -3,15 +3,20 @@
         <install version="1.0">
             <actions>
                 <!-- first action is always downloading -->
+                <!--<action type="download_by_url" target_filename="ATLAS.tar.bz2">http://downloads.sourceforge.net/project/math-atlas/Stable/3.10.1/atlas3.10.1.tar.bz2</action>-->
                 <action type="download_file">http://downloads.sourceforge.net/project/math-atlas/Stable/3.10.1/atlas3.10.1.tar.bz2</action>
                 <action type="shell_command">tar xfvj atlas3.10.1.tar.bz2</action>
                 <action type="download_file">http://www.netlib.org/lapack/lapack-3.4.2.tgz</action>
 
                 <action type="shell_command">
+                # try to disable cpu throttling
                 if hash cpufreq-selector 2>/dev/null; then
                     cpufreq-selector -g performance
+                elif hash cpupower 2>/dev/null; then
+                    cpupower frequency-set -g performance
                 else
                     echo 'Please deactivate CPU throttling by your own, or install cpufreq-selector'
+                    exit
                 fi
                 </action>
                 <action type="shell_command">
@@ -30,7 +35,7 @@
                 </action>
             </actions>
         </install>
-        <readme>ATLAS_LIB_DIR and ATLAS_INCLUDE_DIR will be set (including libatlas.a).
+        <readme>ATLAS_LIB_DIR and ATLAS_INCLUDE_DIR (including libatlas.a) will be exported for later use.
         During ATLAS library compilation, ATLAS performs code efficiency checks. These checks can only provide optimal results, if "frequency scaling" is disabled on the CPU, and no other load-intense processes are running. 
         Ideally, you should compile on an empty cluster node with CPU frequency scaling disabled (see "cpufreq-selector" or "cpufreq-set").
         </readme>