Skip to content
Snippets Groups Projects
Commit 16a5edf5 authored by David M. Rogers's avatar David M. Rogers
Browse files

Initial commit

parents
No related branches found
No related tags found
No related merge requests found
_site
.sass-cache
.jekyll-cache
.jekyll-metadata
vendor
404.html 0 → 100644
---
permalink: /404.html
layout: default
---
<style type="text/css" media="screen">
.container {
margin: 10px auto;
max-width: 600px;
text-align: center;
}
h1 {
margin: 30px 0;
font-size: 4em;
line-height: 1;
letter-spacing: -1px;
}
</style>
<div class="container">
<h1>404</h1>
<p><strong>Page not found :(</strong></p>
<p>The requested page could not be found.</p>
</div>
source 'https://rubygems.org'
gem 'jekyll'
gem 'jekyll-sitemap'
gem 'jekyll-redirect-from'
gem 'jekyll-seo-tag'
gem 'jekyll-coffeescript'
gem 'github-pages', group: :jekyll_plugins
gem 'webrick'
GEM
remote: https://rubygems.org/
specs:
activesupport (6.0.4.1)
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 0.7, < 2)
minitest (~> 5.1)
tzinfo (~> 1.1)
zeitwerk (~> 2.2, >= 2.2.2)
addressable (2.8.0)
public_suffix (>= 2.0.2, < 5.0)
coffee-script (2.4.1)
coffee-script-source
execjs
coffee-script-source (1.11.1)
colorator (1.1.0)
commonmarker (0.17.13)
ruby-enum (~> 0.5)
concurrent-ruby (1.1.9)
dnsruby (1.61.7)
simpleidn (~> 0.1)
em-websocket (0.5.3)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0)
ethon (0.15.0)
ffi (>= 1.15.0)
eventmachine (1.2.7)
execjs (2.8.1)
faraday (1.8.0)
faraday-em_http (~> 1.0)
faraday-em_synchrony (~> 1.0)
faraday-excon (~> 1.1)
faraday-httpclient (~> 1.0.1)
faraday-net_http (~> 1.0)
faraday-net_http_persistent (~> 1.1)
faraday-patron (~> 1.0)
faraday-rack (~> 1.0)
multipart-post (>= 1.2, < 3)
ruby2_keywords (>= 0.0.4)
faraday-em_http (1.0.0)
faraday-em_synchrony (1.0.0)
faraday-excon (1.1.0)
faraday-httpclient (1.0.1)
faraday-net_http (1.0.1)
faraday-net_http_persistent (1.2.0)
faraday-patron (1.0.0)
faraday-rack (1.0.0)
ffi (1.15.4)
forwardable-extended (2.6.0)
gemoji (3.0.1)
github-pages (222)
github-pages-health-check (= 1.17.9)
jekyll (= 3.9.0)
jekyll-avatar (= 0.7.0)
jekyll-coffeescript (= 1.1.1)
jekyll-commonmark-ghpages (= 0.1.6)
jekyll-default-layout (= 0.1.4)
jekyll-feed (= 0.15.1)
jekyll-gist (= 1.5.0)
jekyll-github-metadata (= 2.13.0)
jekyll-mentions (= 1.6.0)
jekyll-optional-front-matter (= 0.3.2)
jekyll-paginate (= 1.1.0)
jekyll-readme-index (= 0.3.0)
jekyll-redirect-from (= 0.16.0)
jekyll-relative-links (= 0.6.1)
jekyll-remote-theme (= 0.4.3)
jekyll-sass-converter (= 1.5.2)
jekyll-seo-tag (= 2.7.1)
jekyll-sitemap (= 1.4.0)
jekyll-swiss (= 1.0.0)
jekyll-theme-architect (= 0.2.0)
jekyll-theme-cayman (= 0.2.0)
jekyll-theme-dinky (= 0.2.0)
jekyll-theme-hacker (= 0.2.0)
jekyll-theme-leap-day (= 0.2.0)
jekyll-theme-merlot (= 0.2.0)
jekyll-theme-midnight (= 0.2.0)
jekyll-theme-minimal (= 0.2.0)
jekyll-theme-modernist (= 0.2.0)
jekyll-theme-primer (= 0.6.0)
jekyll-theme-slate (= 0.2.0)
jekyll-theme-tactile (= 0.2.0)
jekyll-theme-time-machine (= 0.2.0)
jekyll-titles-from-headings (= 0.5.3)
jemoji (= 0.12.0)
kramdown (= 2.3.1)
kramdown-parser-gfm (= 1.1.0)
liquid (= 4.0.3)
mercenary (~> 0.3)
minima (= 2.5.1)
nokogiri (>= 1.12.5, < 2.0)
rouge (= 3.26.0)
terminal-table (~> 1.4)
github-pages-health-check (1.17.9)
addressable (~> 2.3)
dnsruby (~> 1.60)
octokit (~> 4.0)
public_suffix (>= 3.0, < 5.0)
typhoeus (~> 1.3)
html-pipeline (2.14.0)
activesupport (>= 2)
nokogiri (>= 1.4)
http_parser.rb (0.8.0)
i18n (0.9.5)
concurrent-ruby (~> 1.0)
jekyll (3.9.0)
addressable (~> 2.4)
colorator (~> 1.0)
em-websocket (~> 0.5)
i18n (~> 0.7)
jekyll-sass-converter (~> 1.0)
jekyll-watch (~> 2.0)
kramdown (>= 1.17, < 3)
liquid (~> 4.0)
mercenary (~> 0.3.3)
pathutil (~> 0.9)
rouge (>= 1.7, < 4)
safe_yaml (~> 1.0)
jekyll-avatar (0.7.0)
jekyll (>= 3.0, < 5.0)
jekyll-coffeescript (1.1.1)
coffee-script (~> 2.2)
coffee-script-source (~> 1.11.1)
jekyll-commonmark (1.3.1)
commonmarker (~> 0.14)
jekyll (>= 3.7, < 5.0)
jekyll-commonmark-ghpages (0.1.6)
commonmarker (~> 0.17.6)
jekyll-commonmark (~> 1.2)
rouge (>= 2.0, < 4.0)
jekyll-default-layout (0.1.4)
jekyll (~> 3.0)
jekyll-feed (0.15.1)
jekyll (>= 3.7, < 5.0)
jekyll-gist (1.5.0)
octokit (~> 4.2)
jekyll-github-metadata (2.13.0)
jekyll (>= 3.4, < 5.0)
octokit (~> 4.0, != 4.4.0)
jekyll-mentions (1.6.0)
html-pipeline (~> 2.3)
jekyll (>= 3.7, < 5.0)
jekyll-optional-front-matter (0.3.2)
jekyll (>= 3.0, < 5.0)
jekyll-paginate (1.1.0)
jekyll-readme-index (0.3.0)
jekyll (>= 3.0, < 5.0)
jekyll-redirect-from (0.16.0)
jekyll (>= 3.3, < 5.0)
jekyll-relative-links (0.6.1)
jekyll (>= 3.3, < 5.0)
jekyll-remote-theme (0.4.3)
addressable (~> 2.0)
jekyll (>= 3.5, < 5.0)
jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
rubyzip (>= 1.3.0, < 3.0)
jekyll-sass-converter (1.5.2)
sass (~> 3.4)
jekyll-seo-tag (2.7.1)
jekyll (>= 3.8, < 5.0)
jekyll-sitemap (1.4.0)
jekyll (>= 3.7, < 5.0)
jekyll-swiss (1.0.0)
jekyll-theme-architect (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-cayman (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-dinky (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-hacker (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-leap-day (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-merlot (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-midnight (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-minimal (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-modernist (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-primer (0.6.0)
jekyll (> 3.5, < 5.0)
jekyll-github-metadata (~> 2.9)
jekyll-seo-tag (~> 2.0)
jekyll-theme-slate (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-tactile (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-theme-time-machine (0.2.0)
jekyll (> 3.5, < 5.0)
jekyll-seo-tag (~> 2.0)
jekyll-titles-from-headings (0.5.3)
jekyll (>= 3.3, < 5.0)
jekyll-watch (2.2.1)
listen (~> 3.0)
jemoji (0.12.0)
gemoji (~> 3.0)
html-pipeline (~> 2.2)
jekyll (>= 3.0, < 5.0)
kramdown (2.3.1)
rexml
kramdown-parser-gfm (1.1.0)
kramdown (~> 2.0)
liquid (4.0.3)
listen (3.7.0)
rb-fsevent (~> 0.10, >= 0.10.3)
rb-inotify (~> 0.9, >= 0.9.10)
mercenary (0.3.6)
minima (2.5.1)
jekyll (>= 3.5, < 5.0)
jekyll-feed (~> 0.9)
jekyll-seo-tag (~> 2.1)
minitest (5.14.4)
multipart-post (2.1.1)
nokogiri (1.12.5-x86_64-linux)
racc (~> 1.4)
octokit (4.21.0)
faraday (>= 0.9)
sawyer (~> 0.8.0, >= 0.5.3)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
public_suffix (4.0.6)
racc (1.6.0)
rb-fsevent (0.11.0)
rb-inotify (0.10.1)
ffi (~> 1.0)
rexml (3.2.5)
rouge (3.26.0)
ruby-enum (0.9.0)
i18n
ruby2_keywords (0.0.5)
rubyzip (2.3.2)
safe_yaml (1.0.5)
sass (3.7.4)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
sawyer (0.8.2)
addressable (>= 2.3.5)
faraday (> 0.8, < 2.0)
simpleidn (0.2.1)
unf (~> 0.1.4)
terminal-table (1.8.0)
unicode-display_width (~> 1.1, >= 1.1.1)
thread_safe (0.3.6)
typhoeus (1.4.0)
ethon (>= 0.9.0)
tzinfo (1.2.9)
thread_safe (~> 0.1)
unf (0.1.4)
unf_ext
unf_ext (0.0.8)
unicode-display_width (1.8.0)
webrick (1.7.0)
zeitwerk (2.5.1)
PLATFORMS
x86_64-linux
DEPENDENCIES
github-pages
jekyll
jekyll-coffeescript
jekyll-redirect-from
jekyll-seo-tag
jekyll-sitemap
webrick
BUNDLED WITH
2.2.31
source "https://rubygems.org"
gem "jekyll"
gem "jekyll-sitemap"
gem "jekyll-redirect-from"
gem "jekyll-seo-tag"
#gem "jekyll-coffeescript"
gem "minima", "~> 2.5"
#gem "github-pages", group: :jekyll_plugins
#group :jekyll_plugins do
# gem "jekyll-feed", "~> 0.12"
#end
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
# and associated library.
platforms :mingw, :x64_mingw, :mswin, :jruby do
gem "tzinfo", "~> 1.2"
gem "tzinfo-data"
end
# Performance-booster for watching directories on Windows
gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin]
gem "webrick"
TODO 0 → 100644
1. create pages displaying each dataset
2. add summary icons to main page
3. add lots of documentation on how to create, post and, collaborate on datasets
- including OLCF onboarding doc refs.
4. add link to /news in top nav-bar
5. list out datasets by category
name: "ORNL Datasets"
title: "ORNL Dataset Portal"
author: "Oak Ridge National Laboratory"
description: "A collaborative space for the HPC and Data Science communities."
baseurl: "" # the subpath of your site, e.g. /blog
url: "https://frobnitzem.github.io/ornl-datasets"
repo_url: "https://github.com/frobnitzem/ornl-datasets"
github_username: ornl
# Build settings
theme: minima
plugins:
- jekyll-github-metadata
- jekyll-seo-tag
- jekyll-sitemap
- jekyll-feed
collections:
posts:
output: true
permalink: "/news/:year/:month/:day/:title/"
datasets:
output: true
permalink: "/:collection/:name"
# Exclude from processing.
# The following items will not be processed, by default.
# Any item listed under the `exclude:` key here will be automatically added to
# the internal "default list".
#
# Excluded items can be processed by explicitly listing the directories or
# their entries' file path in the `include:` list.
#
exclude:
- Gemfile
- Gemfile.lock
- README.md
- run.sh
- TODO
---
author: David M. Rogers
layout: post
title: "MCHound Dataset"
categories: ascr
---
The mchound dataset.
---
layout: default
---
<div class="home">
{%- if page.title -%}
<h1 class="page-heading">{{ page.title }}</h1>
{%- endif -%}
{{ content }}
{%- if site.datasets.size > 0 -%}
<h2 class="post-list-heading">{{ page.list_title | default: "Datasets" }}</h2>
<ul class="post-list">
{%- for post in site.datasets -%}
<li>
{%- assign date_format = site.minima.date_format | default: "%b %-d, %Y" -%}
<span class="post-meta">{{ post.date | date: date_format }}</span>
<h3>
<a class="post-link" href="{{ post.url | relative_url }}">
{{ post.title | escape }}
</a>
</h3>
{%- if site.show_excerpts -%}
{{ post.excerpt }}
{%- endif -%}
</li>
{%- endfor -%}
</ul>
<p class="rss-subscribe">subscribe <a href="{{ "/feed.xml" | relative_url }}">via RSS</a></p>
{%- endif -%}
</div>
---
layout: post
title: "MCHound Dataset"
date: 2021-11-16 16:27:51 -0500
categories: ascr
---
The MCHound dataset demonstrates Summit performance monitoring capabilities.
---
layout: default
title: About OLCF Datasets
permalink: /about/
---
## {{ page.title }}
{: .page-header .no_toc}
<!-- * Table of Contents
{:toc} -->
**Collaboration fuels our culture.**
The OLCF Datasets Site is intended to be a collaborative space for
the HPC and Data Science communities to share datasets and methods
for generation, analysis, and general computations.
### Contact
Check out our [FAQ](faq). If you have other questions please don't hesitate to contact [David Rogers](mailto:rogersdm@ornl.gov).
---
title: FAQ
layout: default
---
## {{ page.title }}
{: .page-header .no_toc}
*These FAQs primarily target developers working on publishing a dataset. Don't see your question listed below? Please contact [David M. Rogers](mailto:rogersdm@ornl.gov).*
* Table of Contents
{:toc}
### How do I set up a GitHub account?
If you’re new to GitHub and open source in general, figuring out how to get set up can be a challenge. You may want to read through the GitHub Help pages on [setting up and managing your GitHub profile](https://help.github.com/categories/setting-up-and-managing-your-github-profile/).
1. [Create an account on GitHub](https://github.com/join).
You *do not need* a separate work account and personal account. Instead, you can [link multiple email addresses to the same GitHub account](https://help.github.com/articles/adding-an-email-address-to-your-github-account/), which is almost always preferred.
2. [Update your profile information](https://github.com/settings/profile).
* **Photo**: A headshot photo, or image that is uniquely you.
* **Name**: Your first and last name.
* **Bio**: Include a few words about yourself! Don't forget to mention @ORNL.
* **URL**: This might be your [people.llnl.gov](https://people.llnl.gov) page, or a personal website if you prefer.
* **Company**: Probably `Oak Ridge National Laboratory, @ORNL`.
* **Location**: Your primary location.
3. Add your `@ORNL` email address (and any aliases) to your [Email Settings](https://github.com/settings/emails) page. This will link any commits done via [your Git identity](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup#Your-Identity) to your GitHub account.
4. [Enable two-factor authentication (2FA)](https://github.com/settings/security).
### What is two-factor authentication (2FA)?
There are several options for configuring 2FA for your GitHub account:
* [YubiKey](https://yubico.com) hardware security keys
* YubiKeys are the preferred 2FA option, due to the security of the YubiKey hardware tokens. If you have been issued an ORNL YubiKey, it is highly recommended for securing your GitHub (and other) accounts which support them.
* [Learn more about setting up your YubiKey with GitHub.com](https://help.github.com/articles/configuring-two-factor-authentication/#configuring-two-factor-authentication-using-fido-u2f)
* [Google Authenticator](https://support.google.com/accounts/answer/1066447)
* Google Authenticator is a mobile application which you can install on your personal or government issued phone.
* It provides a one-time token (OTP) which you can use to authenticate to GitHub.com
* [Learn more about setting up Google Authenticator with GitHub.com](https://help.github.com/articles/configuring-two-factor-authentication/#configuring-two-factor-authentication-using-a-totp-mobile-app)
* [Authy](https://authy.com/guides/github/)
* Authy is a desktop- or laptop-based application which can be used to generate a one-time token (OTP) for use logging in to GitHub.com.
* This option is usually best for when you do all or most of your work in an environment where you do not have access to a mobile phone or USB YubiKey.
* [Learn more about setting up Authy with GitHub.com](https://authy.com/guides/github/)
Additional 2FA info:
* You also have the option during 2FA to generate and save a list of recovery codes to get into your account in the event you lose access to one of your 2FA methods. This is *highly* recommended, and the recovery codes should be stored someplace safe. Some options for storing your recovery codes include:
* Printing the codes and storing them in a safe place in your office.
* Storing the recovery codes in a password manager that you might be using.
* We recommend that you set up *MULTIPLE* 2FA options. This can protect your access to your account in the event that you lose access to one of your authenticators.
* For more information, check out the [Two-factor Authentication](https://github.com/blog/1614-two-factor-authentication) post on the GitHub Blog.
* Having trouble setting up 2FA? Contact the [LLNL GitHub admins](mailto:github-admin@llnl.gov) who may be able to help.
### How do I get my dataset reviewed and released for GitHub?
Create your repository and dataset on its own. Both [code.ornl.gov](https://code.ornl.gov) and github are good options.
Next, send an email to this site's maintainer to get information
on the review process and add its listing here.
### What is/isn’t allowed to be included in my repo?
Remember that these repositories *are hosted* on GitHub servers, *NOT LLNL servers*, and content placed in them should be limited to "email like" communications. That means:
* NO Classified
* NO Export Controlled
* NO Official Use Only (OUO)
* NO Health Insurance Portability and Accountability Act (HIPAA)
* NO Personally Identifiable Information (PII)
* NO NDA or vendor-proprietary information
* NO Unclassified Controlled Information (UCI)
* NO Unclassified Controlled Nuclear Information (UCNI)
When in doubt, contact a Derivative Classifier (DC) for further guidance.
### My project is approved for release. Now what?
Make sure your repo follows best practices and includes the following informational files:
* An appropriate open source **license**. Details and examples can be seen at [LLNL Software Licensing](https://software.llnl.gov/about/licenses).
* A [**README**](https://guides.github.com/features/wikis/) file that summarizes what the software does and how others can use and contribute to it.
* A **NOTICE** containing any required funding acknowledgments for your project.
After your project has been initially released on GitHub and you are ready to provide a new version, a good practice is to tag the version and include [**release notes**](https://github.com/LLNL/.github/blob/main/community-health/release-template.md).
Another good practice is to provide **user documentation**. Read the Docs (RtD) is a common platform for user guides, tutorials, quick start instructions, and other forms of documentation.
Submit your repo to [**DOE CODE**](https://www.osti.gov/doecode/faq#what-is) so others can find it when searching through DOE-funded projects. After your repo is included in DOE CODE, you may also want to add the **digital object identifier** (DOI) to the repo.
If your repo is research software, consider submitting it to a journal that publishes scientific datasets.
### How does this website’s catalog work?
* The [`input_lists.json` file](https://github.com/frobnitzem/olcf-datasets/blob/main/_datasets/input_lists.json) lists information on included repositories.
* If you have a project logo, please follow the [instructions](https://github.com/frobnitzem/olcf-datasets/tree/main/assets/images/logos) for naming and uploading the file.
### How do I contribute to a dataset?
Refer to individual projects for their requirements on accepting contributions. In general though, we follow the "fork and pull" Git workflow model:
1. Fork a repository.
2. Develop your changes in your fork.
3. Sync your fork to the upstream repository (`git remote add upstream git@github.com:org/repo.git`).
4. Create a pull request to the "upstream" repository.
5. If approved, changes will be merged in by a repository maintainer.
---
# Feel free to add content and custom Front Matter to this file.
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
layout: home
---
The OLCF Datasets Site is a collaborative space for the HPC and Data Science communities to share datasets and methods for generation, analysis, and general computations.
run.sh 0 → 100644
bundle exec jekyll serve
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment