notes:fall2024:projects:pnc0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| notes:fall2024:projects:pnc0 [2024/10/02 01:35] – [timing] cmazzara | notes:fall2024:projects:pnc0 [2024/10/03 01:23] (current) – amelvil2 | ||
|---|---|---|---|
| Line 32: | Line 32: | ||
| =====timing===== | =====timing===== | ||
| One way to calculate your runtime is by using the get_frame_counter() Vircon32 function. You will need to first store the start frames (before you tally the prime numbers) and your end frames (after you tally the prime numbers). Subtracting the start frames from the end frames will give you a value that you can use to find your runtime. | One way to calculate your runtime is by using the get_frame_counter() Vircon32 function. You will need to first store the start frames (before you tally the prime numbers) and your end frames (after you tally the prime numbers). Subtracting the start frames from the end frames will give you a value that you can use to find your runtime. | ||
| - | The get_frame_counter() function obtains the current value of the frame counter (there are 60 frames per second). If you’d prefer, you could use get_time() or get_cycle_counter(). Just remember the runtime will need to be drawn in seconds with three decimal places for milliseconds. | + | The get_frame_counter() function obtains the current value of the frame counter (there are 60 frames per second). If you’d prefer, you could use get_time() or get_cycle_counter(). Just remember the runtime will need to be drawn in seconds with three decimal places for milliseconds. |
| =====titles===== | =====titles===== | ||
| Line 48: | Line 48: | ||
| print_at( X, Y-10, "===== ======== ==== == ====== ====" ); | print_at( X, Y-10, "===== ======== ==== == ====== ====" ); | ||
| </ | </ | ||
| + | |||
| + | =====info===== | ||
| + | You will need to print the info. This can be done similarly to: | ||
| + | < | ||
| + | print type name at an X and Y; | ||
| + | Add X to itself + some value; | ||
| + | itoa Value; | ||
| + | print Value at an X and Y; | ||
| + | repeat x amount of times; | ||
| + | Time = SomeTime - OtherTime | ||
| + | ftoa Value; | ||
| + | Some string length, manipulation, | ||
| + | </ | ||
| + | |||
| + | It is suggested that you make this into a function with parameters that you can pass to it. This may be done for cleanliness and ease of use in the future! | ||
| + | |||
| + | Also, two important functions used in the example are the itoa and ftoa functions which are a part of the string.h library. They allow you to convert numbers to strings which will be important for displaying data that you have recorded. | ||
| ====wedge pnc0 runtimes==== | ====wedge pnc0 runtimes==== | ||
| < | < | ||
| Line 62: | Line 79: | ||
| 4096 9.516 | 4096 9.516 | ||
| 8192 38.033 | 8192 38.033 | ||
| + | </ | ||
| + | |||
| + | |||
| + | ====MrVengeance pnc0 runtimes==== | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | ====cburling pnc0 runtimes==== | ||
| + | < | ||
| + | 1024 0.483 | ||
| + | 2048 1.966 | ||
| + | 4096 7.833 | ||
| + | 8192 31.333 | ||
| + | </ | ||
| + | |||
| + | |||
| + | ====bpatricelli pnc0 runtimes==== | ||
| + | < | ||
| + | 1024 0.483 | ||
| + | 2048 1.967 | ||
| + | 4096 7.85 | ||
| + | 8192 31.367 | ||
| + | </ | ||
| + | |||
| + | ====amelvil2 pnc0 runtimes=== | ||
| + | < | ||
| + | 1024 0.107 | ||
| + | 2048 0.283 | ||
| + | 4096 1.102 | ||
| + | 8192 3.683 | ||
| </ | </ | ||
notes/fall2024/projects/pnc0.1727832949.txt.gz · Last modified: 2024/10/02 01:35 by cmazzara
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
