You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TAU Commander is currently stateful/context sensitive, even at runtime. So you can't create multiple experiments, select one of interest, recompile the code (with a unique name), then select a different experiment/measurement, recompile the code (with a name to reflect the current experiment) and queue them both up at once. It would be really nice, if it's possible, to be able to pass a flag to TAU Commander at runtime to specify which experiment the run and executable corresponds to. Something like:
tau --experiment ln1-hpgmg-sample srun ./bin/myexe.sample # in first batch script
tau --experiment ln1-hpgmg-profile srun ./bin/myexe.profile # in second batch script
It's possible that this isn't feasible due to limitations in TAU or it's dependencies, I'm not sure.
The text was updated successfully, but these errors were encountered:
Also, I wonder about taucmdr's ability to handle the simpler case where you're doing a parameter sweep, like a strong or weak scaling study, and the measurement isn't changing but you may want to run multiple trials concurrently. This is the simple case and probably a prerequisite for running different experiments concurrently---if it's not already implemented (I haven't tested).
TAU Commander is currently stateful/context sensitive, even at runtime. So you can't create multiple experiments, select one of interest, recompile the code (with a unique name), then select a different experiment/measurement, recompile the code (with a name to reflect the current experiment) and queue them both up at once. It would be really nice, if it's possible, to be able to pass a flag to TAU Commander at runtime to specify which experiment the run and executable corresponds to. Something like:
It's possible that this isn't feasible due to limitations in TAU or it's dependencies, I'm not sure.
The text was updated successfully, but these errors were encountered: