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

Add starting point for SC24 tutorials #18

Merged
merged 13 commits into from
Apr 15, 2024
Merged

Add starting point for SC24 tutorials #18

merged 13 commits into from
Apr 15, 2024

Conversation

ocaisa
Copy link
Member

@ocaisa ocaisa commented Apr 11, 2024

Initial commit is based off of the isc24 tutorial but will need tuning. We have up to 3 presenters and 2 assistants. Up to 2 presenters may claim travel reimbursement (up to 1400USD). A 1400USD honorarium is also split between up to 2 presenters. Presenters will get a tutorial pass, assistants will have to request one (and may not have one granted).

Points needed to be addressed by the application are:

  1. Abstract in text format (200-word maximum).
  2. A detailed description of the proposed tutorial (two pages maximum) with the following sections:
    • Tutorial goals – i.e., what will the audience learn about?
    • Relevance for conference attendees – i.e., how does the topic fit with SC?
    • Target audience – i.e., what is the expected audience (researchers, students, developers, practitioners, etc.) and what each one of them will learn?
    • Content level – i.e., how is the content of the tutorial divided (in %) between beginner, intermediate, and advanced?
    • Audience prerequisites – i.e., what should the attendees know to successfully follow the tutorial?
    • Tutorial content – i.e., what is the content, schedule, and organization over the desired time (half- or full-day)?
    • Cohesion measures – i.e., how do you ensure a cohesive tutorial – only for tutorials with multiple presenters from different institutions?
    • Previous editions and potential updates – i.e., if, and where and when was this tutorial presented before, and how will it be updated for SC24?
  3. Detailed outline of the tutorial (one page maximum, in outline form). This “detailed course outline” will be the most critical part of the submission.
  4. Hands-on feasibility check/analysis: If you propose a Hands-on Tutorial (demo- or exercise-based tutorial), you must include an extra section in your tutorial proposal explaining to the committee how your demo and/or exercises have been thoroughly tested and debugged in a variety of settings, to ensure completely smooth operation at the conference. Add this information as part of the tutorial content (see 2, above), which could therefore be extended with at most half a page. Note: The conference will provide SCinet wireless network access to all tutorial rooms. Tutorials requesting wired Ethernet must include a clear justification for the request in their proposal.
  5. Résumé or Curriculum Vitae for each presenter (six presenters maximum, two pages maximum each). Make sure this includes a list of short courses each presenter has taught.
  6. A statement agreeing to release the notes for the SC24 tutorial digital copy.
  7. A request for travel support, if any. This is not factored in the evaluation.

@ocaisa ocaisa marked this pull request as ready for review April 11, 2024 12:58
@boegel boegel merged commit 0088d32 into main Apr 15, 2024
2 checks passed
\end{itemize}
\item [01:00-01:30] \emph{(30min)} Use cases (workflows, CI), incl. hands-on
\item [01:30-02:00] \emph{(30min coffee break)}
\item [02:00-02:15] \emph{(15min)} Testing software in EESSI % AOC: Drop this to recover time?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should say "quality assurance"

@boegel boegel deleted the sc24 branch April 19, 2024 09:01
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

Successfully merging this pull request may close these issues.

2 participants