<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic We also tested the following in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096929#M15840</link>
    <description>&lt;P&gt;We also tested the following version without success:&lt;/P&gt;

&lt;P&gt;Update 1 (build 486553)&lt;/P&gt;</description>
    <pubDate>Thu, 10 Nov 2016 10:46:42 GMT</pubDate>
    <dc:creator>hlrs</dc:creator>
    <dc:date>2016-11-10T10:46:42Z</dc:date>
    <item>
      <title>Feature Request: collector should recognize Cray MPI with ALPS_APP_PE env var</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096918#M15829</link>
      <description>&lt;P&gt;Kevin,&lt;/P&gt;

&lt;P&gt;Cray MPI on their XC systems sets env var ALPS_APP_PE to the rank, unique for each rank, from 0 to N-1 for N ranks.&amp;nbsp; They do not use the same env vars as MPICH, Intel MPI or OpenMPI to pass rank information down to applications.&lt;/P&gt;

&lt;P&gt;advixe-cl run under MPI needs to open a results dir for each rank.&amp;nbsp; I believe it is looking at MPICH, iMPI and OpenMPI env vars to find the rank number to use for the results directories.&amp;nbsp; I am pretty sure it is not looking for Cray's env var ALPS_APP_PE.&amp;nbsp; What I'm seeing is if I launch a Cray MPI job thusly:&lt;/P&gt;

&lt;P&gt;aprun -n 1 advixe-cl --results-dir=/foodir ./a.out&amp;nbsp; this works.&amp;nbsp; When I run more than 1 rank I get a file open error on the results dir.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;As background, Vtune used to have this problem also.&amp;nbsp; They modified their collector to look for an MPI job's rank via the env vars of MPICH, OpenMPI and Cray's ALPS_APP_PE.&amp;nbsp; I think advixe-cl needs this similar mod, to look for env var ALPS_APP_PE to flag an MPI job and to fetch the rank to use in the results dir name.&lt;/P&gt;

&lt;P&gt;Could you confirm that the collector is not looking for ALPS_APP_PE to indicate an MPI job and to fetch the rank? If not, consider this a feature request to get advixe-cl to work under Cray's ALP MPI environment.&lt;/P&gt;

&lt;P&gt;As a workaround, I aprun a wrapper script that launces multiple collectors with results dir set to &amp;lt;results dir&amp;gt;.$ALP_APP_PE.&amp;nbsp; This works around the issue.&lt;/P&gt;

&lt;P&gt;thanks&lt;/P&gt;

&lt;P&gt;Ron&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2016 17:55:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096918#M15829</guid>
      <dc:creator>Ronald_G_2</dc:creator>
      <dc:date>2016-09-29T17:55:29Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096919#M15830</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thanks Ron!&lt;/P&gt;

&lt;P&gt;I'll file a feature request!&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2016 17:58:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096919#M15830</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2016-09-29T17:58:11Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096920#M15831</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Hi Ron,&lt;/P&gt;

&lt;P&gt;I can confirm the behavior you mention. I have filed a feature request.&lt;/P&gt;

&lt;P&gt;The development mentioned that the Advisor -trace-mpi command-line option is a workaround.&lt;/P&gt;

&lt;P&gt;Can you try this?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2016 20:35:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096920#M15831</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2016-09-29T20:35:33Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096921#M15832</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Hi Ron,&lt;/P&gt;

&lt;P&gt;We wanted to verify that the -trace-mpi was sufficient for your requirements..&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 14:51:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096921#M15832</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2016-09-30T14:51:02Z</dc:date>
    </item>
    <item>
      <title>I'll go try it ... give me an</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096922#M15833</link>
      <description>&lt;P&gt;I'll go try it ... give me an hour.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 16:23:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096922#M15833</guid>
      <dc:creator>Ronald_G_2</dc:creator>
      <dc:date>2016-09-30T16:23:00Z</dc:date>
    </item>
    <item>
      <title>well, mixed results.  The</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096923#M15834</link>
      <description>&lt;P&gt;well, mixed results.&amp;nbsp; The -trace-mpi does indeed help - we now get results dirs and files with &amp;lt;node&amp;gt;.&amp;lt;rank&amp;gt; names.&amp;nbsp; However, the results files are empty - the .aux files are only like 46 bytes.&amp;nbsp; We run thusly:&lt;/P&gt;

