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

SummitPLUS allocation #14

Open
markcoletti opened this issue Oct 24, 2023 · 6 comments
Open

SummitPLUS allocation #14

markcoletti opened this issue Oct 24, 2023 · 6 comments
Labels
infrastructure Creating and maintaining supporting documents, files, software, etc. question Further information is requested wontfix This will not be worked on

Comments

@markcoletti
Copy link
Contributor

We may need a SummitPLUS allocation to run tests for determinism on a different h/w platform.

@markcoletti markcoletti added the infrastructure Creating and maintaining supporting documents, files, software, etc. label Oct 24, 2023
@markcoletti
Copy link
Contributor Author

@gitrepoidoscar , @elwasif , and @asedova , the deadline for asking for a SummitPLUS allocation is the 30th, presuming we want one.

@asedova
Copy link
Contributor

asedova commented Oct 24, 2023

Do we want one? I don't anticipate us needing 100K node hours for this project, but you never know. I just wrote one for Slava and am about to write another one and they are not that easy, there are quite a few sections.

If we were to request ~80K node hours, what would we do with them? Only the data generation for DeePMD really uses a lot of compute (and any iterative active learning).

But maybe better safe than sorry.

@asedova asedova added the question Further information is requested label Oct 24, 2023
@markcoletti
Copy link
Contributor Author

But maybe better safe than sorry.

That's what I was thinking. Worse case, if we decide not to do this, I'm probably going to get a SummitPLUS allocation for a different project, and we can use some of the time from that. Regardless, as you stated, it can't hurt to have our own!

@asedova
Copy link
Contributor

asedova commented Oct 24, 2023

Problem is, we need that extensive justification for leadership time, which I don't know if we have.

@markcoletti
Copy link
Contributor Author

I sat next to Ashley Barker last week at the OLCF Users Meeting, and she encouraged me to pass on to others to put in requests. I got the impression they were going to green light what they get and let it be a battle royal, or something. In any case, can't hurt to try. Worse they can do is bounce it, in which case we have alternatives.

@asedova
Copy link
Contributor

asedova commented Jan 18, 2024

We had decided to use the one that related to Oscar's EXPRESS project and allow some MINNERVVA work on there. Oscar's EXPRESS application was rejected. So I guess we need to work on getting a DD on Frontier instead.

@asedova asedova added the wontfix This will not be worked on label Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Creating and maintaining supporting documents, files, software, etc. question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants