Add support for building with tau and examples of running with tau

[bd4]

I'm not sure what the best approach for this is if we want to support building with or without TAU. Maybe ideally there is one Makefile, and you set an env var to enable tau? A second Makefile.tau that builds the same executables would be a good start.

[ianfoster]

Shall we assume that we always want to build with Tau? We’ll always want performance data, I assume.

On Jul 10, 2017, at 3:06 PM, Bryce Allen notifications@github.com wrote:

I'm not sure what the best approach for this is if we want to support building with or without TAU. Maybe ideally there is one Makefile, and you set an env var to enable tau? To start a second Makefile.tau that builds the same executables would be a good start.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CODARcode/Example-Heat_Transfer/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/AC28rQcMV0sgN5dUuSzcZgmVPox5pFiBks5sMoRCgaJpZM4OTWKT.

[jychoi-hpc]

That will simply greatly the building process. I guess adding commands for building this heat example with TAU would be an easy task.

However, I think we also need to consider or define the level of information we want to get from TAU. Would it be enough to get TAU information only from an application level. Or, do we need more depth information, such as, traces from depending libraries, such as Adios, SZ, etc?

On Jul 10, 2017, at 6:51 PM, Ian Foster notifications@github.com wrote:

Shall we assume that we always want to build with Tau? We’ll always want performance data, I assume.

On Jul 10, 2017, at 3:06 PM, Bryce Allen notifications@github.com wrote:

I'm not sure what the best approach for this is if we want to support building with or without TAU. Maybe ideally there is one Makefile, and you set an env var to enable tau? To start a second Makefile.tau that builds the same executables would be a good start.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CODARcode/Example-Heat_Transfer/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/AC28rQcMV0sgN5dUuSzcZgmVPox5pFiBks5sMoRCgaJpZM4OTWKT.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ianfoster]

The initial set of information that we want is illustrated here:

https://github.com/CODARcode/TAU_PROF2JASON/blob/master/performance.txt

On Jul 11, 2017, at 9:12 AM, Jong Choi notifications@github.com wrote:

That will simply greatly the building process. I guess adding commands for building this heat example with TAU would be an easy task.

However, I think we also need to consider or define the level of information we want to get from TAU. Would it be enough to get TAU information only from an application level. Or, do we need more depth information, such as, traces from depending libraries, such as Adios, SZ, etc?

On Jul 10, 2017, at 6:51 PM, Ian Foster notifications@github.com wrote:

Shall we assume that we always want to build with Tau? We’ll always want performance data, I assume.

On Jul 10, 2017, at 3:06 PM, Bryce Allen notifications@github.com wrote:

I'm not sure what the best approach for this is if we want to support building with or without TAU. Maybe ideally there is one Makefile, and you set an env var to enable tau? To start a second Makefile.tau that builds the same executables would be a good start.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CODARcode/Example-Heat_Transfer/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/AC28rQcMV0sgN5dUuSzcZgmVPox5pFiBks5sMoRCgaJpZM4OTWKT.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/CODARcode/Example-Heat_Transfer/issues/3#issuecomment-314455642, or mute the thread https://github.com/notifications/unsubscribe-auth/AC28rRxbBBePhFuOuqeJ3mckm8q7IfNuks5sM4H9gaJpZM4OTWKT.

[jychoi-hpc]

@abidmalik1967, can you provide a short instruction on how to build Heat example with TAU? I just want to look at first to check how easy or difficult it is.

[abidmalikwaterloo]

@jychoi-hpc Instructions are here: https://github.com/CODARcode/TAU_PROF2JASON

You need to build TAU with ADIOS. There is a special flag for this. Then you need to change makefile for each component using the tau wrappers for instrumentation. I emailed every one sample Makefile for each component and for make settings. I can upload the makefiles as well if you haven't received them. Also, you need to change the workflow.swift in order to dump information in separate directories.There are other scripts that we have which can be used to manipulate the TAU data. I am testing them and will upload the detail soon.

[abidmalikwaterloo]

@bd4 Does Cheetah work with TAU?