&lt;P&gt;aprun -n 60 -N 30 -S 15 -j 1 advixe-cl -trace-mpi -collect survey -search-dir=all:r=$PWD -project-dir $SCRATCH/cice/advisor/haswell/intel-p4-60pe -- ./cice&lt;/P&gt;

&lt;P&gt;this runs a 60 MPI rank job on 2 nodes of haswell, 30 ranks per node, 15 ranks per socket, 1st hypercontext (not using hyperthreads).&amp;nbsp;&lt;/P&gt;

&lt;P&gt;The attached is STDOUT output from this run.&amp;nbsp; Note all the "collection stopped" messages.&amp;nbsp; The run actually ran for a minute or 2 with correct program output and results.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Also, re-ran this problem on 1 node with 20 ranks, 10 per socket.&amp;nbsp; Same, the .aux files are just 46 bytes, and the GUI shows no user code and runtime of 0.02s.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;The code is compiled with Intel Fortran 16.0.3 AND 17.0.0 with -g -qopt-report=5.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Any idea why "collection stopped" happens?&amp;nbsp; The Cray compute nodes run a streamlined SLES OS, not quite a micro kernel but if the collectors are trying to coordinate via memory mapped files or RPC then we may have some issue.&lt;/P&gt;

&lt;P&gt;Ron&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 19:37:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096923#M15834</guid>
      <dc:creator>Ronald_G_2</dc:creator>
      <dc:date>2016-09-30T19:37:07Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096924#M15835</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Let me discuss with our development team.&lt;/P&gt;

&lt;P&gt;Can you share the project directory (including the result dirs.)?&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 19:44:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096924#M15835</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2016-09-30T19:44:38Z</dc:date>
    </item>
    <item>
      <title> </title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096925#M15836</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Hi Ron,&lt;/P&gt;

&lt;P&gt;VTune and Advisor should work on Cray compute nodes.&lt;/P&gt;

&lt;P&gt;Can you confirm this is all being run on the Lustre file system?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2016 13:44:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096925#M15836</guid>
      <dc:creator>Kevin_O_Intel1</dc:creator>
      <dc:date>2016-10-03T13:44:59Z</dc:date>
    </item>
    <item>
      <title>Yes, we are running the</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096926#M15837</link>
      <description>&lt;P&gt;Yes, we are running the binary and storing results on Lustre.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I'm working on getting you project dir and results dir.&lt;/P&gt;

&lt;P&gt;Ron&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2016 17:25:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096926#M15837</guid>
      <dc:creator>Ronald_G_2</dc:creator>
      <dc:date>2016-10-04T17:25:34Z</dc:date>
    </item>
    <item>
      <title>We've been able to run an MPI</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096927#M15838</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size: 1em;"&gt;We've been able to run an MPI analysis on a Cray XC environment. &amp;nbsp;I'll capture the details in a KB article on IDZ later.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;BUT &amp;nbsp;-trace-mpi is NOT SUFFICIENT to collect data on an Cray system. &amp;nbsp;As I said, Cray's MPI sets env var ALPS_APP_PE to each rank numbered 0 to N-1. &amp;nbsp;It does NOT set PMI_RANK. &amp;nbsp;Without explicitly setting PMI_RANK to ALPS_APP_PE in a wrapper script the correct directories are not set up by the collection - specifically the "rank.&amp;lt;n&amp;gt;/rank.&amp;lt;n&amp;gt;.advixeexp files are NOT created if PMI_RANK is not set. &amp;nbsp;This proves that -trace-mpi is NOT sufficient.&lt;/P&gt;

