generated from NCAR/NCAR_mkdocs_template
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
90 additions
and
17 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,30 +1,103 @@ | ||
# 2025 Improving Scientific Software Conference | ||
<style> | ||
.md-content .md-typeset h1 { | ||
display: none; | ||
} | ||
.table { | ||
display: table; | ||
} | ||
.row { | ||
display: table-row; | ||
} | ||
.cell { | ||
display: table-cell; | ||
padding: 2px; | ||
padding-right: 20px; | ||
} | ||
</style> | ||
|
||
## About ISS | ||
<figure markdown="span"> | ||
<img src="../../assets/iss2025.png" alt="drawing" width="80%"/> | ||
<figcaption>**From Legacy to Leading-Edge: Transforming Software Design in | ||
Science to Meet Tomorrow’s Challenges**</figcaption> | ||
</figure> | ||
|
||
The annual Improving Scientific Software Conference organized by the UCAR Software Engineering | ||
Assembly (SEA) will take place in spring 2025 as a hybrid event in Boulder, Colorado and virtually. | ||
<div class="table"> | ||
<div class="row"> | ||
<div class="cell"><b>When:</b></div> | ||
<div class="cell">7-10 April, 2025</div> | ||
</div> | ||
<div class="row"> | ||
<div class="cell"><b>Where:</b></div> | ||
<div class="cell">Boulder, CO and virtual</div> | ||
</div> | ||
</div> | ||
|
||
The annual Improving Scientific Software Conference brings together software | ||
engineers, scientists, developers - any individuals with an interest in | ||
scientific software design - to share novel experiences and best practices, | ||
develop connections across divisions and institutions, and advance our | ||
community. | ||
|
||
The pace of change for those using and developing scientific software | ||
accelerated in ways we have not seen in some time. Increasingly, tools and even | ||
models from the private sector are crossing over into our science domains. Large | ||
hyperscalers are driving changes in hardware priorities and we must adapt. And | ||
generative AI developments invite both potential and uncertainty for both | ||
developers and scientists. | ||
|
||
The 2025 Improving Scientific Software Conference is organized by the UCAR | ||
Software Engineering Assembly (SEA). | ||
|
||
### Audience | ||
|
||
The conference is for staff and students at research institutions, universities, and in industry who | ||
are interested in learning and discussing the latest developments and practices in scientific | ||
software. Those working in the geosciences will likely find it most relevant. However, anyone who | ||
finds the agenda beneficial to them is welcome to attend even if they do not fit the category | ||
previously stated. | ||
The conference is for staff and students at research institutions, universities, | ||
and in industry who are interested in learning and discussing the latest | ||
developments and practices in scientific software. Those working in the | ||
geosciences will likely find it most relevant. However, anyone who finds the | ||
agenda beneficial to them is welcome to attend even if they do not fit the | ||
category previously stated. | ||
|
||
## Submitting an Abstract | ||
|
||
TBD | ||
|
||
### Proceedings | ||
|
||
The ISS 2025 Conference will be using Jupyter Notebooks for proceedings again | ||
this year. For those who are unfamiliar, Jupyter Notebooks allow for both static | ||
representation of text, code, and equations using Markdown and HTML as well as | ||
interactive execution of commands with a selected language kernel (interpretor). | ||
This format provides authors with more tools to present their work and allows | ||
readers the opportunity to interact with your code or science in ways not | ||
possible with traditional text-only proceedings. | ||
|
||
**Useful resources for authors:** | ||
|
||
- Instructions for creating an ISS notebook proceeding | ||
- Example notebook proceedings | ||
|
||
We expect authors to submit proceedings by the end of the Conference week (11 | ||
April, 2025). This timing will allow us to offer an office hour during the | ||
conference to provide assistance to authors who want it. | ||
|
||
If you have any questions, please email the [ISS Proceedings | ||
committee](mailto:[email protected]). | ||
|
||
## Registration and Logistics | ||
|
||
More information coming soon! | ||
|
||
## Code of Conduct | ||
|
||
UCAR and NSF NCAR are committed to providing a safe, productive, and welcoming environment for all | ||
participants in any conference, workshop, field project or project hosted or managed by UCAR, no | ||
matter what role they play or their background. This includes respectful treatment of everyone | ||
regardless of gender, gender identity or expression, sexual orientation, disability, physical | ||
appearance, age, body size, race, religion, national origin, ethnicity, level of experience, | ||
political affiliation, veteran status, pregnancy, genetic information, as well as any other | ||
characteristic protected under state or federal law. | ||
UCAR and NSF NCAR are committed to providing a safe, productive, and welcoming | ||
environment for all participants in any conference, workshop, field project or | ||
project hosted or managed by UCAR, no matter what role they play or their | ||
background. This includes respectful treatment of everyone regardless of gender, | ||
gender identity or expression, sexual orientation, disability, physical | ||
appearance, age, body size, race, religion, national origin, ethnicity, level of | ||
experience, political affiliation, veteran status, pregnancy, genetic | ||
information, as well as any other characteristic protected under state or | ||
federal law. | ||
|
||
**All participants are required to abide by this [Code of Conduct](https://www.ucar.edu/who-we-are/ethics-integrity/codes-conduct/participants).** | ||
**All participants are required to abide by this [Code of | ||
Conduct](https://www.ucar.edu/who-we-are/ethics-integrity/codes-conduct/participants).** |