mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add 2048x2048 rendered image to 2024/endoh1

Browse Source
This commit is contained in:
Landon Curt Noll committed 2025-10-07 18:24:43 -07:00
1 parent 1dfbd4644f
commit 043f8c52f1
9 files changed
+119 -23
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2024/2024.tar.bz2
BIN
View File
Binary file not shown.
2024/endoh1/.entry.json
+8
View File
@@ -93,6 +93,14 @@
"display_via_github" : true,
"entry_text" : "1024x1024 image in PNG form"
},
{
"file_path" : "endoh1-2048.png",
"inventory_order" : 130,
"OK_to_edit" : true,
"display_as" : "image",
"display_via_github" : true,
"entry_text" : "2048x2048 image in PNG form"
},
{
"file_path" : "2024_endoh1.tar.bz2",
"inventory_order" : 1415926535,
2024/endoh1/2024_endoh1.tar.bz2
BIN
View File
Binary file not shown.
2024/endoh1/README.md
+50 -3
View File
@@ -84,12 +84,56 @@ value before attempting to try a larger size such as **512** and beyond.
<div id="larger">
### Be first to build images larger than 1024x1024
### Be first to build images larger than 2048x2048
</div>
#### On the 2048x2048 rendering:
[Joel Yliluoma](../../thanks-for-help.html#bisqwit) rendered:
- [record 1024x1024 image](endoh1-1024.png)
- [2048x2048 image](endoh1-2048.png)
Here is the fun saga of how the above image was rendered.
> The above image was started on **Thu Sep 11 10:14:24 AM UTC 2025**
> using 118 parallel jobs, then was suspended or 1 hour at the `Y=217` mark,
> was interrupted accidentally at the `Y=254` mark. After a quick
> edit to the his version of the `try.sh` script so that it will not delete
> existing work when restarted, he started again a minute later, at the
> **Thu Sep 11 01:36:08 PM UTC 2025**. The rendering was interrupted again
> at the `Y=972` mark for a couple of minutes, and interrupted again
> on `Y=1017` mark, due to a system crash (due to memory exhaustion not
> entirely related to the rendering). The rendering resumed 4 hours later,
> this time using 49 parallel jobs, on **Fri Sep 12 09:23:04 PM UTC 2025**
> when the rendering was finished on **Sat Sep 13 06:24:39 PM UTC 2025**.
> However files at `Y=1017` were corrupt by the system crash, so rendering
> re-resumed on **Sat Sep 13 06:25:56 PM UTC 2025** and truly finished on:
> **Sat Sep 13 06:29:51 PM UTC 2025**! :-)
The hardware used to render was:
```
CPU: AMD Ryzen Threadripper 3960X 24-Core Processor
between 49 and 118 threads
GCC 14.2.0-19 14.2.0
Debian Testing (currently Debian 14…ish?)
GNU Make 4.4.1
```
A summary of [Joel Yliluoma](../../thanks-for-help.html#bisqwit) valiant effort
to render the above image is as follows:
User time: **22 days 9 hours 13 minutes 54.094 seconds**<br>
Sys time: **18 days 18 hours 58 minutes 30.936 seconds**
#### On the 1024x1024 rendering:
[Joel Yliluoma](../../thanks-for-help.html#bisqwit) rendered:
- [1024x1024 image](endoh1-1024.png)
The above image was rendered between **Wed Sep 10 09:21:22 PM UTC 2025** and
**Thu Sep 11 09:48:40 AM UTC 2025** using 78 jobs in parallel on:
@@ -100,7 +144,10 @@ The above image was rendered between **Wed Sep 10 09:21:22 PM UTC 2025** and
GCC 14.2.0-19 14.2.0
Debian Testing (currently Debian 14…ish?)
GNU Make 4.4.1
```
```
#### Question
**QUESTION**: Do you have the patience to build an even larger image?
If you do, **using the program as it is written of course**, please [send the IOCCC](../../judges.html)
2024/endoh1/endoh1-2048.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 167 KiB

2024/endoh1/index.html
+44 -9
View File
@@ -25,14 +25,14 @@
<!-- END: this line ends content from: inc/head.default.html -->
<!-- -->
<!-- This web page was formed via the tool: bin/readme2index.sh -->
<!-- The content of main section of this web page came from: 2024/endoh1/README.md -->
<!-- This web page was formed via the tool: unspecified -->
<!-- The main section of this web page came from JSON and other data files -->
<!-- -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- !!! Do not modify this web page, instead modify the file: 2024/endoh1/README.md !!! -->
<!-- !!! Do not modify this web page, instead modify the file: 2024/endoh1/README.md !!! -->
<!-- !!! Do not modify this web page, instead modify the file: 2024/endoh1/README.md !!! -->
<!-- The main section of this web page was generated via the tool: unspecified -->
<!-- The main section of this web page was generated via the tool: unspecified -->
<!-- The main section of this web page was generated via the tool: unspecified -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- Markdown content was converted into HTML via the tool: bin/md2html.sh -->
@@ -448,7 +448,7 @@
<a class="Right" href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/Makefile">Makefile</a>
<a class="Right" href="#inventory">Inventory</a>
<a class="Right" href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/prog.orig.c">Original C</a>
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.ioccc.org%2F2024%2Fendoh1%2Findex.html">&#x2713;</a>
<a class="Right" href="https://validator.w3.org/nu/?doc=#">&#x2713;</a>
</div>
<!-- END: this line ends content from: inc/navbar.mid.html -->
@@ -530,11 +530,44 @@ down the result. We recommend that experiment various values of <code>RESERVE</c
with moderate <code>SIZE</code> of <strong>32</strong> in order to try to find an optimal <code>JOBS</code>
value before attempting to try a larger size such as <strong>512</strong> and beyond.</p>
<div id="larger">
<h3 id="be-first-to-build-images-larger-than-1024x1024">Be first to build images larger than 1024x1024</h3>
<h3 id="be-first-to-build-images-larger-than-2048x2048">Be first to build images larger than 2048x2048</h3>
</div>
<h4 id="on-the-2048x2048-rendering">On the 2048x2048 rendering:</h4>
<p><a href="../../thanks-for-help.html#bisqwit">Joel Yliluoma</a> rendered:</p>
<ul>
<li><a href="endoh1-1024.png">record 1024x1024 image</a></li>
<li><a href="endoh1-2048.png">2048x2048 image</a></li>
</ul>
<p>Here is the fun saga of how the above image was rendered.</p>
<blockquote>
<p>The above image was started on <strong>Thu Sep 11 10:14:24 AM UTC 2025</strong>
using 118 parallel jobs, then was suspended or 1 hour at the <code>Y=217</code> mark,
was interrupted accidentally at the <code>Y=254</code> mark. After a quick
edit to the his version of the <code>try.sh</code> script so that it will not delete
existing work when restarted, he started again a minute later, at the
<strong>Thu Sep 11 01:36:08 PM UTC 2025</strong>. The rendering was interrupted again
at the <code>Y=972</code> mark for a couple of minutes, and interrupted again
on <code>Y=1017</code> mark, due to a system crash (due to memory exhaustion not
entirely related to the rendering). The rendering resumed 4 hours later,
this time using 49 parallel jobs, on <strong>Fri Sep 12 09:23:04 PM UTC 2025</strong>
when the rendering was finished on <strong>Sat Sep 13 06:24:39 PM UTC 2025</strong>.
However files at <code>Y=1017</code> were corrupt by the system crash, so rendering
re-resumed on <strong>Sat Sep 13 06:25:56 PM UTC 2025</strong> and truly finished on:
<strong>Sat Sep 13 06:29:51 PM UTC 2025</strong>! :-)</p>
</blockquote>
<p>The hardware used to render was:</p>
<pre><code> CPU: AMD Ryzen Threadripper 3960X 24-Core Processor
between 49 and 118 threads
GCC 14.2.0-19 14.2.0
Debian Testing (currently Debian 14…ish?)
GNU Make 4.4.1</code></pre>
<p>A summary of <a href="../../thanks-for-help.html#bisqwit">Joel Yliluoma</a> valiant effort
to render the above image is as follows:</p>
<p>User time: <strong>22 days 9 hours 13 minutes 54.094 seconds</strong><br>
Sys time: <strong>18 days 18 hours 58 minutes 30.936 seconds</strong></p>
<h4 id="on-the-1024x1024-rendering">On the 1024x1024 rendering:</h4>
<p><a href="../../thanks-for-help.html#bisqwit">Joel Yliluoma</a> rendered:</p>
<ul>
<li><a href="endoh1-1024.png">1024x1024 image</a></li>
</ul>
<p>The above image was rendered between <strong>Wed Sep 10 09:21:22 PM UTC 2025</strong> and
<strong>Thu Sep 11 09:48:40 AM UTC 2025</strong> using 78 jobs in parallel on:</p>
@@ -543,6 +576,7 @@ value before attempting to try a larger size such as <strong>512</strong> and be
GCC 14.2.0-19 14.2.0
Debian Testing (currently Debian 14…ish?)
GNU Make 4.4.1</code></pre>
<h4 id="question">Question</h4>
<p><strong>QUESTION</strong>: Do you have the patience to build an even larger image?
If you do, <strong>using the program as it is written of course</strong>, please <a href="../../judges.html">send the IOCCC</a>
the following:</p>
@@ -842,6 +876,7 @@ Adding multiple spheres would require stack support for recursive ray tracing (s
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/ref.32.png">ref.32.png</a> - 32x32 image in PNG form</li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/ref.128.png">ref.128.png</a> - 128x128 image in PNG form</li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/endoh1-1024.png">endoh1-1024.png</a> - 1024x1024 image in PNG form</li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/endoh1-2048.png">endoh1-2048.png</a> - 2048x2048 image in PNG form</li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/ref.512.png">ref.512.png</a> - 512x512 image in PNG form</li>
<li><a href="https://github.com/ioccc-src/winner/blob/master/2024/endoh1/ref.512-variant.png">ref.512-variant.png</a> - variant of 512x512 image in PNG form</li>
</ul>
@@ -919,7 +954,7 @@ Jump to: <a href="#">top</a>
<div id="coda"><h3>Coda</h3>
<p>
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.ioccc.org%2F2024%2Fendoh1%2Findex.html" rel="nofollow">Nu HTML check this web page</a><br>
<a href="https://validator.w3.org/nu/?doc=#" rel="nofollow">Nu HTML check this web page</a><br>
<a href="#top">Jump to top</a> <a href="#content">Jump to Content</a> <a href="#inventory">Jump to Inventory</a><br>
</p>
</div>