&lt;P&gt;Observe: the first experiment I run a simple MPI pi.c with 4 ranks. &amp;nbsp;In this case I do NOT set PMI_RANK in the wrapper. &amp;nbsp;Here is the wrapper and run command and the resulting directories attached in file 'wrapper-no-pmt-rank-set.txt'. &amp;nbsp;Note there are NO rank.&amp;lt;n&amp;gt;/rank.&amp;lt;n&amp;gt;.advixeexp files created.&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;green/collectorbug&amp;gt; more runit.sh&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;# --- script needed to lauch collector on Cray XC cluster ---&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;# --- we do NOT set PMI_RANK or PMI_PE, only ALPS_APP_PE is set to rank --&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;# export PMI_RANK=${ALPS_APP_PE}&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;# export PMI_PE=${ALPS_APP_PE}&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;export PMI_NO_FORK=1&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;advixe-cl --collect survey -trace-mpi --project-dir ./adviproj --search-dir all:r=/lustre/ttscratch1/green/collectorbug -- ./cpi&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo; min-height: 18px;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;Here is the job launch&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;aprun -n 4 -N 4 -j1 -d1 -cc depth advixe-cl --collect survey -trace-mpi --project-dir /lustre/ttscratch1/green/collectorbug/adviproj --search-dir all:r=/lustre/ttscratch1/green/collectorbug -- bash runit.sh&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo; min-height: 18px;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;the directories created are missing "rank" designation.&amp;nbsp; Advisor can't open this collection&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;find adviproj -type f -exec ls -l {} \; &amp;gt;&amp;amp; wrapper-no-pmi-rank-set.txt&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;Now, rerun this run but uncomment out the line and set PMI_RANK thusly:&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;green/collectorbug&amp;gt; more runit.sh&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;export PMI_RANK=${ALPS_APP_PE}&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;# export PMI_PE=${ALPS_APP_PE}&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;export PMI_NO_FORK=1&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;advixe-cl --collect survey -trace-mpi --project-dir ./adviproj --search-dir all:r=/lustre/ttscratch1/green/collectorbug -- ./cpi&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;and look at the file created via find:&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;aprun -n 4 -N 4 -j1 -d1 -cc depth advixe-cl --collect survey -trace-mpi --project-dir /lustre/ttscratch1/green/collectorbug/adviproj --search-dir all:r=/lustre/ttscratch1/green/collectorbug -- bash runit.sh&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo; min-height: 18px;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&lt;SPAN style="font-variant-ligatures: no-common-ligatures"&gt;find adviproj -type f -exec ls -l {} \; &amp;gt;&amp;amp; wrapper-with-pmi-rank-set.txt&lt;/SPAN&gt;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;Observe that the correct "rank" files are created in this case and Advisor GUI can view the collected data.&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;I would consider this a bug - the collector should be able to get the rank in a Cray MPI environment if it merely looks for ALPS_APP_PE instead of PMI_RANK. &amp;nbsp;Seems simple enough, especially since I clued it in by using -trace-mpi. &amp;nbsp;This is would help a lot of us trying to use Advisor XE on Cray XC systems.&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;Ron&lt;/P&gt;

&lt;P style="margin-bottom: 0px; font-size: 15px; line-height: normal; font-family: Menlo;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Oct 2016 21:05:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096927#M15838</guid>
      <dc:creator>Ronald_G_2</dc:creator>
      <dc:date>2016-10-13T21:05:19Z</dc:date>
    </item>
    <item>
      <title>We also have problems with</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096928#M15839</link>
      <description>&lt;P&gt;We also have problems with the intel advisor on our CRAY XC40.&lt;/P&gt;

&lt;P&gt;We use now the following wrapper script to perform the survey collection through&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;aprun_opt="-n $n -N $N -j2 -d $[ $T * 2 ] -cc numa_node"
aprun $aprun_opt ./advixe-cl_survey.sh ${workdir} ${BIN}
&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;#####
#advixe-cl_survey.sh $1 source path $2 Binary
#####
#!/bin/bash
export PMI_RANK=${ALPS_APP_PE}
export PMI_NO_FORK=1
#export PMI_NO_PREINITIALIZE=1 # not required for survey

advixe-cl -collect survey -trace-mpi --no-auto-finalize -flops-and-masks -project-dir ./advisor -search-dir src:r=$1 $2 ./input.par &amp;gt; output.log.survey&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;This works for MPI and OpenMP applications for us. The only point is, that we are not able to get any Flops and bandwith reports with the Haswell CPUs. If I remember right, with another clustre and Haswell CPUs this worked, but I have to check this again.&lt;/P&gt;

