Skip to content

Commit

Permalink
Add more links
Browse files Browse the repository at this point in the history
  • Loading branch information
matthewreyna committed Jan 9, 2025
1 parent 814b7a5 commit c382557
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion 2025/submissions/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ No. The only part of the Dockerfile we care about are the three lines marked as

__What's the base image in Docker?__

Think of Docker as a series of images, or snapshots of a virtual machine, that are layered on top of each other. For example, your image may built on top of a very lightweight Ubuntu operating system with Python 3.8.6 from the official Docker Hub (think of it as a GitHub for Docker). You can then install your NumPy, SciPy, and other libraries on it. If you need the latest version of TensorFlow, then search for it on [hub.docker.com](https://hub.docker.com/) and edit your file so that the first line of your Dockerfile now reads as: `FROM tensorflow`. For a specific version, say 1.11, lookup the [tags](https://hub.docker.com/r/tensorflow/tensorflow/tags) and change it accordingly to a specific version, such as`FROM tensorflow:1.11.0`. We recommend using specific versions for reproducibility.
Think of Docker as a series of images, or snapshots of a virtual machine, that are layered on top of each other. For example, your image may built on top of a very lightweight Ubuntu operating system with Python 3.8.6 from the official Docker Hub (think of it as a GitHub for Docker). You can then install your NumPy, SciPy, and other libraries on it. If you need the latest version of TensorFlow, then search for it on [hub.docker.com](https://hub.docker.com/) and edit your file so that the first line of your Dockerfile now reads as: `FROM tensorflow`. For a specific version, say 1.11, lookup the [tags](https://hub.docker.com/r/tensorflow/tensorflow/tags) and change it accordingly to a specific version, such as `FROM tensorflow:1.11.0`. We recommend using specific versions for reproducibility.

__sklearn or scikit-learn?__

Expand Down
2 changes: 1 addition & 1 deletion _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ logo: /assets/img/physionet-cinc.gif
logo_after_2015: /assets/img/ecg-ml.gif
description: George B. Moody PhysioNet Challenge
grantnotice: <p>Supported by the <a href="https://www.nibib.nih.gov/">National Institute of Biomedical Imaging and Bioengineering (NIBIB)</a> under NIH grant number R01EB030362.</p> <p>© PhysioNet Challenges. Website content licensed under the <a href="https://creativecommons.org/licenses/by/4.0/legalcode">Creative Commons Attribution 4.0 International Public License.</a></p>
quicklinks: <div id="quicklinks"><b>Quick links for this year's Challenge:</b><ul><li><a href="https://forms.gle/baopm4U2Z2dmju777">Registration form</a></li><li>Example <a href="https://github.com/physionetchallenges/matlab-example-2025">MATLAB</a> and <a href="https://github.com/physionetchallenges/python-example-2025">Python</a> submissions and <a href="https://github.com/physionetchallenges/evaluation-2025">scoring</a> code</li><li>Submission <a href="https://physionetchallenges.org/2025/submissions/">instructions</a> and <a href="https://forms.gle/af4jwLMzjJPTqos8A">form</a></li><li><a href="https://physionetchallenges.org/2025/leaderboard/">Leaderboard</a>, <a href="https://physionetchallenges.org/2025/results/">results</a>, and <a href="https://physionetchallenges.org/2025/papers/">papers</a></li><li><a href="https://groups.google.com/forum/#!forum/physionet-challenges">Public discussion forum</a></li><li><a href="https://physionetchallenges.org/2025/#rules">Rules and deadlines</a></li><li><a href="https://physionetchallenges.org/2025/faq/">Current</a> and <a href="https://physionetchallenges.org/faq/">general FAQs</a></li><li><a href="https://physionetchallenges.org/about/">About</a></li></ul> Please post questions and comments in the forum. However, if your question reveals information about your entry, then please email info at physionetchallenge.org. We may post parts of our reply publicly if we feel that all Challengers should benefit from it. We will not answer emails about the Challenge to any other address.</div>
quicklinks: <div id="quicklinks"><b>Quick links for this year's Challenge:</b><ul><li><a href="https://forms.gle/dJQzeWsXNVgM2URY9">Registration form</a></li><li>Example <a href="https://github.com/physionetchallenges/matlab-example-2025">MATLAB</a> and <a href="https://github.com/physionetchallenges/python-example-2025">Python</a> submissions and <a href="https://github.com/physionetchallenges/evaluation-2025">scoring</a> code</li><li>Submission <a href="https://physionetchallenges.org/2025/submissions/">instructions</a></li><li><a href="https://physionetchallenges.org/2025/leaderboard/">Leaderboard</a>, <a href="https://physionetchallenges.org/2025/results/">results</a>, and <a href="https://physionetchallenges.org/2025/papers/">papers</a></li><li><a href="https://groups.google.com/forum/#!forum/physionet-challenges">Public discussion forum</a></li><li><a href="https://physionetchallenges.org/2025/#rules">Rules and deadlines</a></li><li><a href="https://physionetchallenges.org/2025/faq/">Current</a> and <a href="https://physionetchallenges.org/faq/">general FAQs</a></li><li><a href="https://physionetchallenges.org/about/">About</a></li></ul> Please post questions and comments in the forum. However, if your question reveals information about your entry, then please email info at physionetchallenge.org. We may post parts of our reply publicly if we feel that all Challengers should benefit from it. We will not answer emails about the Challenge to any other address.</div>
show_downloads: false
google_analytics:
theme: jekyll-theme-minimal

0 comments on commit c382557

Please sign in to comment.