search

SCIInstitute / map3d

Other
3 stars 3 forks source link

Allow automatic time stepping the circulates through t=0 #34

Open rsmacleod opened 6 years ago

rsmacleod commented 6 years ago

The idea here is that the user could hold down the arrow key and move endlessly, looping through the time course of the data.

bryanworthen commented 6 years ago

I imagine this would be a toggleable feature?

bryanworthen commented 6 years ago

Feature should be complete. I intentionally did NOT force multi-surface synchronization on looping - a surf that reaches the end will loop back to the beginning even if other surfaces haven't reached the end yet.

(Use -fl on the command line or select 'Frame Looping' from Frame Control menu).

rsmacleod commented 6 years ago

Hi Bryan,

We chatted about this last week and would actually propose a slightly different wrap around behavior.

Could you set things so that all surfaces are held at the last time frame until the longest one is done, and then wrap back to the first index in all surfaces? This seems like it would keep things best aligned over multiple plays of a beat. This the sequence would like the following for 2 cycles of a 3-surface scenario in which surface 1 has 6 time instants, surface 2 has 4 and surface 3 has 5.

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 4 4 1 2 3 4 4 4 ... 1 2 3 4 5 5 1 2 3 4 5 5 ...

Your scenario, if I understood correctly, would result instead in

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 1 2 3 4 1 2 3 4 ... 1 2 3 4 5 1 2 3 4 5 1 2 ...

and you can see how in the second cycle already, things get offset and we get a mess with no alignment at all across surfaces.

Thanks (and happy belated birthday)! Rob

On Jan 3, 2018, at 23:20 , bryanworthen notifications@github.com wrote:

Feature should be complete. I intentionally did NOT force multi-surface synchronization on looping - a surf that reaches the end will loop back to the beginning even if other surfaces haven't reached the end yet.

(Use -fl on the command line or select 'Frame Looping' from Frame Control menu).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SCIInstitute/map3d/issues/34#issuecomment-355207660, or mute the thread https://github.com/notifications/unsubscribe-auth/ACbwN235cjhnAH9oNQHkZ5EzdP7et_Igks5tHG2QgaJpZM4OajSN.

bryanworthen commented 6 years ago

Yes, you are correct in that that is what it would currently do, and yes, I can make it happen as you describe.

Bryan

On Sat, Jan 6, 2018 at 7:18 AM, Rob MacLeod notifications@github.com wrote:

Hi Bryan,

We chatted about this last week and would actually propose a slightly different wrap around behavior.

Could you set things so that all surfaces are held at the last time frame until the longest one is done, and then wrap back to the first index in all surfaces? This seems like it would keep things best aligned over multiple plays of a beat. This the sequence would like the following for 2 cycles of a 3-surface scenario in which surface 1 has 6 time instants, surface 2 has 4 and surface 3 has 5.

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 4 4 1 2 3 4 4 4 ... 1 2 3 4 5 5 1 2 3 4 5 5 ...

Your scenario, if I understood correctly, would result instead in

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 1 2 3 4 1 2 3 4 ... 1 2 3 4 5 1 2 3 4 5 1 2 ...

and you can see how in the second cycle already, things get offset and we get a mess with no alignment at all across surfaces.

Thanks (and happy belated birthday)! Rob

On Jan 3, 2018, at 23:20 , bryanworthen notifications@github.com wrote:

Feature should be complete. I intentionally did NOT force multi-surface synchronization on looping - a surf that reaches the end will loop back to the beginning even if other surfaces haven't reached the end yet.

(Use -fl on the command line or select 'Frame Looping' from Frame Control menu).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ SCIInstitute/map3d/issues/34#issuecomment-355207660, or mute the thread < https://github.com/notifications/unsubscribe-auth/ ACbwN235cjhnAH9oNQHkZ5EzdP7et_Igks5tHG2QgaJpZM4OajSN>.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/SCIInstitute/map3d/issues/34#issuecomment-355749675, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQy7k1AJonKEgHkD69pmptw9XtWTsT8ks5tH4CcgaJpZM4OajSN .

bryanworthen commented 6 years ago

And thanks for the birthday wishes!

On Sun, Jan 7, 2018 at 4:07 PM, Bryan Worthen bryanworthen@gmail.com wrote:

Yes, you are correct in that that is what it would currently do, and yes, I can make it happen as you describe.

Bryan

On Sat, Jan 6, 2018 at 7:18 AM, Rob MacLeod notifications@github.com wrote:

Hi Bryan,

We chatted about this last week and would actually propose a slightly different wrap around behavior.

Could you set things so that all surfaces are held at the last time frame until the longest one is done, and then wrap back to the first index in all surfaces? This seems like it would keep things best aligned over multiple plays of a beat. This the sequence would like the following for 2 cycles of a 3-surface scenario in which surface 1 has 6 time instants, surface 2 has 4 and surface 3 has 5.

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 4 4 1 2 3 4 4 4 ... 1 2 3 4 5 5 1 2 3 4 5 5 ...

Your scenario, if I understood correctly, would result instead in

1 2 3 4 5 6 1 2 3 4 5 6 ... 1 2 3 4 1 2 3 4 1 2 3 4 ... 1 2 3 4 5 1 2 3 4 5 1 2 ...

and you can see how in the second cycle already, things get offset and we get a mess with no alignment at all across surfaces.

Thanks (and happy belated birthday)! Rob

On Jan 3, 2018, at 23:20 , bryanworthen notifications@github.com wrote:

Feature should be complete. I intentionally did NOT force multi-surface synchronization on looping - a surf that reaches the end will loop back to the beginning even if other surfaces haven't reached the end yet.

(Use -fl on the command line or select 'Frame Looping' from Frame Control menu).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/SCIInstitute/map3d/issues/34#issuecomment-355207660>, or mute the thread <https://github.com/notificati ons/unsubscribe-auth/ACbwN235cjhnAH9oNQHkZ5EzdP7et_Igks5tHG2QgaJpZM4OajSN .

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/SCIInstitute/map3d/issues/34#issuecomment-355749675, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQy7k1AJonKEgHkD69pmptw9XtWTsT8ks5tH4CcgaJpZM4OajSN .