&lt;P&gt;But when we want to collect the&amp;nbsp; trip count data, we get the following error message:&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;Mon Nov&amp;nbsp; 7 14:58:01 2016: [PE_0]:_pmi_alps_sync:alps response not OKAY&lt;BR /&gt;
	Mon Nov&amp;nbsp; 7 14:58:01 2016: [PE_0]:_pmi_init:_pmi_alps_sync failed -1&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;advixe: Warning: The application returned a non-zero exit value.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;We were able to fix this problem with export PMI_NO_PREINITIALIZE=1 so that our advixe-cl_tripcounts.sh wrapper is:&lt;/P&gt;

&lt;PRE class="brush:bash;"&gt;######
#advixe-cl_tripcounts.sh $1 source path $2 Binary
######
#!/bin/bash

export PMI_RANK=${ALPS_APP_PE}
export PMI_NO_FORK=1
export PMI_NO_PREINITIALIZE=1

export PMI_MMAP_SYNC_WAIT_TIME=300 #We have to check if this is really required

advixe-cl -collect tripcounts -trace-mpi --no-auto-finalize -project-dir ./advisor -search-dir src:r=$1 $2 ./input.par &amp;gt; output.log.tripcounts

&lt;/PRE&gt;

&lt;P&gt;The problem is, that we still get the following warning/error:&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;advixe: Warning: The application returned a non-zero exit value.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;I have also checked with the following hello world, if it is a problem with the application or advixe-cl.&lt;/P&gt;

&lt;PRE class="brush:fortran;"&gt;PROGRAM HELLO

 INTEGER NTHREADS, TID, OMP_GET_NUM_THREADS, OMP_GET_THREAD_NUM

!C Fork a team of threads giving them their own copies of variables
!$OMP PARALLEL PRIVATE(NTHREADS, TID)


!C Obtain thread number
 TID = OMP_GET_THREAD_NUM()
 PRINT *, 'Hello World from thread = ', TID

!C Only master thread does this
 IF (TID .EQ. 0) THEN
  NTHREADS = OMP_GET_NUM_THREADS()
 PRINT *, 'Number of threads = ', NTHREADS
 END IF

!C All threads join master thread and disband
!$OMP END PARALLEL

END

Again the survey work fine, but the tripcounts does not work. In the interactive mode we get the following extended output:
&lt;/PRE&gt;

&lt;PRE class="brush:bash;"&gt;aprun -n 1 advixe-cl --collect tripcounts --no-auto-finalize -project-dir ./advisor -search-dir all:r=./ -- ./hw_advisor_test
Intel(R) Advisor Command Line Tool
Copyright (C) 2009-2016 Intel Corporation. All rights reserved.
advixe: Error: Internal error. Please contact Intel customer support team.
advixe: Error: Analysis terminated abnormally.
advixe: Error: An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the Intel customer support team.
advixe: Warning: The application returned a non-zero exit value.
Application 5827006 resources: utime ~0s, stime ~1s, Rss ~52160, inblocks ~11650, outblocks ~3178&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Iused the following environment:&lt;/P&gt;

&lt;P&gt;PrgEnv-intel/5.2.82 (ifort version 16.0.3)&lt;/P&gt;

&lt;P&gt;Intel Advisor 17.1 (build 477503)&lt;/P&gt;

&lt;P&gt;Anybody some idea?&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2016 14:15:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096928#M15839</guid>
      <dc:creator>hlrs</dc:creator>
      <dc:date>2016-11-08T14:15:31Z</dc:date>
    </item>
    <item>
      <title>We also tested the following</title>
      <link>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096929#M15840</link>
      <description>&lt;P&gt;We also tested the following version without success:&lt;/P&gt;

&lt;P&gt;Update 1 (build 486553)&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2016 10:46:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Feature-Request-collector-should-recognize-Cray-MPI-with-ALPS/m-p/1096929#M15840</guid>
      <dc:creator>hlrs</dc:creator>
      <dc:date>2016-11-10T10:46:42Z</dc:date>
    </item>
  </channel>
</rss>

