Add CSV for Firefly animation #59
Open
Conversation
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
Every LED picks ten nearest neighbours and starts to flash at a default period of 30 frames. Light from neighbouring LEDs that is visible during the own dark phase pushes the own cycle forward slightly. This should lead to sync'ed LEDs after a while, but does it? Actually, by separating R, G, B, there are three independent populations of 500 LEDs each (and in each population, the "same" LED may pick a slightly different set of neighbours if there are ties or almost-ties by distance). The three populations were then mixed in such a way that they end with a dark moment as last frame. The CSV is somewhat long, so I hope the tree will make 60 fs rather than 30 fps :)
Add CSV file for firefly animation
|
I think the length is almost bearable: "only" 2.5 mins with 30fps. I just feel that starting around frame 1000 or so, I'd argue that there isn't much more going on than before, It appears to just repeat the same 30 frames (that is the frequency with which all LEDs turn off approximately) over and over. Or the changes to before are too little to be noticeable. Don't know if the current runner code permits this, but last year Matt just interrupted animations when he had enough. So, he might just end the animation after the first half a minute or so. |
|
Thank you for actually trying it out - for I didn’t. 😔 I may submit a shorter update with fewer rounds after the final state is reached. Apparently my code did not notice it well enough or was too nitpicky
Von meinem iPhone gesendet
Am 06.01.2022 um 19:11 schrieb Dennis Albrecht ***@***.***>:
I think the length is almost bearable: "only" 2.5 mins with 30fps. I just feel that starting around frame 1000 or so, I'd argue that there isn't much more going on than before, It appears to just repeat the same 30 frames (that is the frequency with which all LEDs turn off approximately) over and over. Or the changes to before are too little to be noticeable.
Don't know if the current runner code permits this, but last year Matt just interrupted animations when he had enough. So, he might just end the animation after the first half a minute or so.
—
Reply to this email directly, view it on GitHub<#59 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABQ7SEVYEUQYP2NAJG4JMVDUUXLLHANCNFSM5LMX7OBA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
regenerated with new insights: - better periodicity detection - end after a few final periods, hence no longer unbearably long - shift the R, G, B populations for nicer colour effects(?)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An animation that is awfully long (some 4000 frames!), so hopefully, the tree ultimately runs at 60 fps rather than 30 fps. If not, feel free to double-speed it by averaging pairs of consecutive lines.