Welcome to DU!
The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards.
Join the community:
Create a free account
Support DU (and get rid of ads!):
Become a Star Member
Latest Breaking News
General Discussion
The DU Lounge
All Forums
Issue Forums
Culture Forums
Alliance Forums
Region Forums
Support Forums
Help & Search
Go ahead, I dare you, ask for time on Badger and Grizzly...
I'm not sure that this is acceptable on a family blog, but here goes:
I came across this text today:
Conclusion:
Therefore, we propose a total one-year allocation of 5,050,000 CPU-hrs on Badger and Grizzly:
25,000 for (1) + 25,000 for (2) + 5,000,000 for (3). This should be divided into 50,000 CPU-hrs on Badger
for (1) and (2) and 5,000,000 CPU-hrs on Grizzly for (3). Total data storage needs are 10 TB in Lustre
scratch space and Campaign Storage space. Many of the large trajectory files may be deleted after
publication of the resulting paper; hence, we do not need as much archival storage space. We ask for 5 TB
Archival Space.
Therefore, we propose a total one-year allocation of 5,050,000 CPU-hrs on Badger and Grizzly:
25,000 for (1) + 25,000 for (2) + 5,000,000 for (3). This should be divided into 50,000 CPU-hrs on Badger
for (1) and (2) and 5,000,000 CPU-hrs on Grizzly for (3). Total data storage needs are 10 TB in Lustre
scratch space and Campaign Storage space. Many of the large trajectory files may be deleted after
publication of the resulting paper; hence, we do not need as much archival storage space. We ask for 5 TB
Archival Space.
It's from here:
Salts in Hot Water: Developing a Scientific Basis for Supercritical Desalination and Strategic Metal Recovery
Badger and Grizzly indeed...
