Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building STAT gui on summit #40

Open
roblatham00 opened this issue Feb 18, 2022 · 2 comments
Open

Building STAT gui on summit #40

roblatham00 opened this issue Feb 18, 2022 · 2 comments

Comments

@roblatham00
Copy link
Contributor

STAT user guide suggests using spack

on ORNL summit, I have found that stat-core-merger only works with python2.7, which poses challenges:

% spack spec stat+gui%[email protected] '^[email protected]' cxxflags=--std=c++14
Input spec
--------------------------------
stat%[email protected]+gui
    ^[email protected] cxxflags="--std=c++14"

Concretized
--------------------------------
==> Error: stat%[email protected]+gui ^[email protected] cxxflags="--std=c++14" is unsatisfiable, errors are:
  no version satisfies the given constraints
@lee218llnl
Copy link
Collaborator

To be honest, the stat-core-merger isn't very well supported and is not the primary use case for STAT. STAT is more commonly used to attach to running hung jobs.

Certainly to build STAT via spack, you will need to use python 3.X. I think some effort would need to be done to make stat-core-merger work with python 3.X. I know that this in inconvenient, but you could build STAT with spack with python 3.X to get the main STAT functionality (attach to running jobs and the GUI). You could then build a separate STAT from source with python 2.x (and without the GUI) to try to get stat-core-merger working. For the python 2.x build you can configure against the dependencies that were built with spack (i.e., mrnet, dynist, launchmon, graphlib, etc.) and just specify --with-python=/path/to/your/python2.7

@roblatham00
Copy link
Contributor Author

I'm sorry to hear that about stat-core-merger. I was looking for a way to collect backtraces and it did exactly what I wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants